Angular.js is dead, so let's talk about everything else

The video is terrible. These two guys are too awkward for a script like this.

But TRWTF is how stupid are the fans in the audience. Laughing and applauding at the news that all their code has just been abandoned by Google and left to rot into "legacy". Silverlight people at least had the brains to see the writing on the wall. How long is the denial phase, again?

TLDW for the lazy ones. Google has basically decided to invent a new SPA framework and named it angular 2.0. Current angular 1.x is an evolutionary dead end.

There's no update path. No piece of the old code you get to keep. Just throw away all the weird angular 1.x constructs you've spent years mastering, and start anew. Might as well move to ember or react and away from these jokers' clutches.

Gong! Gong! RIP angular.js.

That's what you get when you trust google to provide you with programming tools. They have an abysmal record so far.

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

Then rename it to "Angular Classic 2.0" and the other one to "Angular Modern" for extra confusion. Then the third version can be "Angular One" and the other one "Angular 10". No wait, that's another company...

Complaining that you can't do shit you did in 1.x when you move to 2.0 (no example here because I know neither) is like complaining that you can't do shit you did in Windows XP when you move to Windows 7 (example: dumping user data in Program Files). All computer systems should be rewritten and redesigned from scratch every few years. Backwards compatibility is good only in short term.

I don't think the comparison is fair. First, we're talking about a whole rewrite on something that hasn't been around for more than a few years. On the other, this is not about some API changes, but a whole rewrite that simply won't work with your existing code.

You can easily convert python 2 code to python 3. Or even write python 3 compatible code that runs on 2.

This may be (especially for someone better at Python than I), but my recent experience trying to use the two together was not enjoyable. (It was working with the Ubuntu panel, so maybe TRWTF was Ubuntu.)

The reason Google's products are used is that they are good products that do what they're supposed to.

And yet, never exceptional.

That's my point. All these tools and frameworks sort of work and have some measure of success. But Google is one of the richest tech companies in the world. They get all the best programmers and give them the best conditions. Including a lot of time to hack away on their passion projects outside of the daily churn.

Their dev products should be mind-blowing. World changing. And what do we get instead? GWT? Dart? Go? And now angular. All with some merit, but meh in the end.

Their dev products should be mind-blowing. World changing. And what do we get instead? GWT? Dart? Go? And now angular. All with some merit, but meh in the end.

Both Protobuf and Chrome were pretty awesome. Except Protobuf is now inferior to Cap'n Proto in every way (fun fact: the author of both is the same person), and Chrome is getting worse and worse with every release since v15 or something.

I wasn't talking from business point of view - I was talking from technical point of view. Netscape went out of business due to the above, but they did make a better browser than they could do without rewriting from scratch.

Does Angular need special browser support besides proper JavaScript implementation? Boy, that sucks.

Browser side apis that aren't anything to do with JavaScript might change in the future and then you are stuck using a depreciated framework which you have to maintain your own incompatible fork of it.

[1]: http://www.jwz.org/doc/cadt.html
Reading the esteemed Zawinski's article does leave me a tad puzzled. If a software was written from scratch, how could you possibly recreate all of the same bugs? I can imagine that once in a while you would get the same bug, but I can't imagine that this would be a regular occurrence.

Load of bugs in current version
Bugs are left there forever while dev on "new and shiny" continues, which is typically a rewrite.
Bugs are stale and nobody can be bother to check them. Won't get fixed as they are in the old version
New version is now current version ... go back to step 1.

The one pissing me off currently: Open Broadcaster Software, OBS.

It doesn't work with my capture card. There's no technical reason it shouldn't work (it works with some brands and not others), it's just a bug.

So I go into their bug tracker, it's reported, but what's the comment? "This won't be fixed now because we're rewriting OBS from scratch for version 2.0." What do you think the odds are version 2.0 will ever be finished? Ever? I'd put it at maybe 1:5. ... maybe.