> it's really no different than vanilla CSS

Is this supposed to be a plus? When you have indirections they're supposed to provide some abstraction and the abstraction might or might not provide the utilities you desire, but there is a point to it. A near 1:1 mapping is completely useless and just a different syntax for the sake of it.

But that's not quite what it is, though.

Probably the most damaging idea ever exiated in frontend dev. I'm glad that AI now abstracts all that crappy tailwind code away so I can stop giving a shit.

"humanoid" robots are as relevant to commercial robotics as AGI to LLM, that is, not at all. As long as they can move on wheels and operate 2 hands (doesn't matter how many fingers), the application is huge already.

Not everyone use AI only for coding, for “code smell” being even applicable here. Many of my skills are just processes distilled from actual sessions doing odd tasks and coordinating different tools. It’s pretty reasonable to assume that it saves the agent from repeating that first time exploration fumbling

Wanting to run a single OS at a time is anti Apple now? Run MacOS or run Linux, why run both and create more problems than it solves and waste resources?

Run both when you need to build for both. Why not run both when you need to?

yes, but you're arguing for running both whenever you need (only) linux?

I’d need both, so I’d use both.

how many people fall into the openclaw trap because they just need a way to command agents from mobile, and cron tasks? Only thing I am missing with codex is the ability to recall anything from any session (I see it in this openclaw "2" release note so I guess it wasn't in openclaw "1" anyway). I guess claude and codex can look up transcripts globally too, just not as a first class feature.

That is exactly what I'm building pond for myself: one store for all my sessions, Codex and Claude Code both and a bunch of others including OpenClaw, and my agents can access it over MCP. It also happens really often that when my agents cannot find something, they just call pond search themselves. Faster that way. Whenever I need a session from a while ago now, I just know it's in pond. Repo, if you'd be willing to give it a try: github.com/tenequm/pond

I am being rude but why are people investing in a bar that ONLY shows icons? This dock thing is a wasteful concept invented by OSX that somehow people think worth copying.

Not to support the idea that good touchpad is apple’s monopoly, but I and most people I know stop having wrist pains by giving up the mouse. If we’re talking about a stupid idea that’s both inefficient and a health hazard, the mouse is it. All the other pointing devices (trackball, trackpoint, rolling mouse etc) make sense one way or another

Needing a 3rd hand for a peripheral is naturally a flawed idea. The only reason I prefer the mouse over the palm trackpad is because it can't interfere while probably still having to use it occasionally. The track point and trackball were better interfaces than both but they weren't a great platform for making Apple look innovative.

the 3rd hand wasn't event what I meant by inefficient, it more that you need an extra surface to move some pointer and do the least possible amount of HCI data transfer. It's so... lame in this age of mobiliy

Yea, moving the burden from your wrists to your finger joints is surely a genius idea and the epitome of health

It would be an adequate argument if such finger pain existed

I'm not sure about the overall argument.. But I think arthritis of the fingers manifests eventually for most people who work with their hands and finger movement combined with any compression on tendons exacerbates carpal tunnel syndrome. Ergonomic I/O makers are essentially experimenting on the population, but less ethically as their bias is in using a bunch of nonsense to further a dialogue that supports whichever patents they obtained.

Personally I don't believe anything requiring 3 hands could be adequately tested given the freedom of movement given to the subject. I think only 2 hand home row keyboard use with specific additional positioning requirements has a flake of scientific rigour. (This is why I could only honestly support the track pointer in the home row as the least risky of the choices as it is the smallest deviation from something with a foundation.)

Not sure why people try so hard to interpret this in such a hostile way. It's very obvious that the 11 days were for the faithful, mechanical, agentic port, and then they followed up by commanding refactoring. The comments about the faithful port not being idiomatic rust are annoying