Screen size would have always been big, absent production costs and marketing price. Over time display tech just got better and cheaper to finally do it.

Echo chamber strikes again, because I see none of that, just love for knowledge, history, and science.

Try posting anything even mildly positive about AI on Bluesky and you’ll experience instant hate.

Well that's just what getting out of the AI echo chamber feels like.

Try saying anything positive about AI at the grocery store and you'll have the same experience.

Kind of shocked there's not any mention about tumblr in the article, there is an entire community of people who adore powerlines, get tattoos, talk about their aesthetic values, it's an entire subculture that I love following.

To be fair, Alibaba IS a tech giant, one of the biggest in fact.

They are just giving sleepless nights to the western tech giants.

I'm hearing Tencent, Zhipu and Baidu shaking from here. It's fair to assume BATX / 6 Tigers don't sleep very well either.

Interesting, I found the Rust code _far_ more readable.

I don't really get an AI smell on this, in fact I see multiple parts that an AI would have corrected - grammatical issues, personal writing quirks, etc.

Writing similar to this: is quite a normal way of writing for technical articles - especially when you are trying to make the point clear and well organized.

"A major version bump is not something we do lightly, and it is not just ceremony"

For me, this sentence pops out like a sore thumb

Really looking forward to that new Async system, especially when reading/querying against thousands of parquet files. This is going to monumentally affect me and my work - I have to query against millions of massive parquet files and the speed has already been rather wonderful, but if those metrics are to be even 100% in range, this is going to make life so much better.

DuckDB is seriously an incredible utility.

Racket may be significant faster than many, esp since transitioning to Chez, but its still very hard/problematic to compile to a binary, and if wrapped into a binary still very bloated in size.

FWIW: I enjoy working with Gambit, especially since it can compile to C and standalone binaries and also scores even higher than Racket.

I read through the page, and thought it was precisely what it needed. It very adequately described its usage, differences, and it's key points.

This isn't a blog post, this is a homepage, and as a homepage it is selling its idea to its specific audience, which is developers who use WordPress as a CMS and deplore the rest of the tedious stack. Even if it's AI generated, its obviously been human-edited rather well.

OP, I thought it was well-done, great work, makes sense, I'll have to dig through the changes to see if its worthwhile, but I love the concept and limited attack vector size (a lot of WP security bugs are from their parsers and server-side rendering).

Thank you :)

This is wonderful - might even be exactly what one of my projects needs to use as a dependency.

In the README it mentions that it puts the dev environment in a filesystem jail, but how are you able to use your hosts bins without leaking access to the rest of the system? Or is that just an assumed liability?

It assembles and pivots to own root filesystem. The filesystem mounts dirs and files from your original filesystem, most of them in read-only mode, but does not mount files that expose secrets to the sandbox. The sandbox also mounts own, writable version of your home dir, so secrets, such as .ssh dir are not exposed. The config file allows to configure which files should be exposed from your original home. For example, configs, such as .bashrc, are safe to expose in read-only mode, provided you don't store secrets in them.