Disclosure: I am one of the developers of Tailor.
We would have loved to write Tailor in Swift, however (at the time of development) using the industry-standard ANTLR parser generator was the most feasible and straightforward way to develop a cross-platform tool without having to reverse-engineer the previously closed-source and proprietary SourceKit infrastructure.
Facebook also came out with a storage interface and state management library that is used to manage unidirectional data with a backend called Flux https://facebook.github.io/flux/
And a lot of the cool kids these days are using a Flux-like state management system called Redux -
http://rackt.org/redux/index.html which is roughly based on the immutable patterns from Haskell/Elm.
If you have significant resistance to upgrading from Windows XP or IE8, then you need to charge more for your product. Let's face it, maintaining websites on older browsers that have poor standards support is expensive.
I maintain such a web application myself. I work primarily on OS/X as my main development machine, and run various windows versions in virtual box in order to test these older browsers. Since the feature is usually completed using modern browsers up-front, there almost always a QA glitch that has to get worked out on IE8, chewing up another 20-30% of the total time of the project. Time that costs everyone in the business time, energy and pain. Think about that; 30% of the cost of development to support < 3% of the users.
When the large web companies like Google and Facebook remove support for these legacy browsers, every web developer on Earth cheers. Every instance of IE8 that is snuffed from existence is more time we can spend on creating great software features, and not wasting time back-porting.
MS IE11 is a pretty decent browser. Has auto-updating, and supports many web standards correctly. It's not perfect, or even better than other browsers, but it's a beginning. Now we just need Microsoft to sunset everything before IE11, and save the web development world $Billions.
If AT&T, Comcast, Verizon and other ISPs are intentionally limiting bandwidth to certain content providers, as the measurements seem to indicate, they may be actually doing us a favor. By doing this, they are causing people to discuss the issue and eventually lead to market changing trends or new regulations and potential legal hazards for ISPs that do this in the future.
If anything, Amazon is a smart company, there might be an opportunity here for last-mile internet delivery...Amazon Fiber Prime anyone?
Or, you could refer to the product you're interested in buying, as they can provide information about how well different internet providers can service their product:
1. Microsoft is cheap. SSL/TLS encryption of content requires a little more processing power.
2. The Bing API doesn't support HTTP/S. Could be a JSONP limitation.
3. Conspiracy Theory: Microsoft wants to fill up NSA's snooping storage archive, so they can sell them more Windose and SQL servers.
Right? I would appreciate an in-depth root cause analysis report on why it failed, mitigation steps and final solution. I'm sure such a document exists somewhere...
Coming from Backbone and not really spending any time with either Ember or AngularJS; It seems to me that Ember adopts a more Backbone-like approach to managing Model changes. If only Javascript had a missing method dispatcher, these types of accessor syntax differences would be moot.
