dinosaurdynasty (u/dinosaurdynasty)

dinosaurdynasty commented on I built a 2x faster lexer, then discovered I/O was the real bottleneck modulovalue.com/blog/sysc... · Posted by u/modulovalue

torginus · 19 days ago

You have a limit of 1k simultaneous open files per process - not sure what overhead exists in the kernel that made them impose this, but I guess it exists for a reason. You might run into trouble if you open too many files at ones (either the kernel kills your process, or you run into some internal kernel bottleneck that makes the whole endeavor not so worthwhile)

dinosaurdynasty · 19 days ago

That's mainly for historical reasons (select syscall can only handle fds<1024), modern programs can just set their soft limit to their hard limit and not worry about it anymore: https://0pointer.net/blog/file-descriptor-limits.html

dinosaurdynasty commented on The most famous transcendental numbers sprott.physics.wisc.edu/p... · Posted by u/vismit2000

canjobear · a month ago

> 1: Almost all numbers are transcendental.

Even crazier than that: almost all numbers cannot be defined with any finite expression.

dinosaurdynasty · a month ago

Leads to really fun statements like "there exists a proof that all reals are equal to themselves" and "there does not exist a proof for every real number that it is equal to itself" (because `x=x`, for most real numbers, can't even be written down, there are more numbers than proofs).

dinosaurdynasty commented on I'm a laptop weirdo and that's why I like my new Framework 13 blog.matthewbrunelle.com/... · Posted by u/todsacerdoti

fullstop · 2 months ago

I was hoping that this is how it would work for System76 -- when I bought the laptop they sold replacement batteries. Five years later I find myself needing a battery and they are unavailable -- not on System76's website, not online, nowhere. My only option is to either replace the laptop or buy a used one and take the battery from that, hoping that it's good.

For the last six months I've just been using a laptop as a mini pc with no battery.

dinosaurdynasty · 2 months ago

https://system76.com/search.php?search_query=battery

If I search for battery stuff shows up, but they only ship bare batteries to the 48 states and Canada.

Contacting support should be able to help you too.

dinosaurdynasty commented on Bikeshedding, or why I want to build a laptop geohot.github.io//blog/je... · Posted by u/cspags

energy123 · 2 months ago

Is his build even possible today in a laptop?

In a desktop, you would need a top of the line threadripper for that 256GB/s of memory bandwidth.

Consumer grade Zen 5 desktops reach only about 80GB/s in real world testing, with a theoretical max of slightly over 100GB/s.

dinosaurdynasty · 2 months ago

AMD Strix Halo (a consumer mobile processor) has theoretical support for 256GB/s of memory bandwidth (quad-channel, 8000 MT/s LPDDR5X, must be soldered, supports 128GB at most).

dinosaurdynasty commented on Fast UDP I/O for Firefox in Rust max-inden.de/post/fast-ud... · Posted by u/Bender

rkomorn · 5 months ago

This is how I find out there's a 2.0 Factorio? What am I doing with my life??

dinosaurdynasty · 5 months ago

Not only that, there's also a DLC with 4 new planets.

dinosaurdynasty commented on Fast and cheap bulk storage: using LVM to cache HDDs on SSDs quantum5.ca/2025/05/11/fa... · Posted by u/todsacerdoti

iam-TJ · 7 months ago

When using LVM one can use the dm-integrity target to detect data corruption.

dinosaurdynasty · 7 months ago

You can even use it without LVM, though it's still a pain to setup.

dinosaurdynasty commented on Fully homomorphic encryption and the dawn of a private internet bozmen.io/fhe... · Posted by u/barisozmen

kube-system · 7 months ago

Sure, hardware is cheap.

However if you actually follow the 3-2-1 rule with your backups, then you need to include a piece of real estate in your calculation as well, which ain’t cheap.

dinosaurdynasty · 7 months ago

You don't need homomorphic encryption for a backup, normal encryption suffices.

dinosaurdynasty commented on Pgactive: Postgres active-active replication extension github.com/aws/pgactive... · Posted by u/ForHackernews

ForHackernews · 7 months ago

What are good off-the-shelf distributed databases? We looked at MongoDB but it wasn't worth giving up SQL. To reiterate the no free lunch point, no one has figured out how to outsmart the CAP theorem yet, so all you can do is design around it.

dinosaurdynasty · 7 months ago

CockroachDB

dinosaurdynasty commented on 'Sticky thinking' hampers decisions in depression bps.org.uk/research-diges... · Posted by u/domofutu

ElevenLathe · 8 months ago

I will add that in my opinion, white collar jobs increasingly /are/ this emotional labor. We don't need as many people to "do stuff" any more (at least not as part of our organizations directly -- it's mostly been outsourced to workers in the far east), but there is endless demand for people to "drive things forward". This is the case for management of course, but that's been their purpose since their position was invented some time in prehistory. Increasingly, this is also an explicit ask of workers, and some jobs are nearly-explicitly nothing but this (product/project/program managers, scrum masters, etc.), even at the IC level.

