If you're really Steven Sinofski, pretty damn amazing to see you on hn. Watching you introduce Windows 8 at build two years back, I couldn't have ever imagined seeing you post on hn or any other discussion forum for that matter.
I think there's a page or two that describes what the jsx transformer does(which is it converts them to React.DOM elements IIRC). I think that's where I learnt that you could use raw JS functions instead of jsx, even though it said that jsx should be preferred or something to that effect.
It's not so remarkable considering the IITs aren't a single university. They are dispersed across all of India which is a fairly large country geographically.
Also the fact these three people come from India isn't that remarkable considering that there are 1 Billion people there. Now if they were from some small developing country like say Sri Lanka or Bhutan, it would be really impressive.
> Angular has a void with the lack of a useful enough eventing solution - $scope eventing ...
I've found that using a publish/subscribe system for communicating between components makes them more loosely coupled and modular. In most cases, the components I've written are naturally somewhat slightly coupled so I just pass around functions as props from parent to child components.
> HTML mixed in with JS via JSX is also an abomination ...
Totally agree. I use the default React.DOM elements instead. I find them more transparent and easy to read, and manipulation of these are much easier using the map, filter, folds etc.
We're not saying Angular's bad, just that React's approach is better :) I've tested both (and quite a few other MVVM libraries actually) before I came to this conclusion.
Of course, I gain nothing by someone choosing Angular over React or vice versa. I'm just sharing my experience and leaving them to make their own choice.
If you're using something like Angular, Ember or React, it's safe to assume that you'll be building a Single Page Application with the majority of code in Javascript. So evaluating libraries for stability, functionality etc is time well-spent, not wasted.
While it is true that there are far too many frameworks that come and go in JS land, you can find very stable, well-maintained and clean libraries too. For anything that's essential to your stack(DOM interaction, routing, UI elements etc), typically you'll find multiple well tested and stable libraries. Atleast, that has been my experience.
With well designed libraries, integration is rarely a problem. They are designed to be interoperable and don't make too many assumptions about things they aren't good at.
It takes a little bit of work upfront, but I find it's far better than relying on monolithic frameworks that tries to do everything under the sun(and usually fail).
Switch to React, I guarantee you that your front-end dev time(and overall) dev time will drop drastically to 20% :)
There are tons of javascript libraries that are out there that offer the things you want. In most cases, they are more featureful and more stable than Angular's implementations.
Router - Backbone's router, page.js etc
Web service querying - simple jquery ajax calls or you could use breeze.js, pouchdb etc
Unit testing - React has one built in, but you could use others too.
Not to mention, it's much simpler than Angular. You can get upto speed with React in 2 or 3 days. Once you make the shift to specifying single states for your interactions and letting React rebuild the DOM on changes, you'll never go back to anything else.
Alan watts' writing is exemplary. The thing I like about his writing is that it's written with an outsider's perspective and critical thinking is never discarded unlike most other books on eastern philosophy. I highly recommend his book "The Joyous Cosmology" where he talks about psychedelic experiences and their effects on spirituality.
They're either related to Jetbrains in some way or really lack creativity or maybe they're trying to unduly profit off the good reputation Jetbrains generally has in the community.
While that is true, why would you assume that the poster bought the phone for that reason? He might have bought the phone for any number of reasons such as the low price, decent specs etc.
Depends on what you want to do with it. If you're looking to develop mobile or desktop applications it's almost useless. The desktop GUI is stuck in the 80s and as far as I know even that isn't an option for mobile.
If you're doing web apps, it's probably worth a try provided you don't mind writing your own libraries for a lot of stuff.
Zen philosophy stresses on going with the flow and accepting things as they are. You could argue that Kobun did hit a target even if it wasn't the one the audience (or himself for that matter) anticipated.