3 ms·
There's something to be said for a set of technologies you can continue using for a couple decades. I don't use MySQL anymore but otherwise this is my favorite
by jmathai 4y ago
There's something to be said for a set of technologies you can continue using for a couple decades.
I don't use MySQL anymore but otherwise this is my favorite stack. Nowadays, I use sqlite, flat json files, or google sheets.
- hyperhopper 4y agoPeople have continued using Fortran and cobol for decades. Doesn't mean they are good or pleasant. Try refactoring 20 year old php then tell me it is pleasant. If you can't, it shouldn't be recommended to OP
- deleted 4y ago[deleted]
- elteto 4y agoFortran will outlive every single JS framework mentioned on this page, and then some. There's definitely good and pleasant in knowing that your code will run for many years to come, if your project has such a timespan. Therefore, PHP is absolutely a valid recommendation.
- jmathai 4y agoDing. Ding. Ding. Basically my response :).
- hyperhopper 4y agoFortran surviving so long is due to lock in, not merits. That is a bad thing, not a good one.
- jmathai 4y agoNot sure why you think 20 year old PHP code would be difficult to refactor. It's extremely backwards compatible and things don't change much at all. I have a couple large projects written in PHP from 10-20 years ago that I'm sure I could refactor or make changes to easily. https://github.com/photo/frontend https://github.com/photo/frontend https://github.com/jmathai/photos https://github.com/jmathai/photos
- ofrzeta 4y agoAlso, see this: https://github.com/rectorphp/rector https://github.com/rectorphp/rector Instant Upgrades and Automated Refactoring of any PHP 5.3+ code