So I wonder if what the article is pointing at wasn’t actually the inability of merging iOS and MacOS fully more than anything.
1,499 karma · joined April 19, 2014
https://twitter.com/clehene
So I wonder if what the article is pointing at wasn’t actually the inability of merging iOS and MacOS fully more than anything.
First, it can’t have an exact length because it’s not a static thing, but a process. Second, as opposed to fractals that can be zoomed in forever, our measurements seem to hit some limits, so the reality is not quite like fractals in this sense.
Of course, it all makes sense if you think about it. What’s perhaps more interesting is we can’t “really measure” anything absolutely and the whole idea of absolute measures becomes rather tricky once you get to physics. In fact it gets philosophical and disputed and you realize that nothing is quite certain, nor quite agreed upon.
I think Quanta Magazine does a good job making justice to these things though.
> Overall, the work lacks a self-consistent and transparent accounting of resources, making its central claims difficult to substantiate and leaving a strong sense of sensationalism and hype, rather than honest scientific exposition.
"Clowns to the Left of Me, Jokers to the Right"
Yet, in general the correlation between results "on paper" and results in practice is over a long period of time, if any.
It doesn't mean that new results aren't good, just that they may not translate into something practical very soon.
E.g.
4 days ago (same paper) https://www.reddit.com/r/science/comments/1s2bjqp/a_new_hafn...
3 years ago https://www.reddit.com/r/singularity/comments/14d1dt5/why_ar...
5 years ago https://www.quora.com/Would-it-be-worthy-to-use-memristors-t...
Do you feel like software transcends pyhsics, mathematics and logics? Because that's what the statement translates to.
The only reason it's impossible, is because nobody tries, because trying to do so would interfer with the deliverables of next sprint. The software industry has painted itself into a corner.
Why are the abstractions leaky? Are all abstractions leaky? Why - we simply accept the situation without spending any real effort.
"There's no free lunch" - this is representative of the level of argument in software circles entirely. But WTF does that mean? If the lunch is not free, how cheap or expensive can it get and why?
This is why, as engineers, we tend to brush off the Dijkstras as arrogant, while at the same time ignoring both our arrogance and ignorance.
My own incomplete opionion is that the net effect is that we ended up writing orderd of magnitude more code than necessary to solve the problems at hand. It's the equivalent of doing the computations manually instead of using a calculator. This has led to an industry that has served us well, but strictly speaking it was never necessary and much more could have been achieved with a fraction of the resources.
I was in high school and was running a "computer games club" (~ Internet cafe for games and kids) since 1998 when we got a place, renovated it ourselves, got custom built furniture (cheap narrow desks) and initially 6 computers - AMDs at 300Mhz. By 2000 we broke a wall in the adjacent space and had ~15, cable + satellite internet for downloads and whatever video cards we could buy or scrap. It was wild.
There are exceptions, though, like Mercury, which expanded to consumers after having success with their business banking product.