techenthusiast

Yeah. And if you wanted to virtualize Android apps...

How does that article in any way compare in rigor to the most famous paper on the US housing crises?

That article literally gets supply and demand wrong...

Because there are numerous network effects* for specialized concentration of labor.

*Network effects are unfortunately only understood as a handwavey buzzphrase in tech, but they have been researched and defined in extreme detail by economists. Think non-ergodic math.

YES.

Seeing an NBER paper on Hacker News of all places makes me want to cry tears of joy.

That zoning and insane levels of regulation are absolutely the causes of the housing crises in the US is the mainstream consensus among economists.

For those unfamiliar, Glaeser is widely considered the foremost urban economist, so I'm shocked to see his famous paper linked on here. He's absolutely brilliant.

The graph is apparently derived from John Hennessy's latest textbook revision.

Probably an ASIC with int8 and lots of SIMD? Beyond that, ¯\_(ツ)_/¯

If there's sufficient interest, would like to write more about foundry in the future. It's an educational problem because almost no one writes about these things on the internet.

Well, the OS is most strictly the kernel, right? It's honestly all together. It's an SMP system that you can already run on normal ARM and x86 devices.

The team has stated that everything in the kernel is true, and that there's quite a lot there to infer from. What they can't say publicly is the how and why, e.g. how would they hypothetically implement backwards compatibility with Android apps?

Thanks. Yeah, they really could not be more transparent about that. Most of the bring-up is on mobile + PC silicon as well.

There's no need to kill Chrome OS for the education, mind.

Thanks, but would sooner recommend my third article: https://techspecs.blog/blog/2017/3/15/fuchsias-hypervisor.

TL;DR - Google might run virtualized Android apps in containers on Fuchsia OS.

There's no one repo to point to, but you can at least look at code review for the hypervisor: https://fuchsia-review.googlesource.com/q/hypervisor.

The Android API wouldn't be going anywhere. That's what I say in the article - Fuchsia would continue to support the Android API seamlessly.

You wouldn't have to do it all at once. You'd emulate the Linux user space, and do everything incredibly gradually. Both APIs would be supported for many, many years. But they could stop advancing the Android API within a shorter timeframe.

Extremely, extremely? :) Apple kept Carbon apps running on OS X for a very long time.

That's what I'm saying :) An (extremely) gradual phase-out of the Android API.

Ah, thanks for clarifying. I updated the article to be more conservative about Rust's inclusion.

I updated the article with the following clarification at the top:

I use Andromeda equivalently with Fuchsia in this article. Andromeda could refer to combining Android and Chrome OS in general, but it's all the same OS for phones, laptops, etc. - Fuchsia. I make no claims about what the final marketing names will be. Andromeda could simply be the first version of Fuchsia, and conveniently starts with "A." Google could also market the PC OS with a different name than for the mobile OS, or any number of alternatives. I have no idea. We'll see.

I added an Update section for anyone wondering why it looks like Andromeda really is the same as Fuchsia.