pramttl
Joined 13 years ago
Joined 13 years ago
I'm not calling for open doors to everyone, this certainly needs a balanced approach. However, with such suspensions I think we seem to be going one extreme path. Global talent has helped develop industries and businesses here. Increasing restrictions to this extent and suspending these visas is going to push this talent out and promising businesses who want to get the best talent to work with them, will not-immediately but definitely follow their way out too. I hope the people who are celebrating this, at-least for a few minutes, come out of the myopic view and look at the long term economic consequences.
The H1B program itself is not a problem and in-fact is a big positive contributor to the US economy; but it definitely has issues like the one you highlighted (e.g. harder for employees to switch jobs) that should be addressed by the government to make it more viable.
"GoodRx does not sell information regarding your drug prescriptions and medical conditions that are linked to your name, contact information and other personal data you provide us."
[1] https://investor.verisign.com/releasedetail.cfm?releaseid=98...
Angular Router does allow nested states: - https://angular.io/docs/ts/latest/guide/router.html - https://angular.io/docs/ts/latest/api/router/index/Router-cl...
I don't quite recall what "targetted views" mean?
1. Typescript awesomeness: You can write plain JS or give type hints in Typescript. Typescript is awesome, because it is a superset of Javascript and compiles to Javascript. (Typescript > ES6 > ES5)
2. Modular code: It is is much easier to manage Angular code as it grows (compared to AngularJS). Components could be made independently and reused within other components using component interaction [1] (@Input, @Output)
3. Template Directives: .html template directives are available unlike ReactJS. A ReactJS vs Angular2 blog post online [1] argued that that putting HTML in Javascript is better than putting Javascript in HTML. I'd argue that template directives like ngFor, ngIf, etc are much simpler to understand. Also, it is easier to collaborate with a designer/half-developer who knows some html/scss and doesn't know Javascript than working in ReactJS where every collaborator has to know JS. This way, it is also easier for someone to gradually learn the framework. For me, template directives are a big win. If someone wants to construct templates with plain JS, that is still possible in Angular.
4. @angular/router is better than AngularJS routing and we don't have to use a 3rd party library (like ui-router was more popular in AngularJS than the angularjs router)
One thing that I have found annoying is that: UI libraries for Angular. Example: material2 (currently at alpha.8) [3] are not complete yet and lack several useful components. This can be a problem if you are looking to quickly build a complete, good looking UI. Hopefully, now with Angular 2.0.0 out; Angular team could focus on quicker development of material2, so we have all the AngularJS Material UI goodness with Angular.
[1] https://angular.io/docs/ts/latest/cookbook/component-communi... [2] https://medium.freecodecamp.com/angular-2-versus-react-there... [3] https://github.com/angular/material2