Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sedatk
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
241.
▲
Unix v4 tape raw binary image recovered
(elk.zone)
39 points
by
sedatk
10mo ago
|
3 comments
242.
▲
by
sedatk
10mo ago
> People were trying to figure out how to make money off of the Internet from the early days of the Internet being publicly accessible People were doing that even in ARPANET days. The commercial aspect was seen as a strong incentive to m
243.
▲
by
sedatk
10mo ago
Huh, is that why my Steam Deck won't wake up my TV?
244.
▲
by
sedatk
10mo ago
See https://news.ycombinator.com/item?id=46211578
245.
▲
by
sedatk
10mo ago
That sounds quite troublesome if the encryption key is lost, compromised, or rotated for any other reason.
246.
▲
by
sedatk
10mo ago
Ooh a new bug.
247.
▲
by
sedatk
11mo ago
Canada life expectancy (2025): 83.3 years US life expectancy (2025): 78.4 years Alaska life expectancy (2025): 74.7 years https://www.macrotrends.net/global-metrics/countries/can/can... https://ind
248.
▲
by
sedatk
11mo ago
That looks cool!
249.
▲
by
sedatk
11mo ago
I agree with your point, but I must correct you on DOS: it had device drivers too. :) That's how we used to access mouse input, CD drives, network, extended memory, etc. Yes, it sucked on the graphics and sound; every app basically had
250.
▲
by
sedatk
11mo ago
Or you could target .NET Framework 4.8 which is supported by all Windows OSes out of the box albeit quite outdated.
251.
▲
by
sedatk
11mo ago
Microkernel architecture doesn't magically eliminate bugs, it just replaces a subset of kernel panics with app crashes. Bugs will be there, they will keep impacting users, they will need to be fixed. Rust would still help to eliminate
252.
▲
by
sedatk
11mo ago
What yucky politics?
253.
▲
by
sedatk
11mo ago
> But that's easy to fix, so just implementation quirk for this particular library, the idea is sound. It's in ULID spec.
254.
▲
by
sedatk
11mo ago
UUIDv7 is the closest to ULID as both are timestamp based, and UUIDv7 has fewer quirks than ULID, no question about it. I agree that picking UUID variant requires caution, but when someone has already picked ULID, UUIDv7 is easily a superio
255.
▲
by
sedatk
11mo ago
To implement a thread-safe sequential increment, you need locking. When you use locking, then it becomes a “non-universal” ID generator with arbitrary performance impact. Either it’s collision-prone or locking. Both are problematic in their
256.
▲
by
sedatk
11mo ago
Thanks for the heads up, then it’s one less reason for ULID to adopt this weird behavior.
257.
▲
by
sedatk
11mo ago
Yes, the problem is that this mode is supported and required per the spec. So, a developer must know the pros/cons of this mode. It requires them to correctly assess the consequences. It's quite easy to shoot themsleves in the foo
258.
▲
by
sedatk
11mo ago
> I hope that's not literally incrementing a sequence It's literally incrementing it by one: https://github.com/ulid/javascript/blob/11c2067821ee19e4dc78... https://github.com/uli
259.
▲
by
sedatk
11mo ago
You mean someone who wants to attack your system might be discouraged by Base32 encoding?
260.
▲
by
sedatk
11mo ago
Not if the same ULID generator instance is used across threads.
261.
▲
by
sedatk
11mo ago
> You only need to lock sequence if you care about IDs being ordered within a millisecond Yes, and that's when sequences are only used. I guess that's to avoid hogging the CPU or emptying the OS entropy pool during high loads.
262.
▲
by
sedatk
11mo ago
See my sibling comment.
263.
▲
by
sedatk
11mo ago
You're right, not hosts or processes in that case. I forgot about random part as it's been a while since I looked at it. However, a single instance of a ULID generator must support this mode, which means that on multi-threaded arc
264.
▲
by
sedatk
11mo ago
Whenever ULID comes up, I need to remind that it has a sequential ID generation mode in its spec which is prone to conflicts on multi-threads, processes or hosts which kills the purpose of a "universal" identifier. If you need a s
265.
▲
by
sedatk
11mo ago
Why do you think you fainted? Because of the gases?
266.
▲
by
sedatk
11mo ago
Yeah it went on about 12 hours which might be a record. But this was the 38th eruption this year. Others may not have been as big as this though. That said, it feels like a once in a lifetime experience, yes. See my video: https:/
267.
▲
by
sedatk
11mo ago
Yes we watched it in the night too. It was disappointing to see iPhone “normalizing” its brightness down. I had to take raw photos to capture it.
268.
▲
by
sedatk
11mo ago
I was there today. We happened to notice the smoke over Kilauea while driving to Hilo, then checked out USGS cams, and immediately drove there and spent the next 7 hours getting mesmerized. As my first eruption encounter, I didn’t expect t
269.
▲
by
sedatk
11mo ago
It’s a very trimmed down kernel with minimal set of drivers and modules. It doesn’t even support SD cards out of the box. That’s probably the main reason as no hardware probing/initialization delays are incurred.
270.
▲
by
sedatk
11mo ago
Those GUIDs aren't related to NT kernel but Windows Explorer and its COM-based component system. They were introduced with Windows 95, IIRC.
More ›