Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aseipp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
271.
▲
by
aseipp
2y ago
Here is an incomplete paper that gives a 50,000ft overview: https://www.chromium.org/chromium-os/developer-library/refer... The average Linux desktop does not even come close to having a design as thorough as this
272.
▲
by
aseipp
2y ago
> all details are in the paper. > However, if you read Yeah, no, that's not going to happen on this site. Why would people waste their time actually reading the paper? That takes too much effort and that's time you could h
273.
▲
by
aseipp
2y ago
That is correct, and I should have been more, clear: when I say "Buy them" I mean direct sales of the hardware from seller to buyer. I am not referring to cloud compute style sales. Yes, they have been offering TPUs through Google
274.
▲
by
aseipp
2y ago
Yes, and now after years of doing that Groq is pivoting to being a cloud compute company, renting their hardware through an API exactly the same way Google does. Building out your own vertically integrated offering with APIs is comparativ
275.
▲
by
aseipp
2y ago
Yeah, Secure Boot/Measured Boot is also needed to resist against persistent compromise in the virtual world, which is arguably much more problematic and has a much longer history of actual application in the wild. Chromebooks for examp
276.
▲
by
aseipp
2y ago
People constantly bring this point up every 2 weeks here, the cost competitiveness of TPUs for Google comes exactly from the fact they make them in house and don't sell them. They don't need sales channels, support, leads, any of
277.
▲
by
aseipp
2y ago
Because you're thinking of it backwards. Users have known for decades that they can click an icon, a window will appear, and that's the "application" they're interacting with. This is culturally ingrained as the bas
278.
▲
by
aseipp
2y ago
Interesting. But yeah, even with a very small number of tools, what ends up happening when you just kitbash them together is that the only way to truly understand the dependency graph and build requirements is "Be the person who wrote
279.
▲
by
aseipp
2y ago
The build system is a key component. If you are working primarily in one language with one set of consistent tools that work together, then you can likely get by with just using whatever tools your language offers. Apparently, people have g
280.
▲
by
aseipp
2y ago
Yes, you can buy Ampere Altra systems; you can get a 128 core (2.6GHz) + mobo bundle for about $2.5k USD, and it should be "SystemReady" which is a fancy term for "boots generic UEFI images": https://www.neweg
281.
▲
by
aseipp
2y ago
I mean, to be fair, if you're fiddling with/invoking cl.exe manually then you'd need to know a lot of the general equivalents and nits listed here. MSVC's debug build will do a lot for you out of the box though which is
282.
▲
by
aseipp
2y ago
I'm glad to know that authoritarian policing and throwing innocent citizens in jail under false pretenses is actually the fault of the dirty conniving Chinese. I was getting worried for a minute there, because it almost seemed like we
283.
▲
by
aseipp
2y ago
Saying "elevated voltage causes damage" is not attributing blame to anyone. In the very next sentence, they then attribute the reason for that elevated voltage to their own microcode, and so it is responsible for the damage. I lit
284.
▲
by
aseipp
2y ago
The benchmarks on GitHub use the N300 which has 2 chips per board with 4 boards in the system -- that's the "2x4" they refer to -- with each board being 1400 USD. So that's only $5.6k to match the system they sell, versu
285.
▲
by
aseipp
2y ago
The Loudbox is $12k USD, you can see the pricing right above the specs/description: https://tenstorrent.com/hardware/tt-loudbox
286.
▲
by
aseipp
2y ago
CUDA lives in userspace; this kernel driver release does not contain any of that. It's still very useful to release an open source DKMS driver, but this doesn't change anything at all about the CUDA situation.
287.
▲
by
aseipp
2y ago
You can just use Nouveau and NVK for that if you just need workstation graphics (and the open-gpu-modules source code/separate GSP release has been a big uplift to Nouveau too, at least.)
288.
▲
by
aseipp
2y ago
This looks kind of small and homely and is obviously designed to appeal to a certain niche, which is nice. But the problem with a lot of "alternative code hosting" tools like this, IMO, is that they aren't actually that good
289.
▲
by
aseipp
2y ago
Yes, I should have been more explicit: the raw WASM proposal only really defines how shared memory and cross-thread atomics work where it's assumed each thread runs a wasm module (with shared memory regions that are appropriately mappe
290.
▲
by
aseipp
2y ago
Yes, but they're very close to being standardized and have multiple existing implementations among different browser engines and also non-browser runtimes. (Of course, I don't think the threading proposal is exactly what OP had in
291.
▲
by
aseipp
2y ago
Jujutsu supports using Git repositories as the underlying repo format, in fact you can even run most of your `git` commands in the exact same repository -- and it is otherwise unnoticeable to anyone beyond yourself, barring customized setup
292.
▲
by
aseipp
2y ago
Things like logs are just generally ignored in gitignore so they can just be there or whatever. In practice this hasn't been a huge problem for me. Hacks/workarounds/etc are actually pretty easy to handle and there are a coup
293.
▲
by
aseipp
2y ago
There isn't an "explicit" staging area in the sense it's a separate semantic concept that is distinct from a "commit"; rather, the provided machinery for working with commits can be used to do all the things yo
294.
▲
by
aseipp
2y ago
Following up late to this, but, broadly speaking: we mostly just haven't added these features because users haven't asked for them and we haven't otherwise gotten around to it. That's basically it. They would all be usef
295.
▲
by
aseipp
2y ago
Sad news, I've learned a lot from some of his old course notes and would come across papers coauthored by him. Take care Arvind, I'll write some Bluespec this week in your honor!
296.
▲
by
aseipp
2y ago
The JH7110 is a superscalar quad-core dual-issue design at 1.2GHz and has 2MB of L2 cache. The Core 2 Duo P8600 from late 2008 (around the same era you can buy Coreboot-able Thinkpads like my old X200) has dual 2.4GHz processors with 3MB of
297.
▲
by
aseipp
2y ago
The JH7110 is a multi-year-old SBC that is slower than a Raspberry Pi 3 is. It does not have many extensions for things people today take for granted (no hardware crypto for instance is in practice a massive loss.) So, if you're OK wit
298.
▲
by
aseipp
2y ago
> conversely, relying on a git tag of "v1.2.3" from a random Github repo could be anything at any point. I don't know of a single modern build tool that can do this but doesn't require or record this information speci
299.
▲
by
aseipp
2y ago
FWIW, there are working and usable ports of EDK2 to the RPi4 (not sure about v5) so you can just throw the image on an attached USB drive. The FSBL then boots the EDK2 image, which can then load a generic UEFI image like normal. I used that
300.
▲
by
aseipp
2y ago
I don't understand what you're suggesting. ChromeOS has an extensively documented threat model and it is, quite unarguably, vastly more intimate and well defined than any comparable desktop solution in the FOSS world. ChromeOS als
More ›