User avatar
nixCraft 🐧 @nixCraft@mastodon.social
2y
😉
1995: PHP is dead, learn ColdFusion 2002: PHP is dead, learn ASP.net 2003: PHP is dead, learn Django 2004: PHP is dead, learn Ruby on Rails 2010: PHP is dead, learn Flask 2011: PHP is dead, learn AngularJS 2016: PHP is dead, learn Next.js 2022: PHP is dead, learn Python 2023: [Peter Quill from "Avengers: Infinity War"] How the hell is this dude still alive?
46
6
0
0
User avatar
nixCraft 🐧 @nixCraft@mastodon.social
2y
Anyone who has worked on a well-developed product knows that you can't replace old working tech like PHP or COBOL in an instant because it will cause more problems than solving them. Not to mention, it always involves heavy costs. The famous bank wanted to replace COBOL with new tech; the upfront cost for a year project was over 1 billion. The big vendor questions said they can't provide a 101% guarantee of the project's success. That is how complicated things are...
9
0
0
0
User avatar
🪨 @Varpie@peculiar.florist
2y
@nixCraft Most often, that is the case because the existing systems aren't well documented, which means the first step is to reverse engineer a 60 year old codebase that nobody can read. It is bound to result in some differences in the implementation that will result in costly mistakes.
0
0
0
0