3 ms·
Angular's fatal mistake was the name change around Angular 2 ("Don't call it 'Angular 2', just call it 'Angular'"). The problem is that Angular 1 is VERY diffe
by umvi 6y ago
Angular's fatal mistake was the name change around Angular 2 ("Don't call it 'Angular 2', just call it 'Angular'").
The problem is that Angular 1 is VERY different from Angular 2+ and searching "Angular" gave Angular 1 results... the search index of Google was poisoned for so long with the wrong results that I switched to React out of frustration.
- hnrodey 6y agogoogle: angular http post call -angularjs
- bob1029 6y agoThe transition from Angular 1=>2 made it clear to us that this was not a good framework to use for long-term projects. We moved to RiotJS which was a breath of fresh air... for a little while. Then the same problems started plaguing that project in terms of major breaking changes so we hopped ship again. Now, we are on top of Blazor using server-side rendering. Our hopes are that by taking up allegiance with Microsoft that we can ward off horrific breaking changes for a few years and actually build something valuable during that time. Blazor is particularly appealing to use because we were able to completely define our UI state machines in C# classes that can be tested in perfect isolation from any client/browser interaction. We can also directly inject & reuse our existing business services without needing to develop any JSON APIs or other wasteful boilerplate.
- ep103 6y agoThat said, the name change was reasonable, because the changes in the framework were so, so vastly different.
- umvi 6y agoI agree name change was necessary, but "Angular" was a bad pick because of search index collisions with previous generation. Should have chosen a name that would not have caused search collisions.