723 karma · joined January 12, 2012
In the case of Angular zones, if additional async APIs are added to the browser, Angular needs to be updated to patch them with its own zone implementation.
This wouldn't break existing sites, but could leave, for example, sites on older angular versions unable to use new browser APIs, use libraries that use new browser APIs, or install security updates to dependencies if newer versions rely on new browser APIs.
https://blog.thoughtram.io/angular/2016/02/01/zones-in-angul...
I can imagine Angular zones becoming problematic in exactly this kind of way in a few years...
We see this most clearly when we look at ideologies that are dominant today. For example, a fairly core ideology over the last 30 years is that more and more aspects of society either should, or inevitably will, be governed by the market. As a result, ideologies that don't subscribe to this this idea are generally viewed as similar no matter how much they might otherwise be unrelated. Which is kind of strange, since 'ideologies that don't subscribe to this idea' amounts to most of the ideologies adopted over the course of human history.
The proportion of Haskell libraries for tasks like string padding is probably lower than the proportion of ruby or js libraries, for example.
You'd be getting neither the benefits of native nor the benefits of cross-platform.
Edit: looks like the tint framework linked above actually isolates the webview from the node runtime. Nice.
This sentence is a fantastic example of why translation is so hard!
> But has anyone proved that markets actually do approximate the (intractable) correct allocation? They could be a very poor approximation or even be actually computing something we don't want.
> They could be a very poor approximation or even be actually computing something we don't want.
Well, it would be wrong to take the market allocation to define the desired outcome, but assuming we have some other understanding of what our desired outcome, we can at least assess whether it performs better or worse at the computation than some other approach, right?
It's interesting also that markets seem to share properties with other sub-optimal approaches to computationally hard problems. Getting stuck in local maximas, for example.
Which is why articles like this are so great. When I was first dipping my toes into development, Mike Ash's articles were a great help in cutting through the marketing hype and realising that these are mostly things you could have implemented yourself given the time and inclination.
setOfAllPossibleStatesOfWorld.every(s => s.app.isRewrittenInNode) && app.rubyVersion.hasReallyUnintuitiveUIPresumably they have access to much better information about the code's intent and future behaviour than the cpu does.
So using obj-c in the kernel might require giving up some of the language's dynamism. Not sure how this was handled in NeXT.
I just wanted to point out that said debate would hinge on more than a narrowly semantic question about the meaning of "man".