As much as I enjoy a good chat about languages, that was not the purpose of this thread, although I know I mentioned that JS fit a project better than TS right now. If someone wants to start a new thread regarding languages that meet Grace Hopper's criteria of sounding close to English (perhaps we have apps like Siri for that as the programming industry went a far different direction!), or languages that give you enough rope to hang yourself (basic, js, cobol, ...) compared to languages that hang you themselves or cause you to want to hang yourself, or whatever else there might be, I might even chime in. Right now I would be happier to accept any more comments in this thread that are more directly related to the original post.
I now have advice from several sources and am leaning toward Sander's advice of choosing option b, upgrading to 1.4 before we dive into the rewrite, continuing to use ui-router. The second most popular response from folks I have chatted with is to bite the bullet and convert to the new router before we begin. The folks with that suggestion are far better than I am at coding and can just "toss things in and deal with it" better than I. With what I have seen so far, given I have been happy with ui-router, I am pleased not to have to start thinking like the new router, but that might be overly short-sighted of me. It seems to be yet another paradigm shift for no apparent reason (so I'm glad others are aware of the reasons and trust that they are good ones). I'm hopeful that ui-router will stick around for the conversion to Angular 2, so it might even help with that effort in the future. Is there anyone who can speak in favor of choosing option c and converting to the new router now rather than diving into a significant re-write without learning the new router first? --dawn On Monday, June 1, 2015 at 11:50:31 PM UTC-5, Anton Trapp wrote: > > Language wars. How funny. Hated JavaScript (came from Ruby and this is > still my favorite), with CoffeeScript I can look at it because it does not > look to ugly :) > Yes, some concepts (or the lack of them) show that not the most clever > people invented it yesterday and used all the experience from other > languages to do that. > > But to say a language is bad because people try to make it better over the > years as the intended purpose changes and it gets used by much more people > is silly. Every language that is used and after every new pattern that > proves worthy (DRY, ...) gets it's updates, otherwise it vanishes. > > And I am in the software business for almost 30 years. Saw many languages > and projects. Not a single one failed because of the used language. Some > failed because of people not able to understand how do deal with the > weaknesses of the languages and frameworks. > > And bashing around on something without any proof is just wasting my time. > JavaScript is definitively one of the most important and most used > languages today. Likely because it is unusable and all people who use it > are idiots. > > Really have better things to do. Out of this thread - have fun bashing ;) > -- 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.
