> you really are completely misconstruing the point just to be edgy I'm misconstruing the point because I don't like analogies, especially when they only bring

> you really are completely misconstruing the point just to be edgy I'm misconstruing the point because I don't like analogies, especially when they only bring confusion. There's no need to bring cars into a discussion about Java and PHP. Programming languages are programming languages, cars are cars. > It's an insanely practical language, in fact probably -the- most practical language and that is why it's chosen overwhelmingly for important systems that need a large number of developers. Java being practical is part of it, its marketing to managers is also part of it. But being the most practical language for "important systems that need a large number of developers" doesn't mean that it's the most practical language for everything. To answer your first question: > So while PHP is ok, why choose PHP when you can choose Java/Kotlin? When you're a single developer that does lots of small projects, PHP works really well. In a way, it allows you to go faster at first. Depending on your business, that may be the most important thing, or not important at all. While my bank is surely running 90% Java, I would bet that there are many internal applications that saves people a ton of time that are written in PHP. That's how it was at my last job at <BIG COMPANY>.