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

If you have a family, a minivan makes so much more sense than an SUV. Minivans have more interior space, more cargo room, auto rear doors that are impossible to bang on the adjacent car, cost less, get better fuel economy, and more.

I live off a dirt road, and if my minivan breaks, I'm not going to buy an SUV, I'm going to buy another minivan, but I will buy an AWD model instead of FWD like my current model.


I tried so hard to convinced my wife to get a minivan, but alas, we ended up with a Subaru Crosstrek or something like that.

It took me too long in my career to feel comfortable asking the dumb questions. I would have had a much easier time if I had just asked them. I eventually learned to ask dumb questions when I made a friend who was never afraid to ask then, and it was amazing how quickly he learned.

Not to be confused with the kubernetes container runtime interface CLI https://github.com/kubernetes-sigs/cri-tools/blob/master/doc...

This is pretty similar to what github did with git.io https://github.blog/changelog/2022-04-25-git-io-deprecation/

He has a great video where he goes through a bunch of different software that Aphex Twin used over the years. https://youtu.be/5wIOBBodoic

I was about to talk about how online help files are forgotten these days, and should guide you to the right information to set up an ad-hoc network, but I was disappointed three times over by macOS.

macOS does not have any offline documentation like pretty much every OS used to. When I turn off my WiFi and then open "Mac User Guide" or "Tips for your Mac", they both tell me they require an internet connection.

When I re-enable my internet connection, neither of those apps have information about how to set up an ad-hoc wifi network.

When I looked up how to create an ad-hoc network in other sources, I discovered that the ability to create an ad-hoc network was apparently removed from the GUI in macOS 11, and now requires CLI commands.

I hate how modern tech companies assume that everybody always has access to a high speed internet connection.


I hate how modern tech companies assume that everybody always has access to a high speed internet connection.

I suspect it's deliberate, especially when said company also sells cloud services.


https://www.cesium-app.com was great for me for a long time. I forgot why I quit using it, but I don't think it was because it stopped being great.


There is also https://containers.dev which is the first thing I configured when my company gave us Cursor. All agentic LLMs to date need to be on a very short leash.

Pro tip: you can run `docker diff <container-id>` to see what files have changed in the container since it was created, which can help diagnose unexpected state created by the LLM or anything else.


I use uptime-kuma[1] with notifications sent out through the included Apprise integration[2]

1. https://github.com/louislam/uptime-kuma

2. https://github.com/caronc/apprise


One gotcha I caught myself in with this technique is using it in a script that would remediate a situation where my home has lost internet and needed the router to be power cycled. When the internet is out, `uv` cannot download the dependencies specified in the script, and the script would fail. Thankfully I noticed this problem after writing it but before needing it to actually work, and refactored my setup to pre-install the needed dependencies. But don't make the same mistake I almost made! Don't use this for code that may need to run airgapped! Even with uv caching you may still get a cache miss.


`uv run --offline` will use cached dependencies and not check for newer versions. Works for `uvx` too, i.e. `uvx --offline ...`.


But don't you have to only ever run it once to have the deps/venv for subsequent runs?


I don't know if uv garbage collects its cache, but it wouldn't surprise me. Otherwise disk usage would grow indefinitely.


Yes, disk usage grows indefinitely

https://github.com/astral-sh/uv/issues/5731


If you indefinitely grow the collection of packages that you have in use in permanent virtual environments, then yes your disk usage will and should grow indefinitely anyway.

There's not much point recycling contents from a package cache unless you currently don't have a venv using that package and also don't reasonably expect to have one in the near future.

And I'm saying this as the guy complaining all the time about things like the size of Numpy wheels.


Here's a fun one (says he, in a panic): Will we get to a point where (through fault or, gasp, design) a given AI will generatively code a missing dependency, on the fly - perhaps as a "last ditch" effort?

(I can imagine languages having official LLMs which would more or less "compress/know" enough of the language to be an ...

... import of last resort, of sorts, by virtue of which an approximation to the missing code would be provided.-


I'm pretty sure we've already reached a point where people generatively code possibly-malicious packages to publish under names of non-existent packages commonly hallucinated by LLMs prompted by other devs.


Oh my goodness: That is a truly truly scary thought.-


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

Search: