6SixTy

There's something to be said that mass production is another distinct stage of invention. Karl Benz may have invented the first internal combustion engine car, and plenty more built cars by hand for the rich, but Henry Ford made cars anyone could have for cheap.

That's a comical amount of pennies

$1M to the US Government is like dropping pennies, less than that actually. By the READMEs, this font is actually a modification to another font and more sleuthing revealed that the author actually worked on this in his spare time.

Part of making a typeface is making it subconsciously part of the brand. Though there's precedent for making a functional font in this use case as Airbus designed B612 for readability within their glass cockpits.

Considering that the support tier where you get access to the testing suite is 150K/year, I don't think they will be spilling any beans soon.

I remember a video where the only thing that stuck with me was that the guy was working on his English skills, and used an AI voice. That's not abnormal by any stretch of the imagination nor memorable, but how he edited the AI voice made it about as natural as a normal voice.

They are basically acquiring talent and/or preexisting IP. RISC-V is free but implementations are the sole IP of the company.

Implementing ARM and RISC-V decoders might depend on licensing fine print for each licensee

Why assume that a game has to be made? Making a handful of tech demos doesn't come with that baggage and deflects criticism of making an empty shell of an engine with nothing to speak of.

Microsoft offers Windows on ARM servers. Could slam the Windows ARM ISO on a 3rd party VPS as well.

Ford's big mistake with the 1.0L Ecoboost wasn't exclusively using a timing belt, it was using a timing belt submerged in oil. They did state that they engineered the rubber to withstand being submerged in oil, but ultimately it didn't really work out like they had hoped.

An interesting fact is that the first gen US Honda Odyssey minivan completely lacks slide out doors commonly associated with the vehicle type.

Apple's GPTK only supports D3D12 -> Metal. In addition, it's ambiguous if 3rd parties can distribute the D3DMetal dylib, as there's no license.

Main issue is the lack of Vulkan support on macOS. Currently, solutions like MoltenVK have to be developed to add Vulkan support, which isn't as clean as just supporting it.

For some reason the prospect using Wine, Rosetta 2, and DXVK with MoltenVK on top just to run some games doesn't inspire a lot of confidence that this whole thing will be performant and/or stable.

Not a fan of how this car would work ergonomically. Center mounted speedo is annoying and there's zero attempt to prevent glare from them. I also can't tell what's going on with all of the switches on the passenger's side and the handbreak.

My take is that it could help tie up fragmentation. RISC-V has different profiles defining what instructions come with for different use cases like a general purpose OS, and enshrining them as an ISO standard would give the entire industry a rallying point.

Without these profiles, we are stuck with memorizing a word soup of RV64GCBV_Zicntr_Zihpm_etc all means

There is and kind of isn't. There are community led modding apis, but also datapacks that are more limited but still allow someone to do cool stuff leveraging tools, items, etc already in the game.

If you remember entire contraptions of command blocks doing stuff like playing Pokemon Red in Minecraft or "one commands" that summoned an entire obelisk of command blocks, the introduction of datapacks pretty much replaced both of those.

If you read the LKML thread with Linus' rant, you would know that big endian ARM* is a problematic part of the Linux kernel that the maintainers are removing due to lack of testing let alone receiving bug fixes. It's also implied that big endian causes problems elsewhere beyond ARM, but no examples are given.

Later on in the thread, Linus states that he has no problem with historically Big Endian architectures, it's just that nothing new should be added for absolutely no reason.

*ARMv3+ is bi endian, but only for data, all instructions are little endian.

The rundown on this is that CodeThink added Big Endian RISC-V because of a half-baked optimized networking scenario where somehow the harts (RISC-V speak for a cpu core) don't have Zbb byte manipulation instructions. Linus shuts down efforts made in mainline Kernel (!!) because these issues are extremely flimsy at best and don't have technical merit for complicating the kernel's RISC-V code and already extreme RISC-V fragmentation.

I've looked at more reasons that CodeThink came up with for Big Endian RISC-V, and trust me, that's the best that they have to present.

The move to 48v is very much about efficiency within the harness backbone. For the same wattage, less amperage is needed in a higher voltage system, meaning the wires can be smaller and they produce less waste heat.

There are a few different topologies for a 48v harness, but somewhere in the line there's a 12V DC/DC converter in there somewhere.

12v is easier to adapt and take parts off the shelf. Remember that EVs weren't quite obviously the future at some point.

I have to wonder if this ever happened with the 6v to 12v transition somewhere in the 50's-60's

macOS has like no features already, and they keep removing more.

Chemotherapy is essentially a bet that the drugs will kill the cancer faster than you. Because ultimately, cancer isn't a virus, bacteria, fungus, parasite, nor even a prion (this one is nightmare fuel) -- it's your own cells acting as a parasite. This reason alone makes cancer horrific to treat as it is.

ReactOS right now focuses on Windows XP era hardware and compatibility, also not guaranteed to work outside a VM.

Not even 60GHz. We're talking 2.4/5 here

Don't completely rule out EBCDIC from the equation. It's generally an IBM-ism meant for punched cards with the same characters as ASCII. Despite the similarity, it means that it's a legacy system kept alive to now and switching to UTF-EBCDIC would likely incur disturbing 70+ year old layers of tech debt dust. Some of them don't even support lower case characters as it's using EBCDIC's predecessor, BCD.

RDP is functionality that has to be built into the compositor, rather than a pretty integral part of X itself. WSLg (Windows Subsystem for Linux [2] GUI) works via RDP, and it's Wayland only too.

KDE Connect is honestly just that but better in some respects. And honestly, it's great.

Just looked through my TV, webOS uses Busybox.

When that book was published, the F-117 Nighthawk was already retired after 10 years in service. The thing doesn't even look like it could fly on account of the rudimentary stealth features.