71–80 of 189 posts
Earlier 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?
All I want for Angular are better error message and better browser-refresh times. Right now on 4 I get a meaningless page of gobbledeguck for most error (b/c of transpilation) and 12 seconds to reload the page.
CLI should be pretty much instant to reload a page.
I can personally stand it because I remember working on 2 million line C++ projects in the 90's. The millennials on my team, on the other hand, are going insane. I've recommend they disable live-reloading completely.
Earlier 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.
Even with `--noImplicitAny`, it's gotten pretty easy. Leave a scratch .d.ts file somewhere in your project and when you install a new library you can start with:
declare module 'libraryname'
declare module 'libraryname/**/*'
The number of npm packages with types directly included is growing at an impressive rate (even Facebook often bundles them for React libraries), so there's not even the need to seek out types in so many cases these days.
Earlier quoted context omitted.
Vue.js can be a good option for shops coming from Angular 1.x.
I love Vue. I prefer it to React and Angular. But once you get to customizing your use-case (like adding Typescript, State management, or Design frameworks) you start relying on increasingly smaller projects with less and less "maturity". For example I make heavy use of the vue-typed library[1] but it has 47 stars and two contributors. [1]: https://github.com/vue-typed/vue-typed
This 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.
This 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.
It's not just Angular. To me it feels like everything in the JS world releases way faster than it's reasonable to keep up with these days.
There are no obligations whatsoever to keep your project cutting edge and even less of reason to migrate to a more popular framework. It's not as if browser support for Angular 1 would stop.
Lack 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 fo…
i just updated a medium sized angular 4 app to angular 5 with no problems. typescript has been our saving grace especially when you're collaborating code with your team. we've really come to enjoy angular. if you're migrating from angularjs it can be difficult but if your developing a new app with form validation, routing, redux then i would recommend angular.