He is extremely rich. All of these problems are easily solvable with the resources he has.
And yet he chose his choices.
Readit NewsI think they just meant it's very stereotypically american to drive a very walkable distance and eat McDonald's every day
I’m familiar with this neighborhood. If this were my commute I’d probably walk often.
But:
It’s 42 minutes by foot one way, which is on the longer end for most people. About half of it is pleasantly walkable, the rest looking like no trees and along a busy street.
… For probably six months out of the year, the rest being too uncomfortably hot or windy/cold for most people.
And he’s probably wearing a suit and leather shoes every day, so you risk wet/muddy shoes, road salt, or dripping in sweat or rain. Mess up your hair with a hat in the winter.
And if you are going anywhere after, you’ll need a car anyway. The rest of Omaha is not walkable and quite hilly.
And he’s old, quite old. He’s been old for decades. Some people can do 3.6mi/day in their 50s-80s but most will not.
And his time value in literally among the… top ten in the world or so? And has been for decades?
I say all this as a relatively extreme walking advocate: for most people in some locales (including most of America), it just doesn’t make sense, and this criticism is very silly.
He’s Warren Buffet, so he could make this work if he wanted to. He could insist everyone come to him at his home while he wears pajamas.
But it’s not unreasonable to drive this commute.
And you can get a decent breakfast at McDonald’s too :D
I've always had stuff like this turned down by Netbox, they argue they want to model the logical topology as a source to trust, not the physicality, but then they model rack U placement. I'm always puzzled by their stance.
Like you can't model 1 cat5 split into two 100mb terminations, patch panels are kinda of hack, I think you can now but forever you couldn't just swap a termination direction because logically why would you (but their UI gets messy when 44 are done A-B and the 45th B-A)
Anyway that's thoughts as of maybe v2 or 3? Before the new UI when it was all jquery.
Any links to PRs or discussions?
Regardless of how it must be implemented, if this is a desirable feature then this explanation isn’t an absolution of Linux but rather an indictment: its development model cannot consistently provide this product feature.
(And same for Windows to the degree it is more inconsistent on Windows than Mac)
I should have said ‘product development’ model versus just ‘development’ to be more clear. To state another way: Linux has no way, no function, no pathway to providing this. This is not really surprising, because it isn’t the work software developers find fun and self-rewarding, but rather more the relatively mundane business-as-usual scope of product managers and business development folks.
… And that’s all fine, because this is a super niche need: effectively nobody needs Linux laptops and even fewer depend on sleep to work. If ‘Linux’ convinced itself it really really needed to solve this problem for whatever reason, it would do something that doesn’t look like its current development model, something outside that.
Regardless, the net result in the world today is that Linux sleep doesn’t work in general.
Sleep and hibernate don't just work on Windows unless Microsoft work with laptop and boards manufacturers to make Windows play nice with all those drivers. It's inevitable that it's hit and miss on any other OS that manufacturers don't care much about. Apple does nearly everything inside their walls, that's why it just works.
Regardless of how it must be implemented, if this is a desirable feature then this explanation isn’t an absolution of Linux but rather an indictment: its development model cannot consistently provide this product feature.
(And same for Windows to the degree it is more inconsistent on Windows than Mac)
pbh101 commented on Instant database clones with PostgreSQL 18 boringsql.com/posts/insta... · Posted by u/radimm
Every single commit is Claude.
No human expert involved.
Would you trust your company database to an 25 dollars vibe session?
Would you live in a 5 dollars building?
Is there any difference from hand tailored suit, constructed to your measurements, and a 5 dollars t-shirt?
Some people don't want to live in a five dollars world.
Most of the OSS projects on HN are not worthy for you to base your company on, especially sight unseen. Using an agent has nothing to do with it.
pbh101 commented on Instant database clones with PostgreSQL 18 boringsql.com/posts/insta... · Posted by u/radimm
pbh101 commented on Instant database clones with PostgreSQL 18 boringsql.com/posts/insta... · Posted by u/radimm
What an outrageously bad analogy. Everyone involved in that building put their professional reputations and licenses on the line. If that building collapses, the people involved will lose their livelihoods and be held criminally liable.
Meanwhile this vibe coded nonsense is provided “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. We don’t even know if he read it before committing and pushing.
Same with any OSS. Up to you to validate whether or not it is worth depending on, regardless of how built. Social proof is a primary avenue to that and has little to do with how built.
pbh101 commented on Instant database clones with PostgreSQL 18 boringsql.com/posts/insta... · Posted by u/radimm
I agree that it's ultimately about the product.
But here's the problem. Five years ago, when someone on here said, "I wrote this non-trivial software", the implication was that a highly motivated and competent software engineer put a lot of effort into making sure that the project meets a reasonable standard of quality and will probably put some effort into maintaining the project.
Today, it does not necessarily imply that. We just don't know.
In general that is all implication and assumption, for any code, especially OSS code.
I imagine this holds true (via chatting with insider friends) for many such "industries" including lawmaking, scientific/academic papers, industry RFCs, etc. More or less credential washing.