3 ms·
I'd argue that we shouldn't be adding code (in general, not limited to fish) to support old hardware such as this (or see the crazy list of systems supported by
by raverbashing 6y ago
I'd argue that we shouldn't be adding code (in general, not limited to fish) to support old hardware such as this (or see the crazy list of systems supported by OpenSSL)
A lot of pain in systems comes from unbound backwards compatibility
- capableweb 6y ago"We"? Are you one of the core contributors of Fish? Otherwise I don't see why you'd argue in their place. According to the issue they seem perfectly fine with taking the maintenance burden of any patches to support older hardware, and they are even assisting the issue author to troubleshoot, so not sure what the problem is here? You never know when some customer will put you in front of a vt220 and ask you to solve some arcane issue, and I sure am happy that at least some people care about helping others even if they don't have that specific hardware themselves.
- scaladev 6y agoI appreciate your comment, although I'm honestly surprised that fish maintainers are willing to put any effort into this, considering that fish is a "modern" shell which doesn't take backwards compatibility very seriously and isn't afraid of breaking with the traditional way of doing shell stuff.
- aequitas 6y agoI think it is due to personal nostalgia and technical curiosity. Solving these kind of issues are more of a hobby contrasted to real work that needs to be done on project. Thus sparking more joy and engagement.
- capableweb 6y agoThanks! I don't know if I agree with your "doesn't take backwards compatibility very seriously" point specifically, although they do indeed try to refresh the shell UX a bit. Specifically from their design document[0], there is no mentions of backwards compatibility (except in connection to configurations), but they do mention that one of the goals is to follow posix syntax as much as possible, so seems they do have some care about backwards compatibility. And lastly, "breaking with the traditional way of doing shell stuff" doesn't necessarily mean "doesn't work on old hardware", just means that the shell UX will/can be different, but similar. - [0] https://fishshell.com/docs/current/design.html https://fishshell.com/docs/current/design.html
- ComputerGuru 6y ago> which doesn't take backwards compatibility very seriously I go out of my way to make sure fish still compiles on ancient versions of operating systems (with the most recent compiler you can get on them) and still remains functional in the kernel console (no X), and others on the team go to even further extremes. We’ve argued for weeks over changing the names of variables that might break older fish scripts, even though fish isn’t really a non-interactive scripting language. You’re going to have to qualify that statement.
- raverbashing 6y agoIt's a generic comment, I'm not talking about fish only
- bauerd 6y ago>You never know when some customer will put you in front of a vt220 Yeah with utmost certainty not gonna happen for the vast, vast majority of jobs.
- moonbug 6y agooh you sweet summer child.
- kstrauser 6y agoI’ve been in the field for 25 years, including work inside telco COs and large data centers, and as far as I know I’ve never been in the same room as a VT220. I doubt that many of my more junior coworkers have even heard of one. I know what they are and how you might still use one today, but they’re extremely rare outside maybe a couple of very narrow niches.
- Aloha 6y agoI would bet that you have been in front of a VT220, or VT320, or a real terminal that could emulate one of them. Nortel Meridians for example (yay, ld21) use a serial terminal, usually read DEC, usually a VT220 or 320. But there are WYSE (and others too) terminals too, which usually can emulate a 220, and so on.
- kstrauser 6y agoThat’s certainly possible, but if so it wasn’t something I had personal contact with enough to register that it happened. And I definitely knew what those terminals were, so I’m pretty certain I would have noticed that “oh, hey! A real VT220!”
- icedchai 6y agoYep, they are very uncommon these days. When I was in college in the mid 90's, VT220's were still common on some parts of campus. A few years later, I had a job at a mostly DEC shop. They had a few terminals here and there, connected to Alpha Servers and a couple of old VAXes. I haven't seen one in the wild in a little over 20 years...
- dmos62 6y ago> "We"? Are you one of the core contributors of Fish? Otherwise I don't see why you'd argue in their place. It's not about arguing in their place. It's about thinking where our collective (includes the mentioned developers, me, and you as well) wants to take its technology. What afffects you, affects me and vice versa. We're not as seperate as you make out.
- rutthenut 6y agoI'd argue that supporting a known legacy standard makes more sense - it isn't exactly 'unbounded', it is compatibility support.
- senko 6y agoIf you read the issue comments, you can see this: > Specifically, (pseudo-)serial devices, like the Linux console VT, initialize the rows and columns of the tty device to zero. That confuses fish since it now believes that nothing will fit on a line. Fish expects to be running inside a terminal emulator (xterm, konsole, iTerm2, etc.) which sets the tty width and height to the correct values. So it's not only old hardware. It applies to modern hardware when you're using console to access a Linux server, which is not at all uncommon for data centers or headless servers.
- raverbashing 6y agoThanks for pointing this out, I had read this and really is an issue with fish
- masklinn 6y agoIn fact the somewhat more useful issue is https://github.com/fish-shell/fish-shell/issues/3740 https://github.com/fish-shell/fish-shell/issues/3740 where this problem ended up finally being understood / diagnosed (it's also linked at the very end of TFA).
- irateswami 6y agoThis is why I love old hardware, even as a relatively "young" person in tech. It really keeps you disciplined and honest with your code. I have three older Xeon machines with very bad specs that I use as a Kubernetes cluster, and it's where I test a lot of my deployments. If whatever I thrown on it will run well, then it'll be blisteringly fast on an AWS server.
- bayindirh 6y agoAs a software developer, I politely disagree with your view. Some of the core standards powering UNIX/Linux is stable since eternity. Implementing these standards well enables a ton of backwards compatibility out of the box. There are libraries which still protect their PDP-10 compatibility despite being maintained and refactored for current generation systems. OTOH, every good software should build upon its foundation. When you have good foundation and a good interface to it, touching it is almost unnecessary in the long term.
- mhh__ 6y agoI think that pain can also be a symptom of bad architecture - i.e. a lot of systems are clearly made in the image of their forbearers, so it shouldn't be totally impossible to restrict a subset of behaviour to make it work on (say) a physical terminal instead of emulated one.
- GekkePrutser 6y agoThat's what termcap/terminfo is for. It's not just a matter of backwards compatibility, but also forwards. Right now the common term type is xterm (or variants thereof like xterm-256color). 20 years ago it was vt100. Will it still be xterm in 10 years from now? Considering Xorg itself is claimed obsolete by its own maintainer makes me wonder if it will be. Good thing we already have a mechanism to support smooth alternatives for terminal types.
- kps 6y agoWhile I personally use `tput` in scripts where it matters, I think an argument can be made that effectively all terminals now in use support ANSI X3.64 aka ECMA-48 aka ISO/IEC 6429. The 37-year-old VT220 does. The greater sins I see today are assuming line length and assuming background colour.