WeChat ID
aaronpk_tv
PHP is quite possibly one of the best languages to use for a project these days. The community is massive and full of people who are deeply passionate about best practices. There are more quality frameworks than you can hope to keep up with (if your ranking of quality is the meager toy that rails is, you'll be happy here). The frameworks are really good at abstracting away the awful API choices the language makes. That said, if you're writing in "PHP" instead of a given set of frameworks... you're working at a company that hired someone who wrote a lot of code with no experience of what makes a good system... but you'll soon find the JS looks exactly like that too, because that's not a PHP problem.
We traded the open technology of RSS for Twitter and now we will pay the price of the anonymous corporate agents telling us what words we can read.
Our wiki software reads and writes Markdown files from the filesystem. With 100+ pages on our wiki, we can still do near instantaneous full text search. Plus, changes to the content can continue to be tracked using Git and backed up automatically to Github. And there’s no database server to worry about. And if we ever want to migrate to another system, we’ve got all of our data in simple, human readable text files.
The Indieweb approach has a lot in common with Ev's ideas for Medium, but the key difference is that we are doing it in a way that works across websites, not just within one. We can use an editor on one site to post to another using micropub, even to silos. We have ways to highlight based on fragmentions, and a very simple way to connect responses together using webmention.
No one moves where they tweet because some other tool has better formatting or profile customization. That’s because a tiny percentage of the value Twitter brings comes from the software itself. It’s all about the network — the connection with other users and the content they create.