4 ms·

I'm the author and I agree. Things have slowed down and matured. The "JS moves too fast" meme is well out of date, and in fact I wrote a comment here a few hour

I'm the author and I agree. Things have slowed down and matured. The "JS moves too fast" meme is well out of date, and in fact I wrote a comment here a few hours ago bemoaning it

escape_goat 4y ago
I don't know what it's like these days but I recall especially the pernicious 'evangelism'. People on a literal salary promoting frameworks like they were from marketing. As a bargain basement, self-taught, late web 1.0 dev more comfortable on the server side I remember rake-stepping the undiscussed limitations of Backbone JS, and then studying the ridiculous complexities of Angular 1 while reading post after post of Angular doctrine, and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong." By the time I was done I genuinely had no interest left in me for another new framework, package manager, or library.
- Frotag 4y ago
  > and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong. I wasn't in webdev-land when the migration happened, but as someone who maintains both AngularJS and Angular2 code, they don't seem all that different. Especially considering the later versions of ng1 tossed out all the globals (components with isolate scope by default) and moved to class-based directives. And then ng2 came along and rewrote everything into a prettier API (typescript with decorators and shit). But otherwise they both seem to have the same design when it comes to change detection, dependency injection, controllers / views, etc.
- mgkimsal 4y ago
  > and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong." By the time I was done I genuinely had no interest left in me for another new framework, package manager, or library.... I've seen this more than a few times over the years, and it makes me a lot more skeptical of praise for anything new. Almost always the praise is about technical aspects of a new tech/stack, and the value is almost always in the larger ecosystem. I'm fine - happy, often - with using something slightly out of date if it means there's a community of people who can help support it, answer questions, publish mods, etc. There's a balance somewhere to be found, but I've been burned too many times picking a tool, investing in it, then having much be thrown away for the 'v2' version which is often not backwards compatible (for good reasons, usually, but still problematic). Marks of maturity of a project - acknowledging upgrade requirements, publishing upgrade guides, supporting previous versions for a publicly stated time range, etc.
  - spiralx 4y ago
    > Marks of maturity of a project - acknowledging upgrade requirements, publishing upgrade guides, supporting previous versions for a publicly stated time range, etc. All of which did happen for AngularJS. And you could still be using your AngularJS components within an Angular application today - or vice versa - thanks to the tools provided to migrate piecewise. End of life for AngularJS was only five months ago after a four year LTS period that started in 2018, given that Angular 2 was released in 2016 that's a five and a half year period where both frameworks were supported. Libraries deciding to break everything without warning is definitely an issue that's caused me grief in the past. Moving from AngularJS was something we decided on and planned out well in advance.

I'm the author and I agree. Things have slowed down and matured. The "JS moves too fast" meme is well out of date, and in fact I wrote a comment here a few hours ago bemoaning it

escape_goat 4y ago

I don't know what it's like these days but I recall especially the pernicious 'evangelism'. People on a literal salary promoting frameworks like they were from marketing. As a bargain basement, self-taught, late web 1.0 dev more comfortable on the server side I remember rake-stepping the undiscussed limitations of Backbone JS, and then studying the ridiculous complexities of Angular 1 while reading post after post of Angular doctrine, and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong." By the time I was done I genuinely had no interest left in me for another new framework, package manager, or library.

Frotag 4y ago
> and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong. I wasn't in webdev-land when the migration happened, but as someone who maintains both AngularJS and Angular2 code, they don't seem all that different. Especially considering the later versions of ng1 tossed out all the globals (components with isolate scope by default) and moved to class-based directives. And then ng2 came along and rewrote everything into a prettier API (typescript with decorators and shit). But otherwise they both seem to have the same design when it comes to change detection, dependency injection, controllers / views, etc.
mgkimsal 4y ago
> and then learning that the great leap forward for Angular 2 was "yeah we're going to throw all that bullshit out we were wrong." By the time I was done I genuinely had no interest left in me for another new framework, package manager, or library.... I've seen this more than a few times over the years, and it makes me a lot more skeptical of praise for anything new. Almost always the praise is about technical aspects of a new tech/stack, and the value is almost always in the larger ecosystem. I'm fine - happy, often - with using something slightly out of date if it means there's a community of people who can help support it, answer questions, publish mods, etc. There's a balance somewhere to be found, but I've been burned too many times picking a tool, investing in it, then having much be thrown away for the 'v2' version which is often not backwards compatible (for good reasons, usually, but still problematic). Marks of maturity of a project - acknowledging upgrade requirements, publishing upgrade guides, supporting previous versions for a publicly stated time range, etc.
- spiralx 4y ago
  > Marks of maturity of a project - acknowledging upgrade requirements, publishing upgrade guides, supporting previous versions for a publicly stated time range, etc. All of which did happen for AngularJS. And you could still be using your AngularJS components within an Angular application today - or vice versa - thanks to the tools provided to migrate piecewise. End of life for AngularJS was only five months ago after a four year LTS period that started in 2018, given that Angular 2 was released in 2016 that's a five and a half year period where both frameworks were supported. Libraries deciding to break everything without warning is definitely an issue that's caused me grief in the past. Moving from AngularJS was something we decided on and planned out well in advance.