> but hey, my Amazon or Spotify experience rocks and delivers great value.
They won't if there are no more good books to read/music to listen to, because the gains aren't worth the effort that goes into producing them.
I don't think danger is books or music disappearing, but that the quality goes down, as the incentives for authors/musicians/composers to invest significant time and effort producing high quality work are reduced.
This particularly applies to the 'avant-guarde' works which push the envelope creatively/intellectually, but typically don't correlate with high volumes.
Angular doesn't do this (batch DOM updates) - but because Angular's $digest cycle is a batch, it's fairly close (or at least, less bad than Backbone's default behaviour).
Dirty checking and watch execution happens in batches, but the resulting DOM updates are executed ad-hoc within each batch iteration - without any regard for requestAnimationFrame or forced synchronous layouts for instance.
the two best features of Typescript's type system IMHO are:
- structural typing for interfaces (which means that classes implicitly implement an interface if the definitions match)
- gradual typing (mainly the ability to convert between 'any' and other types implicitly, which makes it much easier to interact with JS libraries/port JS code to Typescript.)
More generally speaking, Typescript aims to solve the problem of maintaining large codebases by giving you the additional security of static typing. The idea is that many simple errors can often be caught by a compiler, but would be much more time-consuming to find otherwise.
AFAIK Typescript is level 1 gradual typing. Typed Clojure is also level 1, but I'm aiming for level 3.
I guess Typed Clojure is more powerful than Typescript in a few ways, but it's more about how well the type system fits the language. I've never used Typescript, but it seems to fit nicely, with interesting tradeoffs.
Definitely not 'widely' but there are a few library implementations out there.
I reckon that the reason for this is that it's most useful when the interactivity is high (i.e. there are a lot of events to react to), but most applications (desktop, web) don't have a high enough number of events to make learning a new paradigm 'worthwhile'.
we[1] are a fintech startup based in london... There are a couple of others too - Seedrs are based in Shoreditch, MarketInvoice is in W1, but a few of the others are slightly further out (e.g Nutmeg is in Vauxhall from memory, we're in Crouch End.)
Edit: a few I forgot - and I'm surely missing several more - Zopa (W1), Abundance Generation (W12), and of course - Wonga (W1)...
A nice JS library for reactive programming is Bacon.js - https://github.com/raimohanska/bacon.js - it's smaller, the source code is easier to read and I found it a little easier to use.
They won't if there are no more good books to read/music to listen to, because the gains aren't worth the effort that goes into producing them.
I don't think danger is books or music disappearing, but that the quality goes down, as the incentives for authors/musicians/composers to invest significant time and effort producing high quality work are reduced.
This particularly applies to the 'avant-guarde' works which push the envelope creatively/intellectually, but typically don't correlate with high volumes.