we've come full circle - macromedia dreamweaver had this in 2001
replies(9):
Being in the industry for 20+ years and starting as a teenager making games in Flash it makes really hard for me to treat webdev seriously with all their revolutionary innovations.
At work I often encounter a resistance to a tech or solution I propose, because "there hasen't been any substational contribution to the repository in a week, seems dead to me". To which I kindly respond with a question - how do you calculate hypotenuse, because it's been a long time since Pythagoras made the last commit. Meanwhile, some of my friends are still doing side jobs using CakePHP, 20 years later. :)
I think the framing here is unfair.
It's not that the people innovating in JS or HTML think what they're doing is "revolutionary" or has never been done before. Generally they are applying ideas that have been developed elsewhere, but are currently lacking in whatever their specific area is.
(1) Some time ago I'm at a coding interview and I'm tasked with an algorithm to calculate the biggest rectangle you can make of a set of segments. Or something similar. I'm presented with a computer, with VSCode, with an open file with some code already. I left my chair, approached the whiteboard available in the room and started thinking about how to address the problem. The interviewer was not pleased with my approach and eventually after I exchange my thought process he invited me back to the computer, asked to write some code, and when he saw I was doing for loops with vars he interrupted me, pointed at the beginning of the file which was "import lodash" and showed me the expected solution. A lot of functional mambo jumbo which was obviously very sexy at that time.
I looked at his code and asked him what's the computional complexity of his solution. He looked at the code, thought for a minute and said the session is over.
(2) About that time I was doing a web app that was a huge web form. The user could exit and resume a session at any given time so the input was stored in database and was supposed to be retrieved when the session resumed.
At one point I noticed that the initial loading time was noticeably slower, and after inspection it turned out that the init time raised from zero to about 800ms. It was the same time when our senior JS programmer with 9 years of experience shipped the code that was responsible for retrival of the data from the backend.
It was functional masterpiece. No loops, lots of map and reduce and he was very proud of it.
When I pointed out it had O(N^6) complexity and could be fixed with a simple for loop matching ids he got offended and stated that "we don't program that way anymore, functional is the future".