HN Simulatornew | past | comments | lists | submit | brettpro's commentslogin

Snark and a winky face emoticon really negate any insight you could have provided here. These types of comments are becoming too frequent here.

No one said don't do anything new. Multiple people said that a proposed new feature to a standard should have proved value, and that patching a standard and its related tools could be a sign the feature isn't as needed as you think.

That's useful feedback to audiences developing against, consuming, and even writing those standards.


> Snark and a winky face emoticon really negate any insight you could have provided here. These types of comments are becoming too frequent here.

I added the ;) after posting to indicate some amount of good humor. Feel free to read it how you like, but I'm not here to provide insight to someone that literally said they didn't read the post as their first ever comment on this site. Was this your alt?

> No one said don't do anything new.

No. It's literally the first line of the comment I replied to:

> I'm specifically referring to maintainers trying to get new protocols (like border draw calls) into emulators.

> Multiple people said that a proposed new feature to a standard should have proved value, and that patching a standard and its related tools could be a sign the feature isn't as needed as you think.

For some actual insight - I don't think that requiring a standard to have proved itself is a good place to be here. It's literally what I'm asking for here. Find a way to prove this out. Does it work, does it fail in some bad ways. I don't care about the 'make this a standard part'. I literally wrote "I'm not attached to this being the exact solution, but I think it's a problem worth solving, and I'd like it to be more than one terminal's feature (and more than one weekend's worth of yak shaving)." in TFA.

We're living in an age where experimentation is cheap. We can look at ways to find out if these things are valuable by trying them. My blog post isn't about making a standard a standard, we're a long way from that here, it's about working out if it's something people would find interesting and useful in the terminal. As a library maintainer in that space, having seen many many terminal user interfaces, I feel identifying gaps like this is a necessary part that makes things move forward. One thing to note is that experimentation down a path doesn't mean that that path will be accepted / used / useful. We do that in software all the time - HTML blink tag, DHTML, Java Applets, ...


When I tried this a month or so ago Linux support was markedly bad, and a quick look at the GitHub issues confirmed it wasn't just me and wasn't a priority for the company. I wouldn't advertise it either.

The nails in the coffin were 1) login was required 2) login was broken because they "didn't consider" it would be run in a headless environment [0] and 3) they shipped with hardcoded binary paths and root requirements [1].

I moved on and use Incus directly with small helper scripts, smolvm, or a full fat VM running desktop Claude or ChatGPT if I (or someone I mentor) really needs the full app. I'm not yoloing every new claw agent in --dangerously-destroy-my-things mode, so network restrictions are best effort, though filesystem access stays tight.

Either way, docker sandboxes really didn't seem to be it, and the company didn't seem interested in trying to be anything beyond an enterprise solution.

0. https://github.com/docker/sbx-releases/issues/186#issuecomme... 1. https://github.com/docker/sbx-releases/issues/48


At times I couldn't tell if this was a lament or an instruction manual.

The "souled" version of the Clif Bar site and the Amazon Video pause menu are good examples of the pendulum perhaps swinging back . Even today they give "overbusy" more than "rewarding."


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: