441–450 of 452 posts
Earlier quoted context omitted.
Good thing you don't have clients demanding IE compatibility. Bye bye ES6 :-(
Doesn't babel (ES6 --> ES5) solve this issue or is there more to it?
Earlier quoted context omitted.
Why would you want HTML embedded into your component? Sounds like a maintenance nightmare.
So better embed the logic into the HTML? :)
I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…
Do you know of any large projects that use Angular 2? I just want see how readable the projects are.
Granted, not open source, but definitely drives home the point that it is trusted in production environments.
Earlier quoted context omitted.
npm install -g create-react-app The fun thing watching the new world of Javascript is that overtooling is so built in to everything that nobody even realizes how many tools they're using. You can't even install this thing until you have the standard pile of javascript tooling in place. And it never occurred to them to even mention how to get said pile set up. Once set up, this still uses all the same stuff. It just r…
This is the problem I have with all these "easy" setups and boilerplate projects. It doesn't matter how you set up your project, unless you do it wrong, it all comes down to a one liner in the end. All these things do is hide the complexity from you with the goal of being able to "get up and running quick", which I find fairly pointless for projects that are of a significant enough size that you're considering using…
React could be replaced with Preact or Inferno.
Redux could be replaced with MobX or RxJS.
Webpack could be replaced with JSPM.
Earlier quoted context omitted.
The sanctioned way forward for React is Flow. It's not as comprehensive as TypeScript, but there's no compilation required - Flow annotations just get stripped out. As of a couple of weeks ago it is part of create-react-app. https://flowtype.org
Too bad flow doesn't work as well as typescript in practice. It has way more bugs, is not as tested. It was very promising at first but typescript now has caught up with Flow best design decision: noImplicitAny, strictNullChecks. Also, check on the "try typescript" website: typescript's JS output is almost left untouched. it's effectively a replacement for babel, if you only care for ES2015 stuff, and not some of the…
Compared to this, typescript is actually dumb enough to require ts definition files to actually parse non-ts (js) files.
Earlier quoted context omitted.
Maybe because Angular material components are much better than material-ui?
I've been very happy with the material-ui components for React. They cover every component I need, and it was trivial to integrate them into an existing app over time, no need to do a full conversion on day one. They also seem entirely React idiomatic, I've learned a lot about how to build reusable components myself from their API.
material-ui's tutorials are really bad examples on this. They teach you to import from specific dir path inside material-ui. (e.g. import Pen from 'material-ui/lib/pen' or whatever)
Instead, they should recommend: import { Pen } from 'material-ui' since most of their exports are already in material-ui/src/index.js file (or some index.js file from package.json's main part)
Earlier quoted context omitted.
Maybe because Angular material components are much better than material-ui?
I've been very happy with the material-ui components for React. They cover every component I need, and it was trivial to integrate them into an existing app over time, no need to do a full conversion on day one. They also seem entirely React idiomatic, I've learned a lot about how to build reusable components myself from their API.
Earlier quoted context omitted.
What about angular CLI - ? have you found that useful in your workflow?
I have found Angular CLI productive, because it helps quickly generate components (each component has an html, ts, css, and spec.ts file with some boilerplate code). It is fairly quick to get up and running with angular-cli as compared to writing a webpack configuration file. However, since angular-cli is in beta, it lacks the flexibility that using webpack directly would offer. (P.S: Angular-CLI latest release would…
So I have never used Angular before but work with Vue. Looking at the tutorial, why is there the syntax of [(ngModel)] (equivalent would be v-model for me) and ngFor = (v-for)? Why are they different? It looks kind of unnecessary to me. I would really appreciate if someone explained it.
[1] - https://angular.io/docs/ts/latest/guide/template-syntax.html... [2] - https://angular.io/docs/ts/latest/guide/attribute-directives...
Earlier quoted context omitted.
Why? It's Apache 2.0 licensed...
People seem to have forgotten that MicroSoft was a gigantic threat to our industry, and still is. It owns 98% PCs world wide. What would we think if 98% of gaz stations worldwide where belonging to one company? That would be dangerous, right? Same with MS except it's worse, because PCs are eveyrwhere controlling everything. It's Big Brother in real life. Just imagine one moment how many critical decisions having worl…