Ahahahahhahahahahhahahahaahaha. Please tell me this is tongue-in-cheek and just more subtle than I give HN credit for. Please.

Not all devs, not even most, but I certainly think this

> In a way it's comforting to know those people who hold these positions, with distinguished careers and supposedly made of better stuff than us mere mortals, are in fact just a bunch of miserable weasels, a-holes and sycophants.

There's nothing that quite makes me feel like humanity has undergone speciation than the fact that this STILL HAS TO BE FUCKING SPELLED OUT FOR PEOPLE.

Hero worship is sycophancy of the highest order. Ugh, and I know you're so right.

Man, it's so understandable. Especially when 35-40% the country is doing exactly that kind of bullshit equivocative defense. Frankly I'm shocked the shitheads usually here read the room and have kept the child-rape apologia to themselves.

Finding and eating roadkill is cheap too, free even. Free protein in this year? Yeah, I'd rather do that than use fucking SMS for anything.

Dogs eat roadkill and poop. Dogs are very popular. You may have a point!

> why should we believe someone that it's a bubble based on "feel"?

because leaders in the space also keep saying it? And then making financial moves that us pleebs can't even dream of, which back that up?

This whole "the media keeps reporting it" as a point against the credibility of something is utterly silly and illogical.

> because leaders in the space also keep saying it?

They have a lot of reasons for saying that, including to give themselves cover in the event of a crash.

What’s happening now is a classic land grab. You’re always going to get inflated prices in that situation, and it’s always going to correct at some point. It’s difficult to predict when, though.

So are you out of touch with CEO comp packages, or are you also bad at math? (In case you or someone else needs to hear it, ain't no CEO ain't gonna fuck ya for defending CEO's excessive compensation in the Hacker News comments. What a weird thing to do.)

Go look at their actual compensation package and get back to me. Unless you want to pay everyone in stock instead of cash you aren’t saving any money.

30,000,000 / 30,000. Hope you can find a calculator to help you with that challenging math. I know it gets hard with such big numbers! (kinda the point, here!)

If you don’t want to actually pay attention that’s fine.

> leverages the unique way that Flox environments are rendered without performing a nix evaluation"

I'm curious! and ignorant! help!

Is that via (centrally?) cached eval? or what? there's only so much room for magic in this arena.

Yeah, it's essentially cached eval, the key being where/how that eval is stored.

When you create a Flox environment, we evaluate the Nix expressions once and store the concrete result (ie exact store paths) in FloxHub. The k8s node just fetches that pre-rendered manifest and bind-mounts the packages with no evaluation step at pod startup.

It's like the difference between giving the node a recipe to interpret vs. giving it a shopping list of exact items. Faster, safer, and the node doesn't need to know how to cook (evaluate Nix). I don't know, there's a metaphor here somewhere, I'll find it.

Only so much room for magic, for sure, but tons of room for efficiency and optimization.

Correction: we don't eval when you create environments.

Our catalog continuously pre-evaluates nixpkgs in the background. 'flox install' just selects from pre-evaluated packages -- no eval needed, ever. The k8s node fetches the manifest and mounts the packages.

Eval is done once, centrally, continuously. So... even more pre-val'd, so to speak.

So, nix-snapshotter? Also, Flox going all in on "environments" seems like such a choice. I'm sure that Flox is not encouraging shipping a binary-in-a-devshell to Prod, so it seems an interesting branding decision.

It's hard for me to understand if I should be excited about this. I think companies do themselves such huge disservices from not being transparent to the nerds that WILL be the ones helping choose/implement these things. Instead of the current feeling I have, there could be three sentences that explains what Flox is offering here beyond what *anyone* can go do right now with nix-snapshotter.

If it's ecosystem stuff (you get Flox's CI, or CLI, or whatever else), that's not very well sold to me on the landing page. Otherwise I'm feeling left empty-handed.

Totally valid - we buried the lede here. Quick version:

Not nix-snapshotter because we skip Nix eval entirely and get way better cache sharing across unrelated workloads (quantized catalog means everything shares base deps). On "environments": these aren't devshells-as-prod, they're the actual runtime; same as 'flox activate' works everywhere. You're shipping a declarative, hash-pinned runtime that happens to also work great in dev/CI

And yeah, we should have been upfront that this is alpha and we're planning to open source it after vetting at KubeCon.

You're right that we're doing ourselves a disservice not being transparent with the technical crowd. What specific technical details would help you evaluate this?

Hard to say because I'm a bit ignorant of the edges of Flox right now! This comment is great though. :) And even more exciting to hear it will be OSS'd. Appreciate your replies here, good luck!

> it would be helpful if you actually explained your reasoning.

It's exceedingly clear that's not going to happen, and I think we all know why. Good reminder to anyone that anyone can just post here. Including people that logic-lessly think that paying a shitty third party that probably has a bad track record is somehow better than using LE. Like, this isn't a serious conversation?

I would have that concern, at minimum 100x more with random shitty unreliable SSL providers, than those being run by literal huge nerds and non-profits. Your analysis here is thin and lazy and that's being generous to your analysis.