There is significant suffering in the world. You and everyone else are drawing lottery tickets everyday. Kids are far from its only source or cause. I'm ill equipped to unpack the meaning of life, but I am certain that suffering is fundamental--your comment is probing at this idea.
This is a very difficult subject since there exists un-imaginable suffering and it's hard to reconcile that. That life is a gift under the umbrella of un-imaginable suffering. Perhaps, that's what spirituality tries to do, I don't know.
I think a lot of folks don't consider that each child comes with a high-enough-to-worry-about risk of negatively affecting the life of everyone in your family to a level on par with one of the adults in your family becoming permanently and severely disabled relatively early in life.
Yeah sure we also risk some micromorts and the life-altering-disability equivalent every time we drive a car or get a sunburn, all right.
To raise $4m seed from AAA partners usually requires connections + track record/credability of the founders - looks like they have that here since they raised 3 rounds with zero revenue.
A tool might not be the best tool to build itself, doesn't mean it is not good.
You don't use a screwdriver to craft screwdrivers. Doesn't mean screwdrivers are inherently bad
They are remarkably common in long lived enterprise Linux servers. Think eg database servers or web servers where they are of the (much longer lived) pet era not cattle era.
Not sure why you need to belittle one example just to add another
I just hope FreeBSD dosen't get bit by the Rust in the kernel initative. Maybe it'll have to deal with it eventually, when, for example, expanding the compatiblity layer to support interoperability with Linux. But, maybe by then, at least Rust will have gone through its hype test gauntlet and we can see it for what it is instead of being tainted by a polticial power grab.
> At some point in early 2026 the rust KPIs should be stable enough for interested developers to try writing new code with them. They will not be perfect, but I want to make sure they work roughly like existing drivers expect and also fit the expectations of rust developers before asking for testers. Hopefully the Apple drivers will be back up to parity with the initial WIP in C in the first half of 2026 as well.
Depending on your process, there is nothing wrong starting with this tool (Neo) first. It's a classic dilemma. For your first tool, buy the cheapest one possible to get the job done. Once the tool becomes understoond, it's limits reached, it's place in the process discovered, then, buy the most expensive one you can afford.
reply