In Phoenix, Arizona, there are solar panels over the parking lots at since of the grocery stores. Makes a huge difference in survivability when you get back to the car.
(Without huge infrastructure dedicated to car welfare, Phoenix is uninhabitable.)
It's car optimized because the 110F weather makes it un-walkable in the first place. When I lived in a walkable city, I would prefer to walk 30 minutes than drive. When I lived in Phoenix, I did not want to spend more than 30 seconds outside in the summer.
You can always start small and over decades grow the area. After all that is how cities like Copenhagen and Amsterdam became bike friendly, not just a few years, but decades of work.
As a fellow European: we're prone to underestimating how uninhabitable bits of America are that nonetheless have people living in them. Those are port cities and therefore stable and temperate. You cannot green Arizona.
Just FYI there's a lot of ways to re-green a desert without actually being wasteful with water. There's some really impressive case studies out there. Shaping the land with berms and swales, building walls of trees to prevent water from being leached away by the wind, etc.
100F days are fine, cakewalks, even, especially with misters + shade. We had 70+ days of 110°F two years ago, and over 20 days 115°F+. They are not the same. Those days are unbearable nightmare fuel, and worse, they turn into insanely miserable nights where the low temperature rarely dips below 95°. It is absolutely awful, dry or not.
Phoenix as well as other similar places (such as Las Vegas where I live part of the year) have an outsized benefit from installing solar compared to normal places. We basically never have to deal with rain or clouds. Installing solar here is a total no-brainer.
25 years ago, I configured GNOME to run a BeOS-like tabbed window manager. On a sun workstation.
But that's not what this is. Or not only:
Nexus Kernel Bridge
Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style node monitoring, device tracking, and messaging to Linux — making it possible to run Haiku applications on a standard Linux kernel.
It claims to run apps from Haiku, the current open-source implementation of a modern BeOS.
Looks like this is a thin translation layer for BeOS/Haiku syscalls. I wonder why they aren't relying on Syscall User Dispatch https://docs.kernel.org/6.19/admin-guide/syscall-user-dispat... which would enable them to put this compatibility layer in user space. It's already being used by recent Wine versions.
It's not really a translation layer, nexus implements the same BeOS/Haiku IPC in kernel but using linux kernel primitives.
It's not as much as a translation layer than any other IPC in the linux system, really BeOS/Haiku apps are first class citizens.
Most of BeOS IPC is in mainline Linux kernel [1] - the difference here seems to be implementing some of the services that are supposed to be available related to filesystem etc and the user land side of it (raw IPC does very little without another layer on top)
[1] - there's a reason why a bunch of BeBook reads the same as some of the oldest parts of Android documentation
BTW because that would not solve any problem for us, the technique you're linking can be useful only if what you want to achieve is binary compatibility otherwise it's useless. That's not really what we are after.
It's almost as if no healthcare legislation gets passed before private insurers have figured out how to extract shareholder value.
(Which makes the system worse. The fiction of a fiduciary responsibility to extract top dollar from a business regardless of consequences is the opposite of "capitalism". Which derives its name from the practice of sound investment to build something of lasting value.
To say nothing of the social deviance of for-profit healthcare.)
I think a read cache device gets set up like RAID0, interleaved reads rather than redundant data.
Examples of auxiliary devices where you want redundancy: there can be a write cache (the ZFS Intent Log, or ZIL). You can also dedicate a fast device for hot items like the deduplication tables, or a dedicated device for tiny files where data can be stored directly in the directory data, rather than allocating a separate data block.
Although the lede suggests that this is about the consequences of healthcare costs in the United States, the research is from Denmark.
Even so:
Denmark has a universal healthcare system, [not] massive healthcare bills that usually ruin people's lives in the United States. Yet, the researchers suggest that economics still plays a big role... Patients who showed the steepest income declines had the strongest links between cancer and crime.
While the original OS X display model, Quartz, evolved from Display PDF via NextStep, I believe that it shifted back to pixel rasterization to offload more of the display stack onto the GPU.
Quartz Extreme?
John Siracusa, Ars Technica:
It's possible that existing consumer video cards could be coerced into doing efficient vector drawing in hardware. Apple tried to do just that in Tiger [note], but then had to back off at the last minute and disable the feature in the shipping version of the OS. It remains disabled to this day.
(Without huge infrastructure dedicated to car welfare, Phoenix is uninhabitable.)
reply