I think that's a bit silly to say. We don't know how the web would have evolved without these languages, but it's pretty evident that modern web development has had some sizable influences on programming in general, and it wouldn't have happened without it's humble beginnings.
I also suggest both languages have evolved quite a bit since. Between these, though, I think modern JS has had the most impact. This can mostly be attributed to the node community, with a great deal of insights from ruby.
Things like async patterns and quality package management have changed our standards for what we expect out of modern languages, despite the coerson based parlor tricks chuckled at by those who don't use the language.
PHP, on the other hand, is still a templating language that lives and dies in a request response cycle.
I don't understand the websocket protocol issue. The connection is not the http(s) protocol beyond the upgrade - allowing the use of http or https here is misleading, no? Is using a turnary or having a value other than what the current page is navigated to so terrible? I'm glad their doing this work at normalizing the browsers. I just find that one a bit low priority if it merits a change at all.
It's great for influencers and beginners because of the ability to copy and paste examples plus the hype. The moment you put a scenario where there is no boilerplate available on the table, the utility of tailwind goes out the window.
As for Htmx, it's nothing new. I don't dislike it, but comparing it to web frameworks like React is missing the point. A lot of what it gives you (or doesn't) can already be achieved with a bit of vanilla js and, if you're feeling fancy, jQuery. Advocating for it as a replacement for something like React is sort of like recommending a bicycle to someone who drives. Yeah, it has its place, but it doesn't replace the utility of the car. Insisting it does indicate you don't know much about cars - or maybe bikes.
Anyway htmx uncomfortably reminds me of the MVC servers we use to write 15 years ago where the frontend always ended up being an unreadable unmaintainable mess after a few years because the frontend was treated as a random collection of assets for views to use.
Yes, if they require me to use a specific os, or install software to observe me, I won't take the job. Do you want me to build you awesome software? You need to let me use the tools of my choice. Full stop.
I thought the game "I know you are, but what am I" was for kids. This hateful obsession with Elon Musk is inherently political, I didn't bring that to this discussion.
So were Germany's industries when they lost the second world war after trying to exterminate the Jews. This is the fault of Hamas, just like what happened to Germans was the fault of the Nazis.
This is why I never use google products for anything mission critical. They cancel all sorts of projects, even when it's against their business interests (arguably). From the outside these projects seem more like pawns for executive advancement rather than products they care about, let alone their customers.
I absolutely cannot wait for this to land. it's been a long time. it's going to make Rust much more approachable to new developers, and it's going to make the lives of existing Rust developers much less tedious.
I also suggest both languages have evolved quite a bit since. Between these, though, I think modern JS has had the most impact. This can mostly be attributed to the node community, with a great deal of insights from ruby.
Things like async patterns and quality package management have changed our standards for what we expect out of modern languages, despite the coerson based parlor tricks chuckled at by those who don't use the language.
PHP, on the other hand, is still a templating language that lives and dies in a request response cycle.