In practical terms, "productivity" is any metric that people with power can manipulate (cheating numbers, changing narratives, etc) to affect behavior of others to their interests.

ALL OF IT is meaningless. It's a pointless discussion.

I'd recommend you read the book referenced in the conclusion: https://link.springer.com/chapter/10.1007/978-1-4842-4221-6_...

The full PDF is available for download. It's mostly a series of essays, so you can pick and choose and read nonlinearly. It's worth thinking about beyond nihilistic takes.

I'll look into it, thanks!

It might sound nihilistic (what does that even mean in this context? anyway), but it's not.

There are lot of good discussions about what good work actually means. I'm dismissing productivity discussions, not the whole set of belief systems.

Basic dicts, arrays and templates might be the killer feature set for declarative data languages. If everyone coalesces to those eventually, it means there's something to it.

I'm getting close to my goal of fitting an entire bootstrappable-from-source system source code as context and just telling Claude "go ahead, make it better".

Model distillation is gift sharing then. It's settled, Carmack said it.

Seems nice.

I launched https://github.com/alganet/tuish yesterday (pure shell backend).

Exporting to pure shell could be a killer feature, especially for smaller and ad-hoc apps (no dependencies, no compilation, etc).

There are pictures in the repo :D

Drawing is a small module though, what tuish does best is terminal compositing. It avoids tricks like cursor parking, which makes it fundamentally different from other TUIs internally. That's why we can render an editor in a partial viewport (non-full screen).

Also, no dependencies to install or compilation steps, just clone and run.

Hi (author here)!

Small TUI toolkit. This is an evolution of an old experiment: https://news.ycombinator.com/item?id=19517992

In the examples, there is a full text editor interface written in nothing but shell and other cool tricks (correct-width terminal tables, box drawing).

Would love some feedback. I tested only on a few selected terminals (WezTerm, VSCode terminal, Windows Terminal), but it should work on a bunch more.

Why would I pay for this? Makes no sense.

It's just confirming to me "yes, LLMs can do it so reliably that someone is trying to sell it, so I can probably just ask an LLM then".

I got my first big job in 2008. Fond memories of that time!

I did well through the 2000 and 2008 crashes. Well, lost my job in 2000 but got an upgrade in 4 months.

Looking backward it looks like everyone suffered during these crashes, but in fact many individuals did fine or even benefited from the realignments.

I like the idea. DOM morphing is nice.

I've done this previously with morphdom to AJAXify a purely server-driven backoffice system in a company.

I would love something even smaller. No `mu-` attributes (just rely on `id`, `href`, `rel`, `rev` and standard HTML semantics).

There's a nice `resource` attribute in RDFa which makes a lot of sense for these kinds of things: https://www.w3.org/TR/rdfa-lite/#h-resource

Overall, I think old 2015-era microdata like RDFa and this approach would work very well. Instead of reinventing attributes, using a standard.

Thanks for the feedback! The RDFa `resource` attribute is an interesting angle I hadn't considered. That said, µJS's default behavior actually requires zero `mu-` attributes; it intercepts standard `href` links and `action` forms out of the box. The `mu-` attributes are only needed when you want to override the default behavior, use patch mode (updating multiple DOM fragments in a single request), or trigger requests from elements that are not links or forms. So in the simplest case, a single `mu.init()` call is all you need. That said, if you want something even more minimal, htmz takes that philosophy to the extreme.

Not exactly what you’re saying, but a bit closer. With this library you set what css classes on the page are “hot”, it fetches the next page state and replaces that part of the page with the new state: https://github.com/robrohan/diffy