Slashdot Mirror
Google's New Angular 2.0 Isn't Compatible With Angular 1 (techcrunch.com)
An anonymous Slashdot reader quotes TechCrunch:
When Google announced Angular 2 in 2014, it created quite a stir in the web development community because this new version wasn't just an update, but instead a complete rewrite that wasn't compatible with the older version... "Angular 1 first solved the problem of how to develop for an emerging web," the company writes... "Six years later, the challenges faced by today's application developers, and the sophistication of the devices that applications must support, have both changed immensely."
Announcing the final release version of Angular 2 last week, Google thanked the open source community, saying "We are grateful to the large number of contributors who dedicated time to submitting pull requests, issues, and repro cases, who discussed and debated design decisions, and validated (and pushed back on) our RCs." TechCrunch writes that Google's Angular team "now also recommends that developers use TypeScript to write their apps...a Microsoft-developed superset of JavaScript that adds features like static typing and class-based object-oriented programming."
Announcing the final release version of Angular 2 last week, Google thanked the open source community, saying "We are grateful to the large number of contributors who dedicated time to submitting pull requests, issues, and repro cases, who discussed and debated design decisions, and validated (and pushed back on) our RCs." TechCrunch writes that Google's Angular team "now also recommends that developers use TypeScript to write their apps...a Microsoft-developed superset of JavaScript that adds features like static typing and class-based object-oriented programming."
That's because it's a complete rewrite, and anyone who has been around for the last year who develops Angular already knew this.
It wont ever be implemented as long as the previous is supported. Shoot my employer still supports IE 6 and would only still use it if MS didn't force change.
I said the same comment on previous story with Swift. People never learn once something is etched it is the word of God and is almost impossible to change
http://saveie6.com/
typescript adds "class-based object-oriented programming".
Lie.
"Classes" existed already as prototypes, and with ES6 you can create those prototypes with your favorite "class" definition.
I'll never be using typescript so I'll never be using angular2. As much as I loved working with Angular1, I'll instead move to reactjs.
When Google announced Angular 2 in 2014, it created quite a stir in the web development community because this new version wasn't just an update, but instead a complete rewrite that wasn't compatible with the older version
Such a stir that it was noticed by Slashdot in 2016
Google has taken a community-hostile position to destroy the future value of all apps unfortunate enough to have selected Google as an honorable vendor and adopted Angular as a key technology.
For their troubles, adopters of Angular have seen their investments discarded, and told to rewrite their apps so Google can make more money.
F that.
We alreaddy knew this for 2 years. The moment i start getting proggraming news ofrom teccrunch is when it's time to give up on that language
either way, it's not with compatible to compete with React anyway
I use knockout.
Much simpler.
http://knockoutjs.com/
What is Angluar?
When you jump onto the newest technology for development there is always a risk that it will die out or be rebooted in a new version.
The problem software development process needs a period of wide usage for people to find where the pain points are. Sometimes those pain parts are part of the root code as they were at the time considered an acceptable trade off, only to later realize it is a big problem.
If you are learning or playing with the technology rusing v1 is good. If you are trying to make a professional system for long term usage you may want to fall back on the older more established alternatives such as jquery while may not solve the problems the same way as angular it will get the job done and has a long track record.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
A rewrite does not have to be incompatible. It usually does so though. A rewrite could be a rewrite of implementation only while keeping API
But is it compatible with SWIFT 2.3??
I must know!
Is this yet another clickbait title? The real news here is that final release is out but the title is about compatibility which was known for 2 years? What the hell!
Um, yeah, that's not how it works. It's all open source. And actually, from my personal point of view, TypeScript might very well be the first MS-developed tool I've had on my machines in, oh, 15 years. And it is actually very nicely done.
Gosh, thanks. That must be why the other ships call me Meatfucker -- GCU Grey Area (Eccentric)
Everything on the web is always a complete rewrite. It is like each year a bunch of new CS grads turn up who are hell bent on 'fixing the internet' by creating a new unifying platform. There is even a sort of cyclical way in which we go through imperative -> OO -> functional and back again as the magical way in which every app ever conceived could be written better. Same happens for design patterns, test strategies, and whatever is the latest model-view-whatever thing. My favorite is when scripting programmers discover pointers and low level memory management and act like they have reached enlightenment.
The whole thing is like groundhog day with different terminology if you stay in the industry for more than a generational cycle, which I guess might be a contributing factor to why most programmers don't last that long.
I've been aghast at the broad adoption of thick client JS frameworks on the open web and a growing open hostility towards progressive enhancement, as if it's somehow not possible to build a single page app without totally breaking everything that makes the web a great platform.
There is a reasonable argument to be made that the vast majority of websites should not be using one of these, as the majority of these frameworks are incompatible with progressive enhancement and progressive enhancement is still the best way to build most sites. I firmly believe vanilla JS should be everyone's default. There are exceptions, but those exceptions are very narrowly tailored. I think this article which outlines those exceptions should be required reading for every web developer.
It seems like a lot of people these days don't realize you can build single page apps using progressive enhancement. And when you do, they perform better and are more fault tolerant while avoiding an unnecessary hard JS dependency. This whole stereotype you hear from people about single page apps being the future and progressive enhancement being the past is the most annoying false dichotomy ever. You can do both so long as you consider choices other than big, largely badly designed frameworks. It seems like most people who use Angular just want to make websites that don't reload the page when you click links. Maybe consider using a client-side router library instead of a giant monoframework. Way less code that has to be dumped on the user.
I'm not saying it isn't possible to use the big monoframeworks responsibly. The article above outlines good use cases for them. If you're building a client-only Electron app for instance, then go nuts with React or whatever if you like it. But seeing people design regular websites on the open web that are mostly just text, forms, and images using things like Angular and React is the biggest, most depressingly popular cargo cult antipattern we've seen since the days of Flash sites.
You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
Anyone can have 50 versions, but let's see if Apple and Google can get 50 versions that are incompatible with the previous one and still have anyone want to use it.
Ok everyone, turn the crank one more time!
.. are partly the constantly mutating APIs! Irony, much??
blunderbuss shot is not compatible with an M20 rifle
This is the last version of Angular. A year from now Google will drop it in favor of Jula 1. Angular was soooo boring. Hope you didn't put much effort into learning it!
yeah.
even more irony is that you kind of lose all benefits of node by piling shit on top of it. might just as well made the whole shit as it's own vm.
react is where it's at. Even google uses it.
off topic, sure, but I wonder how much of this was pre planned.
Manning wanted to change genders,but didn't have the funds.
Plan:
1) Release sensitive data
2) get caught
3) Transition in prison on Gov dime.
Angular 1 first solved the problem of how to develop for an emerging web,"
*What* "emerging web"? The web has been around for decades now. The only thing that's changed is the fact that there are now even more unnecessary layers of javascript on top of everything than there was before.
"Six years later, the challenges faced by today's application developers, and the sophistication of the devices that applications must support, have both changed immensely."
Yeah, because asshats like you keep reinventing the wheel and forcing everyone to relearn what they already knew, throwing away hard won lessons in the process, and resulting in poorer quality code overall because no particular language or API seems to last long enough anymore for people to become proficient enough in it to deal with all the inevitable bugs.
Why even call it Angular if it's completely incompatible with the previous version?
Install most linux distros and run 'python'. Odds are overwhelming that it will be python 2.
But at least on UNIX and Linux, you don't have the problem where the part of the filename after the last period determines which interpreter is used. Instead, you have the executable bit, which causes the OS to read the first line of the file to find the interpreter:
This means use the env program and have it search the PATH for an interpreter called python3.
One reason Python 3.0 through 3.2 didn't gain popularity so fast is that on Windows, .py was still associated to Python 2. It took until 3.3 for the Python team to add the PEP 397 launcher, which looks at the first line to determine which interpreter to use UNIX-style. This way side-by-side installations of Python 2 and 3 work as expected.
Developers have been WAY too eager to jump onto the latest development fad. Google has been well-known for creating products and dropping them. Why should they behave differently when it comes to open source projects?
Microsoft may have its own issues, but at least they stay committed to preserving (most) legacy code. You can still run a lot of c. 1985 software on today's Windows machines! As a .NET developer, I'm pretty sure my source code is still going to work when Version 5 comes out.
I'm glad I didn't take the time to learn this horse shit. I feel bad for all the poor assholes who did.
Google used to be about speed, compatibility and awesomeness.
Now they are just another cocksucker, in a very long list of cocksuckers.
google have very little respect for keeping their APIs established. they deprecate everything and you can hardly depend on any google API to not change. android is a complete disaster because of this. their UI framework and advertising services hardly stay the same for more than a year.
Flipping the major version number should be enough to communicate it is a breaking / not backwards compatible version.
Soon Angular will be as powerful as any decent web framework from 15 years ago.
function service(name, constructor) {
return factory(name, ['$injector', function($injector) {
return $injector.instantiate(constructor);
}]);
}
Such elegance.
I used Angular 1 for two years, the glimpses I had of A2 were scary! Then I read that Rob had left to start a new framework, and he made it to 1.0 before A2 did I love it, I've used it for 3 projects now and it's so sweet! Clean as can be and ES6 thru and thru. They even give you app skeletons that work with webpack so that your production builds are done without you having to do more than switch from: npm start to: npm run build:prod https://github.com/aurelia/ske... They also hook up babel for you, so that you can write ES6 and run as ES5 -- and they support Typescript as a first class citizen if you're into that There's a site here: http://builtwithaurelia.com/ that can let you look at source code for different things pretty quickly Anyway, I can't say enough good things about it - try it, you'll like it !!