Re:Angular 2 Beta released
by sandGorgon on Tuesday December 15, 2015 @10:53PM
(#10742262)
Yes you can!
We are using requirejs, babel,es6 to have a react setup that runs completely in the browser. But for some reason, react makes this information really obscure.
It works really well. Including breakpoints in chrome,etc.
It might work for developing, but I don't think it works well for people actually using it, it's too slow.
Re:Angular 2 Beta released
by sandGorgon on Wednesday December 16, 2015 @01:52AM
(#10742796)
which is actually my point - running it this way helps us do a lot of beta testing internally,etc. Obviously this is not a production strategy, but the way we have written code (with requirejs) is that we can switch between them.
I really hope that React makes this more public - it makes it for quick and dirty prototyping. P.S. love ES6. Performance be damned!!
Care to share your setup? I.e. minimal todo-like application with both direct development and with compilation for production site.
Re:Angular 2 Beta released
by sandGorgon on Wednesday December 16, 2015 @12:02PM
(#10745571)
Give me a few hours, I'll strip some stuff out.
Don't spent to much time on it, because it will be deprecated in few years. :-)
>I think Angular is more accessible than React. I don't think React will be adopted as much by non-engineers.
Both are meant for engineers, if by that you mean developers.
For very small projects you can write react code in one or a few files without babel, webpack/browserify and similar tools. That closes the gap but I agree that angular is easier to just prototype something simple if you're not a developer.
I say that as someone who thinks React is the future of JavaScript development and there's no chance I will ever go back to separate templates so Angular of whatever version is just automatically disqualified. It would be like going back in time and I do not want to do this.