knutwannheden

> Compiler would eat them like donuts.

Made me laugh out loud!

I reckon that while my programming has become more productive with LLMs, it has at the same time gotten a bit more frustrating and boring.

I think it is difficult to know in advance when the LLM will do a reasonable or good job and when it won't. But I am slowly learning when and how to use the tools while still enjoying using them.

Changing screen sizes appears to be a very common theme for Apple. That way they can a few years later re-introduce the old screen sizes as the best invention since sliced bread. Very annoying. I would also have liked to see a 24"+ model.

Interesting. I will be curious to see how it stacks up against Jackson Smile, both in terms of features and performance. Since it appears to support both polymorphism and back-references, it looks like it already has some advanced features.

While I think the paraphrased Jurassic Park quote can be very funny at times, I don't really agree with the statement. But I assume you were being sarcastic.

Am I one of the only developers who actually likes the CONNECT BY queries? Often I think they are a very succinct alternative to recursive CTEs.

My personal favorites are Altair (Python/VegaLite) and Observable Plot. The latter just released a new version with GeoJSON support.

I still didn't get it.

Would be interesting to see what GitHub Copilot makes of this.

I would have opted for Shocker ;-)

It lets you specify a list of terms which mustn't be further apart from each other than a given number of tokens.

I don't have experience with PG FTS, but I've used SQLite FTS5 and love it for its ease of use. Also I really like its NEAR() queries. I was a bit surprised that the post doesn't mention this capability and compare it with the other implementations (i.e. is it available and how does it compare performance-wise).

100% agreed. Whenever I see something being promoted as "cheapest" I try to stay clear. Not only because you often get what you pay for, but also for reasons like the one you mention.

Is it possibly because the font should be monospaced and the reader might then mistake the distance before and after the "I" for a space?