Greg, Interesting comments.
I have to say I started about a week ago learning TypeScript + Aurelia ( http://aurelia.io/) which is an alternative to Angular2 and my experience it's been very very good. Yes, I had few bumps here and there as I need to use Typescript 1.5.3 beta and Aurelia is still in beta as well but I have to say that in less than 2 days of work I build a super crazy & cool UI with with a relative complex ui, lots of interactions, several model, pages, views and so on. I hate JS, I dislike it so much and always found it so hard to code in JS but TS + Aurelia I think they rock together. Compared to Augular2 Aurelia simply rocks and it's so dead easy to setup. My 2 cents from a non JS developer. Regards, Corneliu. On Fri, Aug 28, 2015 at 11:08 AM, Paul Glavich <[email protected]> wrote: > >> JS ecosystem can go to hell. > > Lol. It has been there already. J It re-wrote hell in the form of a > closure. > > > > Seriously though in answer to react comment below, I too find react’s > syntax atrocious. Note that there is nothing at all related to react and > C#/MVC. It is a fast rendering system by way of the shadow dom usage. It > does have a good composition model but I simply cannot stand its syntax. > You give up an easy to read syntax for speed and composability. Flux is a > pattern library that is an augmentation to react that I think is quite good > but could be used without react as well. > > > > It is the new black in terms of frameworks to use though so people are > saying its awesome and everything else is crap, which is kind of the > polarising community of JS dev. It is only at version 0.13.3 so it is so > immature I would not entertain it at this time, but many are. > > > > - Glav > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Tony Wright > *Sent:* Wednesday, 26 August 2015 12:11 PM > *To:* ozDotNet <[email protected]> > *Subject:* Re: TypeScript summary > > > > I wouldn't mind knowing what is so good about React. I'm not enjoying the > syntax of React so far. At the moment if I was to build a new substantial > app it would be using Angular. I feel that you can write some pretty > substantial applications in Angular. Having had a dabble with React, I > don't get the same feeling, so I am wondering if the hype is bigger than > the product itself? > > > > I know React is more about the V in MVC and Angular covers the entire MVC > pattern in Javascript, but I am trying to understand - are they still > essentially trying to solve a similar problem? I can go without using C# > MVC applications at all (excepting WebApi) with Angular, so is the > difference that React is meant to be used in conjunction with C# MVC > solutions? > > > > > > > > On Wed, Aug 26, 2015 at 11:57 AM, William Luu <[email protected]> wrote: > > RE: DOM manipulation. > > > > Here's a (intro and) comparison between DOM manipulation jQuery and React > > > http://reactfordesigners.com/labs/reactjs-introduction-for-people-who-know-just-enough-jquery-to-get-by/ > > > > On 26 August 2015 at 10:03, Bec C <[email protected]> wrote: > > +1 for Greg's comments. Coming from a sql background I found it relatively > easy to jump into c# and .net but my jump to JS wasn't so smooth > > > > > > On Wed, Aug 26, 2015 at 9:55 AM, Greg Keogh <[email protected]> wrote: > > I hope this is my final essay on JavaScript (and so do you!). In summary, > a few weeks ago I volunteered to write an in-browser script driven demo app > which is simply a navigation stack of 4 screens. Angular is so currently so > trendy I spent several hours attempting to learn and use it, but due to > lack of an IDE, no debugging, no guidance, the custom terse syntax and > complex dependencies I gave up (then I learn it's being rewritten in > TypeScript anyway). I've expressed my anger at the 'zoo' of uncoordinated > and competing JS libraries. > > I spent all of yesterday optimistically studying and trying TypeScript, as > the familiar IDE and structure seemed ideal for someone from a C++/Java/C# > background. Given my belief that the JS world is really chaotic, my overall > conclusion is: > > *TypeScript is organised chaos.* > > I was reminded of moving from C to C++ 20 years ago. C was so freeform you > could write spaghetti. C++ helped you write object oriented modular > spaghetti. Just like that, TS is trying to tame the JS spaghetti and make > it feel OOPish and respectable to people with my background, but it's still > just putting a wedding gown on a pig. > > The good news is though, that once I eventually found guidance on how to > organise multiple TS source files, how to use module { } like namespaces, > when to use the <reference>, and why you use --out to concat files, then TS > is probably the least worst option I've seen so far for writing large JS > apps. At least you will finish up with organised modular chaos. > > So you might be able to tame JS with TS, but we are still stuck with the > cumbersome DOM and jQuery. While trying to give my web page app behaviour I > had to have jQuery reference web pages continuously open so I could > remember the arcane and inconsistent syntax to do the simplest things like > toggling visibility or setting text or class attributes. This isn't really > a JS related problem, but I find manipulating the DOM from JS and jQuery > tedious beyond endurance. > > In fact my endurance is exhausted. I will not write the demo and have > commissioned someone else to do it. They write this sort of thing for a > living, so I look forward to learning how they do it. I've learnt a lot in > recent weeks anyway and have decided that for future work like this I will > use TS and jQuery because they're the least worst (for now), and the rest > of the JS ecosystem can go to hell. > > > > *Greg K* > > > > > > >
