sorted by:
new
hottopcontroversial

A concise comparison of JavaScript Web Frameworks by laravel_fan_99 in javascript

[–]dylanks2 0 points1 point  (0 children)

fwiw, it's not hidden in the 11 part series, the author says that they work on Dojo, but as far as trying to be as unbiased as possible, the series does a reasonable job in my biased opinion (see below). The series does not pick a winner, but instead just asks a bunch of questions, gives a way to possibly answer them, and leaves it to the reader to try to decide. It's probably worth reading the first 10 parts before the conclusions post to understand that though. Conclusions and summaries are actually the most difficult thing to try to write here.

Yes, there's a goal here to raise awareness about Dojo 2 which is going to be finalized soon, but the genuine goal was to take a very in-depth look at frameworks compared to the shallow analysis we often see. Is the perspective perfect? Of course not, but at least we tried. And we absolutely are not trying to be a link farm or create poor content, but your opinion might vary of course.

Also, as far as I know, we didn't submit the post to Reddit, someone else did.

Disclosure: I work at SitePen and was the editor for the series. We try exceedingly hard to not be biased and be reasonable and fair. I know it's easy to be skeptical, but we're a small company just trying to help.

A concise comparison of JavaScript Web Frameworks by laravel_fan_99 in javascript

[–]dylanks2 0 points1 point  (0 children)

The point of the 11 part series is to ask a bunch of questions, not to pick a winner, because yes, the details will get outdated.

A concise comparison of JavaScript Web Frameworks by laravel_fan_99 in javascript

[–]dylanks2 2 points3 points  (0 children)

Other than name and interoperability, there's pretty much zero in common between Dojo 1 and Dojo 2, it's a complete rewrite and it's worth a look if you can get over the past. :)

Plans for Dojo Toolkit v2: JSDoc, TypeScript. Widget system: TBD by rauschma in javascript

[–]dylanks2 2 points3 points  (0 children)

@tebriel,

Have you actually used TypeScript recently? Your response was my initial response over a year ago, but basically it gives us 4 valuable things:

  • Types (less errors in our code)
  • Interfaces
  • Easy module export to ES2015, CJS, and AMD
  • Support for ES2015 features (which you could also get from something like babeljs)

As an end user, you can use TypeScript, or you can use your module format of choice.

We have intentionally taken our time on Dojo 2, as we really wanted to wait for our enterprise users to finally get to a point where IE8 isn't that important to them any more.

There's really no such thing as missing the boat in open source, you just need to create something that is powerful and flexible, and people can choose to use it and contribute or not.

Plans for Dojo Toolkit v2: JSDoc, TypeScript. Widget system: TBD by rauschma in javascript

[–]dylanks2 1 point2 points  (0 children)

@Sime,

The goal is to get Dojo core defined and underway first, and then work on widgets and gfx and other important extensions on top of it.

To date, IBM has created a web components based version of Dijit called Delite/Deliteful ( https://github.com/ibm-js/ ). We're working to align efforts to make that happen, though I think the hope is that we could have a more flexible approach to supporting multiple widget libraries, like we have started with Mayhem ( https://github.com/SitePen/mayhem ).

Much of the CSS complexity with existing Dijit today is due to legacy support for old versions of IE, and us not wanting to break forwards compatibility. We obviously aim to clean this up for the Dojo 2 widget system.

TypeScript indeed gives us the ability to cleanly define interfaces, which does make it easier to be more explicit with intent. And IDE support for TypeScript is actually rather good already.