Hacker Newsnew | past | comments | ask | show | jobs | submit | rmwaite's commentslogin

> Once you irrigate a field, that water is gone.

This doesn't seem true to me, in the sense that anything is truly "gone". The water doesn't cease to exist or is converted to anything other than water. It just moves.


Right. The water isn't gone from the universe, certainly. But it's gone from the city/county water system. You've then got to wait for it to come back via the natural water cycle. Whereas it's a lot more efficient to keep as much water as possible in the human system and just keep cleaning and reusing it.

Agree completely about the time thing. Indeed, every time I’ve fallen into the trap of somehow believing I’ve moved “past” the time sink it inevitably has bitten me down the road when something breaks or I learn about some maintenance task I should have been doing but didn’t even know existed.

More than anything, I’ve come to admire those who learn how to do this stuff consistently because it is hard.


Haha for example, to the homeowners out there, you should change your water heater anode rod ASAP if you have not. Good luck getting the rod out, because the caps on the water heater get corroded shut. And did I mention you need to drain the hot water heater to do so. You ever tried draining a hot water heater when that task has not been accounted for in the design? You need a way to drain it.


I remember being the big innovation over svn being merging. There were others things, obviously, but the distributed model + easy merges is what I remember.


Yes, that's true, merging. Which is what made branching a reasonable thing to do.


If the big innovation over svn is merging for git, then the big innovation here is conflicts. I hate the fact that git requires you to stop everything and fix the merge conflict when you merge. I especially hate the fact that when rebasing in git sometimes it requires you to solve conflicts one by one. The big innovation here is jj does not require you to resolve merge conflicts in a timely manner; it simply records the fact that there are conflicts in the file and you go about your ways. You don't ever have to abort like `git rebase --abort` or `git merge --abort`.


Any language of Python’s size and popularity will be a mess, the only difference is what parts of it.


No, python is specifically a mess.


What I find fascinating about LLMs is that a lot of their failures seem strikingly similar to the failures that humans struggle with. I’m not sure what this “means” but I think it’s interesting that we can theoretically fix these failures for LLMs but for humans it is much harder. You pretty much need to educate / indoctrinate people for their entire lives and even then it’s messy and unpredictable and prone to failure—just like LLMs.


I don't think this is something to laugh at. Whether or not you think it's necessary or a proper method of punishment, it isn't funny.


It was always funny to us as kids, and we often laughed at the poor bugger who had earned that punishment (and were laughed at when it was us).

Our teachers didn't abuse us like some do in other societies, with extra homework and detention. We new the rules and punishment for breaking them, and made choices accordingly. Wonderful teachers who I remember fondly decades later, though some of them have passed on.


This matches me experience as well. Some of my earliest rsync experiences were with the Cygwin version and I can remember scratching my head and wondering why people raved about this tool that ran so slowly. Imagine my surprise when I tried it on Linux. Night and day!


In my case, once I set the limit to 0 minutes and refreshed the home tab I don't see Shorts recommendations at all. There is still a Shorts tab at the bottom that tells me I have no remaining time (and allows me to trivially override it, sigh). But otherwise this seems to have cleaned up the "feed" that I see in the app of anything Shorts related (for now, at least).



IP addresses were always meant to be globally reachable. Of course, NAT has corrupted this - which is why NAT is a scourge.


And so are firewalls?


firewalls are a choice that the enduser makes.

non-routed prefixes are a limitation imposed by the ISP the the user can't address.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: