5.0.0? - such precision in versioning for a library or framework seems both too quick and too precise at the same time.
Angular 5.0.0
11–20 of 189 posts
Re: Angular 5.0.0
#12From my colleagues, both front-end developers and full-stack developers, I've heard nothing but criticism of Angular >2.0.0. I would like to hear the other side. If you use fresh Angular, why?
I love it. It is small if I want to, but it has lots of features if I need them. I don't have to worry about 3rd party libraries, because the official router, forms modules, http client, material components, flex layout etc. are all high-quality. The CLI not only helps with new projects, but also makes testing, linting, building, serving, generating new components/services/etc. easy. Implementing lazy loading with th…
Has testing components become any easier? I remember having to write a lot of boilerplate code every time that I wanted to test a component.
Re: Angular 5.0.0
#13Earlier quoted context omitted.
Typescript. When working in a shop with a large contingent of .NET developers, having a language that somewhat resembles what they are used to is a great asset.
Dare I say - but you can use Typescript with other frameworks too.. just because it's built in here / there are more resources?
I found especially that working with a project that requires a lot of extra bits to be installed (like the react ecosystem) makes working with JavaScript libraries from typescript especially painful, since you need to get typescript definitions for all of them, and they may not always mesh well together.
Re: Angular 5.0.0
#14This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.
Re: Angular 5.0.0
#15Earlier quoted context omitted.
Typescript. When working in a shop with a large contingent of .NET developers, having a language that somewhat resembles what they are used to is a great asset.
Dare I say - but you can use Typescript with other frameworks too.. just because it's built in here / there are more resources?
I’ve been using a fork of facebook’s create-react-app with typescript to generate new projects lately. It’s been great, zero friction. https://github.com/wmonk/create-react-app-typescript
Re: Angular 5.0.0
#16From my colleagues, both front-end developers and full-stack developers, I've heard nothing but criticism of Angular >2.0.0. I would like to hear the other side. If you use fresh Angular, why?
I love it. It is small if I want to, but it has lots of features if I need them. I don't have to worry about 3rd party libraries, because the official router, forms modules, http client, material components, flex layout etc. are all high-quality. The CLI not only helps with new projects, but also makes testing, linting, building, serving, generating new components/services/etc. easy. Implementing lazy loading with th…
I hate CLIs that do too much. Just give me a sane starter generator and I`ll take it from there. And please don`t hide webpack from me like angular cli does.
And this part "generating new components/services/etc. easy" I always find strange. Creating a component or whatever takes like 1-2 shortcuts in a normal IDE. And you can also use templates to expand various reusable/common parts. Why would I ever want to learn some cli command that would create ordinary file for me which I can create as usual with the tool I already use.
Heavy CLI tools just add another layer of unnecessary complexity to the project. Why don't just learn webpack which you can use on any project, and you will have much more power at your fingertips.
Re: Angular 5.0.0
#17Lack of compile-time checks for the template (and embedded expressions) is a major limitation of Angular. This may be OK for small projects. For large projects with many developers this is a huge problem. Here's what happens: a developer modifies code he's not familiar with. He introduces a bug due to a typo. He builds the code without errors, and runs the application, and everything seems to be OK. The bug is not found even at run time because the developer did not click on something during his manual testing. You can try to reduce such problems with automated tests, but test automation can't reach every corner. As much as possible such issues should be caught at compile time, and Angular can't. This is a major flaw.
Compare that to .tsx templates (Typescript's version of JSX). All html as well embedded expressions are checked at compile time, and typos are caught at compile time.
Re: Angular 5.0.0
#185.0.0? - such precision in versioning for a library or framework seems both too quick and too precise at the same time.
They are following semver: http://semver.org/
So the major version changes whenever they make a backwards-incompatible change.
However, I clicked in their upgrade calculator (linked from the post) and at a glance it appears the incompatible changes are fairly minor.
Re: Angular 5.0.0
#19Earlier quoted context omitted.
Dare I say - but you can use Typescript with other frameworks too.. just because it's built in here / there are more resources?
I found especially that working with a project that requires a lot of extra bits to be installed (like the react ecosystem) makes working with JavaScript libraries from typescript especially painful, since you need to get typescript definitions for all of them, and they may not always mesh well together.
As I commented above, you might want to take a look at https://github.com/wmonk/create-react-app-typescript.
It’s really helped reduce some of that 3rd party lib / buildchain JS fatigue for me.
Re: Angular 5.0.0
#20This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.
Could be worth your while to look into Cycle.js
It's written in TypeScript and, like Ng2, also heavily based on observables