"Drive things forward" is shorthand for "stress about and take blame for". If you are being asked to "take ownership", you are being asked to earn your bread by conflating your own self worth with the success of some project, usually one whose success is mostly beyond your control. The paycheck is compensation for the sleepless nights and distant stare you affect with your family at the beach. This /is/ the job.

I think this dynamic will only get worse with AI tools doing more for organizations. Project managers are at least somewhat paid for their organization skills and executive function, even if they're mostly being paid for stress. If a machine can organize and coordinate, the only thing left for people to do is...have emotions, worry, absorb threats and abuse.

Another way to think about this is that the ownership class can probably find machine substitutes for most white collar labor, but these machines can't be motivated and managed in the ways that B schools have been teaching for 100 years. Yes, Claude can try to fix a bug, but you can't threaten it to squeeze more out of it. Alice has three kids and a mortgage. It's trivial to threaten Alice -- you don't even have to do it explicitly. If her productivity is enhanced with AI, and her bargaining position softened, this becomes even more attractive because the owners can pay her less to do more.

dinosaurdynasty · 8 months ago

People definitely threaten AIs and find increased short term performance, they've been doing this for a while now.

dinosaurdynasty commented on Should we design for iffy internet? bytes.zone/posts/should-w... · Posted by u/surprisetalk

bob1029 · 8 months ago

If you really want to engineer web products for users at the edge of the abyss, the most robust experiences are going to be SSR pages that are delivered in a single response with all required assets inlined.

Client-side rendering with piecemeal API calls is definitely not the solution if you are having trouble getting packets from A to B. The more you spread the information across different requests, the more likely you are going to get lose packets, force arbitrary retries and otherwise jank up the UI.

From the perspective of the server, you could install some request timing middleware to detect that a client is in a really bad situation and actually do something about it. Perhaps a compromise could be to have the happy path as a websocketed react experience that falls back to a ultralight, one-shot SSR experience if the session gets flagged as having a bad connection.

dinosaurdynasty · 8 months ago

A well done PWA will absolutely beat SSR on a shitty connection if it's actually an app.

Cache-control immutable the code and assets of the app and it will only be reloaded on changes. Offline-first and/or stale-while-revalidate approaches (as in the React swr library) can hugely help with interactivity while (as quickly as possible) updating in the background things that have changed and can be synced. (A service worker can even update the app in the background so it's usable while being updated.) HTTP3/QUIC solves the "many small requests" and especially the "head of line blocking" problems of earlier protocols (though only good app/API design can prevent waterfalls). The client can automatically redo bad connections/requests as needed. Once the app is loaded (you can still use code splitting), the API requests will be much smaller than redownloading the page over and over again

Of course this requires a lot of effort in non-trivial cases, and most don't even know how to do it/that it is possible to do.