I've been building my own tooling doing similar sorts of things -- poorly with scripts and podman / buildkit as well as LD_PRELOAD related tools, and definitely clicked over to HN comments with out reading much of the content because I thought "AI slop tool", and the site raised all my hackles as I thought I'll never touch this thing. It'll be easier to write my own than review yet another AI slop tool written by someone who loves AI.
I'm glad I read the HN comments, now I'm excited to review the source.
You could run the comments everyone else posts through an AI tool and ask it to rephrase it so that it is clean, and easy-to-read.
You could even write a plugin for your favorite web browser to do that to every site you visit.
It seems hard to achieve the inverse that is (would you rather I use i.e.?) rewrite this paragraph as the original author did before they had an AI re--write it to make it clean, (--do you like oxford commas, and em/en dashes! Just prompt your AI) and easier to read
> You could run the comments everyone else posts through an AI tool and ask it to rephrase it so that it is clean, and easy-to-read.
For those coming from a language other than English, you are more likely to lose information by using a tool to “reconstruct” meaning from poorly phrased English as an input, as opposed to the poster using a tool to generate meaningful English from their (presumably) well-written native language.
There's a big difference between me running a filter on other people's words, and those people themselves choosing to run one and then approving the results.
I personally don't see a problem with someone using a grammar checker as long as they aren't just blindly accepting its suggestions. That said, if someone actually is using it in that way, it shouldn't be detectable anyway, so it probably doesn't matter all that much whether or not it's included in the letter of the rule.
Blanchard fed the spec to the tool, and Anthropic fed the code to the tool, so Blanchard didn't do anything wrong, and Anthropic didn't do anything wrong. Nothing to see here.
Yes. Specifically: The use of words to express something different from and often opposite to their literal meaning, and not some knifey spoony confusion.
But why would you do that? Especially if you know there are robots enforcing that you come to a complete stop?
There are many places that don't even allow rights (or lefts) on red.
I got a right on red ticket once, and then I made it a point to obey the law -- especially at the intersections with the robots.
For things like traffic laws especially (where there are very simple cut and dry rules), why is it okay to break the law, and why is it not okay for robots to enforce the law?
Many countries have minimum wages for many jobs [1].
There is a tacit agreement in polite society that people should be paid that minimum wage, and by tacit agreement I mean laws passed by the government that democratic countries voted for / approved of.
The gig economy found a way to ~~undermine that law~~ pay people (not employees, "gig workers") less than the minimum wage.
If you found a McDonalds paying people $1 per hour we would call it exploitative (even if those people are glad to earn $1 per hour at McDonalds, and would keep doing it, the theoretical company is violating the law). If you found someone delivering food for that McDonalds for $1 per hour we call them gig workers, and let them keep at it.
I mean yeah, it's not as bad as being tortured forever? I guess? What's your point?
Minimum wage is a lower class of violation than most worker exploitations.
Uber drivers are over the minimum wage a lot of the time, especially the federal one. Nowhere near this $1 hypothetical.
A big one is that the actual wage you get is complicated. You get paid okay for the actual trips, as far as I'm aware. But how to handle the idle time is harder. There are valid reasons to say you should get paid for that time, and valid reasons to say you shouldn't get paid for that time.
I find that if I want to use JSON storage I'm somewhat stuck choosing my DB stack. If I want to use JSON, and change my database from SQLite to Postgres I have to substantially change my interface to the DB. If I use only SQLite, or only Postgres it's not so bad, but the transition cost to "efficient" JSON use in Postgres from a small demo in SQLite is kind of high compared to just starting with an extra docker run (for a Postgres server) / docker compose / k8s yaml / ... that has my code + a Postgres database.
I really like having some JSON storage because I don't know my schema up front all the time, and just shoving every possible piece of potentially useful metadata in there has (generally) not bit me, but not having that critical piece of metadata has been annoying (that field that should be NOT NULL is NULL because I can't populated it after the fact).
I'm sure it depends where one lives, but if your drinking water is safe there's no real reason to boil the water except for proper steeping.
I definitely use boiling water with my bagged breakfast tea, but boiling is too hot for white and green tea (especially fancier teas), and boiling water "scorches" the "delicate flavors" (using quotes since I'm sure there are better / nicer words than those), so you want to steep at 80C or lower depending on the tea, the quantity the vessel, and the process.
It's definitely better than nothing, and greatly improves things, but UBO is better. Try watching a youtube video in a browser with UBO, and the android app on a network with pi-hole, etc.
That is an excellent description of wavelets from one of the first points: "The vast majority of wavelet documents and internet tutorials appear to be written by mathematicians for mathematicians." all through the article.
I'm glad I read the HN comments, now I'm excited to review the source.
Thanks for your hard work.
ETA: I like your option parser
reply