Thanks Mark. It might make sense at some point to configure the most popular Angular 2.x development environment, whatever that might be, even if it includes an ES6 transpiler. We could then use standards, such as favoring functions over classes in most cases, to keep the added complexity of the extended language from making the software more difficult to develop and maintain. --dawn
On Monday, July 20, 2015 at 5:29:16 PM UTC-5, Mark Volkmann wrote: > > One thing to keep in mind is that ES6 is not an all or nothing > proposition. You can start using an ES6 transpiler without changing any of > the existing ES5 code. Then as existing files are modified, maybe for bug > fixes or to add new features, you can start inserting use of ES6 features > gradually. The benefit is that by the time you are able to use Angular 2 > you will already be comfortable with many ES6 features. > > On Mon, Jul 20, 2015 at 4:21 PM, Dawn Wolthuis <dawnwo...@gmail.com > <javascript:>> wrote: > >> Thanks Mark, but the response here is disappointing. There has been a >> significant investment in learning ES5 with Angular 1.x, and it does not >> sound wise to do a move to ES6 so that it can transpiled back to ES5, when >> all existing code at this organization is written in a non-OO language. >> They are about to launch into a rewrite of an app written some time ago, so >> if it would be a really bad idea to write any app in JavaScript now, >> without first writing OO stuff to be transpiled back to ES5, then I would >> not be surprised if that were the last straw in their decision to go the >> Angular route. This was a very discouraging response, as you might imagine. >> >> >> Are there some good options out there for ES5 frameworks that are likely >> to continue into the future? Please advise. >> >> Thanks. --dawn >> >> On Monday, July 20, 2015 at 3:18:17 PM UTC-5, Mark Volkmann wrote: >>> >>> I recommend starting to use ES6 now with Angular 1. You can use Traceur >>> or Babel, both excellent transpilers. Automate their use with gulp or >>> Grunt. Both can watch for code changes made by any editor/IDE, transpile on >>> the fly, and reload the web browser where the app is running. >>> >>> I don't think the learning curve is very steep for the basics. Start >>> with arrow functions. Add in things like destructuing, default parameter >>> values, and enhanced object literals. Then learn about new new class >>> keyword. You'll be in much better shape by the time Angular2 is ready for >>> production use. >>> >>> On Mon, Jul 20, 2015 at 3:08 PM, Dawn Wolthuis <dawnwo...@gmail.com> >>> wrote: >>> >>>> I would like some help understanding where ES6 fits in the Angular 2.0 >>>> picture. It is not yet "perfectly clear" to me whether folks who will are >>>> learning Angular 1.4 today with ES5 will be compelled to learn ES6 in >>>> order >>>> to transition to Angular 2.0. I have heard (here, I think) that it is not >>>> required, but I have also seen no evidence that there will be a lot of ES5 >>>> materials for those doing Angular 2.0 with ES5 in the future. >>>> >>>> Given that some folks moving to Angular 1.x today are highly proficient >>>> in other non-OO programming languages but have little to no OO experience, >>>> I would prefer that they could learn ES5 and keep going with that in a >>>> transition to Angular 2.0. I would definitely prefer that I could at least >>>> tell them this is likely a wise scenario. ng-1.x/ES5 -> ng-2.0/ES5 -> >>>> (someday maybe) ng-m.x/ES6. >>>> >>>> I am hopeful that we can decouple Angular 2.0 training and migration >>>> (in the future) from ES6 training and migration -- preferring to put off >>>> the latter indefinitely or at least until it can be expected to run in the >>>> browser. However, we do want the wealth of training materials available in >>>> videos etc from the web for our Angular 2.0 training. We would like to use >>>> commonly accepted approaches for this development. At this point, it seems >>>> that most (all?) examples have the two tied together -- the developer must >>>> leap from Angular 1 to Angular 2 while also jumping through OO hoops to >>>> adopt OO patterns (for no highly apparent reason -- perhaps it is the >>>> notion that after a half-century of developers writing applications >>>> without >>>> OO, it is now essential in any language or else that throwing everything >>>> into one language is better than keeping it simple?). [I might not really >>>> be a snarky person outside of my Angular 2.0 distrust, smiles.] With a few >>>> exceptions, as someone else here mentioned, ES6 solves a problem that does >>>> not currently trouble us. It introduces a problem that does -- lack of OO >>>> experience by some, not all, LOB developers. >>>> >>>> Please help me understand whether it will be wise to couple Angular 2.0 >>>> with ES6+transpiler, rather than coding in the same language we must debug >>>> in within the browser. Obviously, a developer would then need to >>>> understand >>>> both ES6 (for the source) and generated ES5 (which will run in the >>>> browser). >>>> >>>> Please clue me in on a) whether ES6 will, for all intents and purposes, >>>> be required in a move to Angular 2.0 b) whether it will be more difficult, >>>> perhaps due to lack of materials, for a site to move from Angular 1 to 2 >>>> without also moving from ES5 to 6 and c) whether you think that it would >>>> be >>>> wise to bite the bullet and do the move from Angular 1 to 2 and from ES5 >>>> to >>>> 6 all at the same time. >>>> >>>> Thanks. --dawn >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "AngularJS" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to angular+u...@googlegroups.com. >>>> To post to this group, send email to ang...@googlegroups.com. >>>> Visit this group at http://groups.google.com/group/angular. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> R. Mark Volkmann >>> Object Computing, Inc. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "AngularJS" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to angular+u...@googlegroups.com <javascript:>. >> To post to this group, send email to ang...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/angular. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > R. Mark Volkmann > Object Computing, Inc. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
