HNHacker News
TopNewBestAskShowJobs

FridgeSeal

7,095 karma · joined March 20, 2017

Opinions are my own etc etc etc
submissionscomments
FridgeSeal··on Committing to Rust in the Kernel
I wouldn’t really describe a lot of Rist codebases I’ve seen as “OO-ify’d”. I’d say it’s got a more functional flavour if anything.

In my experience “de-programming” OOP-programmers is one of the first things teams I’ve been have had to do so that said OOP devs have a better time and write more idiomatic code.

FridgeSeal··on What Is Io_uring?
IIUC io_uring surfaced a bunch of pre-existing-but-rarely-hit code paths that had issues, which was widely taken to mean “io_uring has issues”. Google also disabled it on all machines in GCP, not clear if Google disabled it because of the same issues, or some other thing. The aforementioned issues have been fixed.
FridgeSeal··on It's Okay to Abandon Things
Aaaahh I'm dense. I forget you have to click through the comment to get the favourite button.
FridgeSeal··on Anime is eating the world
2 of their listed categories are also shamelessly AI focused, so you can really see them lining up the investor-catnip.

Would be nice if VC’s would go destroy something of theirs for once, and leave everyone else out of it.

FridgeSeal··on It's Okay to Abandon Things
I wish HN let us favourite comments, because I’d favourite this and then print it out and stick it on my wall. Really like this.
FridgeSeal··on Working in the office 5 days/week to build company culture is a myth: PwC report
What are you calling abuse? Not showing up for “company mandated fun time o’clock”?

Also, I hate to break it to you, but the employees that are “genuinely” abusing WFH and shirking work responsibilities are doing the same thing in the office.

FridgeSeal··on MicroPython on Flipper Zero
Rolling code protocols like Keeloq can be broken pretty easily (apparently).
FridgeSeal··on MicroPython on Flipper Zero
Plenty of devices use the Keeloq protocol for rolling codes which is pretty straightforward to break in modern hardware.
FridgeSeal··on LinkedIn is now using everyone's content to train their AI tool
It’d be like a high-school argument between the edgy kid, and the kid that would wear suits and bring a briefcase. Comical, pointless and everyone else wants both of them to be quiet after about 10 minutes.
FridgeSeal··on LinkedIn is now using everyone's content to train their AI tool
I don’t know why you’re downvoted here, it’s pretty well known there’s a huge bunch of people trying to pick up using LinkedIn DM’s, for whatever reason.
FridgeSeal··on Master Hexagonal Architecture in Rust
I don't think anyone here is seriously suggesting that separating IO and concerns is bad.

I think people here are devaluing the "kind of approach" taken in these over-abstracted-architectures. The snippets of "improved" code in TFA have a lot of new line-noise, a lot of boilerplate and half-a-dozen "new" pieces of terminology, all in the quest to essentially separate IO and core logic.

There's plenty of ways to perform this separation, many of them don't require replicating half the design-patterns from C# tutorial. I'm pretty partial to "functional-core, imperative-shell", I think that it achieves all the same advantages, with none of the new concepts, and far less line noise.

FridgeSeal··on Master Hexagonal Architecture in Rust
I love a good rabbit hole, thank you!
FridgeSeal··on Master Hexagonal Architecture in Rust
> Hard-coding your handler to manage SQL transactions will come back to bite you if you switch to Mongo

I uuuhh, I hate to tell you this, but uh, if you’re swapping Postgres to Mongo, and you think that hardcoded queries are going to be your migration pain points, I have some bad news for you. The difference in semantics (for any such change, not just db) will bite you first, and wil bite a lot harder.

This idea of “we can abstract over everything and then swap them out at our leisure” works less than we’d all like to imagine it does, and crucially building everything to accommodate this utopia, will leave you with mountains of code that will do nothing other than make your teammates hate you and obscure your actual logic.

> AuthorRepository

Oh hello C#. So instead of cursing everyone who has the misfortune of working on your C#-flavoured-rust codebase of having to write literal pages of boilerplate to inevitably add a new struct/type to the codebase, I suggest leaning into idiomatic Rust a bit more. Personally, I’d make read/delete/upset traits, whose methods take a handle to a connection pool. Logic for sql then lives inside these implementations, and can be brought into scope only when necessary. Something like `my_struct.upsert(&conn).await?`. We have locality of behaviour, we’ve separated IO details out, we have all the same advantages with about 50% less code-noise.

FridgeSeal··on Master Hexagonal Architecture in Rust
That’s a mighty lot of words, to say “functional core, imperative shell”.

Maybe I’m being glib, but damn, a whole article, and boatloads of fancy new terminology, just to re-state what the author succinctly landed on in the _first_ paragraph:

> Create your application to work without either a UI or a database so you can <do a bunch of nice stuff and make your life easier>”.

FridgeSeal··on Master Hexagonal Architecture in Rust
Hmmmmm.

Mixed feelings about this.

“Oh our http handler knows about the db”

Ok? Its job here is more or less “be a conduit to the db with some extra logic”.

It “knows about a lot of things” but it’s also exceedingly clear what’s going on.

