4 ms·
It is true that PHP has a bad reputation and that effectively limits number of potential skilled developers. Number of available developers is still high but i
by tored 6y ago
It is true that PHP has a bad reputation and that effectively limits number of potential skilled developers.
Number of available developers is still high but it could be even higher if it had the same successful propaganda as JavaScript or Python.
There is nothing in the language itself that should stop it from competing with any general purpose language,
not anymore.
I think this is the next important step for PHP, have charismatic & humorous evangelist like Douglas Crockford.
Crockford’s missionary work was done during a time when JavaScript was in a big expansion because everyone wanted to write single page applications.
But today there is huge JavaScript fatigue and more and more developers have start to realize that server side rendering is (back to) the future for most of the traditional web, especially in a time where time to market has become even more important.
The constant churn of the JavaScript realm have now reached epidemic levels, a massive & relentless wave of deprecated and unsupported projects sweeps over every organization. Somewhere right now some poor developer inherits a Angular 1.1 project built with gulp.
I think also there have been a shift in regards to fullstack developers versus frontend & backend developers, many companies have woken up to disastrous idea of splitting frontend & backend developers into separate teams and now merging them again, as result the fullstack developer becomes more important. PHP is in my opinion best fullstack web platform you can use.
Say after me, No more build steps for rendering a paragraph, no more unhandled Ajax errors, no more REST JSON apis with only the frontend as consumer, no more reimplementing the database schema in JavaScript, no more asynchronous state rendering on the same page. <Insert Braveheart meme>
- luckyshot 6y agoWow, that was so on point. > Somewhere right now some poor developer inherits a Angular 1.1 project built with gulp. That hit hard. I was reassigned to an old project from 5 years ago with an archaic framework, to refactor all the code to the "new shinny JS framework". Ironically, I was in the team that built it 5 years ago. It is dreadful. Rinse and repeat. I feel like I'm doing something wrong when I advocate against projects that need 50,000 files and a 2-minute build when you could just do with HTML/CSS, native JavaScript and a simple CRUD backend.
- tored 6y agoThanks. Checkout htmx https://htmx.org/ https://htmx.org/ Dynamically update parts of your page but still render everything on the backend, where you already have all your data. Pass HTML fragments back, like we did in the old days prior to the JSON hype, but let htmx do the fetch & swap work so you don’t have to, that is only repetitive anyways. Now you hardly need jQuery (or similar) anymore either, Just HTML & CSS.
- luckyshot 6y agoThank you tored, it even supports WebSockets :-)