https://guides.rubyonrails.org/maintenance_policy.html
> RoR has breaking API changes often enough ... magically break that often
According to the support policy, nothing magic about those breaking changes: "Breaking changes are paired with deprecation notices in the previous minor or major release."
That said, I was referring more to the Ruby on Rails ecosystem in general. Our production deployment has 80 gems, which I'd say is a normal number for a big Rails webapp, and sadly many of them do not follow semantic versioning, so that minor gem version updates might contain unexpected breaking changes for us.
The advantage that old languages like PHP or C++ have here is that their standard libraries have been around for so long that the API rarely changes these days.
Once I learned to listen to incompetent users, I started to create usable software.
My gut reaction is still, "RTFM you're doing it wrong." But now I follow that up by figuring out how to make the software work like the user thought it should or I change it so they never get in the frustrating situation in the first place.
What I finally realized was that if one person got frustrated enough with my software that they took the trouble to post an incoherent and technically incorrect rant on Github then it's likely that 100s more users had similar problems and said nothing.
Now I receive effusive emails about my Open-Source almost weekly.
But after reading the article, I thought that the 99% number was about developers not joining the discussion with other developers. And for that purpose, I'm not sure if open source is still a good idea.
This. Happens so frequently, that making things OSS now carries an additional burden. I personally find it very painful to e.g. ignore the PR or issue opened by some hapless person in a bad situation trying to figure out the most dumbest thing. It makes the alternative (never OSS'ing anything) sound better, if only for my own peace of mind.
So yeah, PHP is still a thing.
Eh, that's not really the case anymore either. It's made many improvements over the years. Not that I'm saying it's some wonderful language, but you can't really compare it to the PHP 4/early 5 days. I think credit is deserved to the folks who have brought PHP to where it is today.
It has nothing to do with the code being spaghetti or not. It's about a level of abstraction where I no longer consider something made with wordpress as something created with PHP. The PHP was allready created and then someone just clicked a few menus to choose what existing PHP he or she wanted.
The more fitting category would be just calling such websites "Wordpress" websites and not PHP websites.
I can deploy a python web application I have written to a new web server within minutes by clicking deploy in bitbucket.
So using your definition:
* The code is already written.
* I clicked a few menus and I had the python code I wanted running.
It isn't a python application. However the web application when it receives a request will run python code. It is clearly a python based web application.
So if I got someone else to press the deploy button in bitbucket, it suddenly isn't python code? That doesn't make sense does it?
> Why don't you consider each and every website running PHP also a C website?
The web site/app logic is written in PHP, not C. The runtime for the vast majority of PHP deployments happens to be written in C.
Additionally while I did say interpreted earlier that really isn't true anymore. PHP runtimes these days tend to break the PHP script down into byte-code. There are alternative runtimes for PHP just as there is Java or .NET.
There are at least 4 I can think of. Two of those aren't C (C++ and .NET). However there is nothing stopping you from writing a runtime that runs on the JVM / Lisp / Go / Brainfuck / Lol code / 68k assembler.
You completely ignored the most important sentence in my comment which addresses this.
> The web site/app logic is written in PHP, not C. The runtime for the vast majority of PHP deployments happens to be written in C.
The logic is written in PHP just as much as it is written in C. The logic is actually written in the language the creator used. Which is the wordpress UI.
I did not. I've addressed it at least 2 times now. If you choose to ignore those responses that invalidate your point that is of your own doing.
> The logic is written in PHP just as much as it is written in C.
Nope. I have already shown this assertion of yours to be false as there is no requirement for the runtime to be written in C.
> The logic is actually written in the language the creator used. Which is the wordpress UI.
Issuing commands to a program (which is what is happening) does not make those commands a programming language.
On the other hand, not even using a service like Heroku can save us from constantly having to patch or update the Rails apps.
1. Most of the new tools are pure nightmare to maintain. RoR has breaking API changes often enough that you need multiple people to maintain a large codebase, whereas in PHP you'd only need one person because things don't magically break that often. And MongoDB is so convoluted and complicated that almost nobody can deploy it correctly. And then there's "new" container techniques, which are basically just an admission that you have no f*ing clue on how to make your new tool set secure. In most cases, the loud new technology is just over-funded hipster stuff, but not ready for the real world yet.
2. Posting things online (e.g. Source Code) will not only attract the attention of peers. You might also get flooded with rather demanding emails by technically incompetent people who complain that your free source code release didn't solve their problem.
Also, I wonder if the author is aware of IRCs ongoing popularity for private development discussion rooms. It seems many people thought Slack was new, but some of us programmers have been hanging out like that since 95.