The main function is fine. I’ll take a “fat” main function over something that obscures what it’s actually doing behind a dozen layers of “abstraction”. Nothing like trying to isolate a component when you’re fighting an outage and nobody can figure out which of the 16 abstract-adapters or service-abstracted launched the misbehaving task.

The original code might be “messy” but it’s at least _obvious_ what it’s doing, and it can pretty clearly be pulled apart into separate logic and IO components when we need to.

This all just feels a bit…over engineered, to say nothing of the insulting tone towards the other learning resource.

FridgeSeal··on Learning to Reason with LLMs
Yeah you’re right, all businesses are made of identical, interchangeable parts that we can swap out at our leisure.

This is why enterprises change ERP systems frictionlessly, and why the field of software engineering is no longer required. In fact, given that apparently, all business is solved, we can probably just template them all out, call it a day and all go home.

FridgeSeal··on Learning to Reason with LLMs
Bold of you to expect transparency and clarity from a company like OpenAI.

You wanted reliable readable graphs? Ppphhh, get out of here, but pay of for the CoT tokens you’ll never see on your way out though.

FridgeSeal··on A good day to trie-hard: saving compute 1% at a time
Idk man, I’m not Cloudflare.

That said: probably different teams with different priorities.

I also disagree that “it’s _only_ $20-30k” as some kind of reason to not do this kind of work. Think of it another way: that’s now another 680 cores that can do _net more work_, that’s another 20-30k we don’t have to spend when traffic increases. “I landed a small PR that wiped $30k net off our costs” is a statement that would make a lot of people in a business pretty happy.

FridgeSeal··on A good day to trie-hard: saving compute 1% at a time
From the article:

> At the time of writing, the rate of requests leaving pingora-origin (globally) is 35 million requests per second. Any code that has to be run per-request is in the hottest of hot paths...function consumes more than 1.7% of pingora-origin’s total cpu time. To put that in perspective, the total cpu time consumed by pingora-origin is 40,000 compute-seconds per second. You can think of this as 40,000 saturated CPU cores fully dedicated to running pingora-origin. Of those 40,000, 1.7% (680) are only dedicated to evaluating clear_internal_headers. The function’s heavy usage and simplicity make it seem like a great place to start optimizing.

Given how many requests are going out, and just how hot the function is, every single gain matters. If my read of the article is correct, this is the hottest part of the hot path, so every gain here is super important.

FridgeSeal··on A good day to trie-hard: saving compute 1% at a time
I don't think it would matter if there's only 1 header to be removed, it's still a problem to be solved.
FridgeSeal··on A good day to trie-hard: saving compute 1% at a time
A lot of Rusts' optimisations are from LLVM, so if that's smart enough to, then I assume it also benefits.
FridgeSeal··on Show HN: Io_uring for Ruby
I'm aware, but give people a proxy for something like downvotes, and they'll use them as such. Hackernews tends to have more restraint than reddit on that front, but not immune.
FridgeSeal··on Rɐbbit Dynamic Datascapes
Hell yeah, I really dig this.

I love the commitment to the aesthetic, I love the reframing of it as “should feel more like a game engine than an app”. As someone who has also been through the dashboard-web-app-spectrum-of-pain, this looks like something I’ll be following with a close eye.

FridgeSeal··on Show HN: Io_uring for Ruby
Probably because it’s a fairly tired argument that gets rolled out almost automatically in response to any async-IO or high speed IO work. It’s like there’s a group that likes to argue that only the cream of the crop spills get to use nice new things, and the rest of us spills be pleased with what we have already. At this point, it’s a bit “ok thank you”, it don’t add much.
FridgeSeal··on Operating system threads are always going to be (more) expensive
> io_uring is mere batching to the kernel upper-half

Your phrasing here suggests the NT kernel can/does have API’s that reach further down, is that correct, or am I reading too deeply? Haha

FridgeSeal··on Asynchronous IO: the next billion-dollar mistake?
Which is fine until we decide that actually, we _would_ like that performance back, and now we re-implement async flows at language level again, realise what an advantage it’s bets us, and then that trickles into other languages as they also seek those advantages.
FridgeSeal··on gRPC: The Ugly Parts
I 100% agree with the enum rules, the frustrating lack of required, but I do disagree with the “oh no FE couldn’t use it out of the box”.

It’s actually ok that not everything need accomodate every single environment and situation. I’d personally like to see some _more_ RPC mechanisms for service-to-service that don’t need to accommodate the lowest-common-denominator-browser-http-requirements, there’s plenty of situations where there’s no browser involved.

FridgeSeal··on Deploying Rust in existing firmware codebases
That makes it sound like JS is analogous to iron, instead of the damp cardboard it actually is hahahaha
FridgeSeal··on The Internet Archive has lost its appeal in Hachette vs. Internet Archive
As far as I can tell (these are all new acronyms to me too), they stand for:

CDL: Controlled Digital Lending

NEL: National Emergency Lending.

FridgeSeal··on Intel: New Core Ultra Processors Deliver Breakthrough Performance
Upside: you can have new cores, which are faster.

Downside: oh you thought performance, no we meant “even faster to burn out”.

← PreviousPage 17 of 34Next →