3 ms·
So you're advocating inflicting an annoying delay on tens of thousands of people because there might exist one person a) uses ancient hardware and b) uses recen
by IshKebab 3y ago
So you're advocating inflicting an annoying delay on tens of thousands of people because there might exist one person a) uses ancient hardware and b) uses recent software and c) messes with their TERM environment variable?
Ridiculous
- zaxomi 3y agoEvery change breaks someone's workflow: https://xkcd.com/1172/ https://xkcd.com/1172/
- IshKebab 3y agoSo we should never change anything. Got it.
- hnlmorg 3y agoYou can change it though. Several people in this conversation have suggested ways to make that change. What you're asking is different. You want to make a global change to a core application in ways that are incompatible with existing, albeit extremely old, hardware. And the only justification is to speed up a non-standard use case for said tool. And you're pushing for this despite there already being purpose designed solutions to your exact problem. Linux (and GNU in general) frequently makes breaking changes. Like dropping 386 support. But it's done where there are actual real world problems. Like maintainability. Or security (why certain features were dropped from GNU Bash ~10 years ago). I get this delay is annoying for you but it's literally just a 1 (one!!) second sleep: (void) napms(1000); If 1000 milliseconds is that valuable to your productivity then why are you wasting millions of them arguing with strangers on the internet? If feels to me like there a real lack of objectivity in this thread.
- IshKebab 3y ago> If 1000 milliseconds is that valuable to your productivity then why the hell are you waste millions of them arguing with strangers on the internet? Yes it is that valuable to me, because it isn't a single 1s delay. I endure it many times per day (or I would if I didn't fix it for me). And of course you know that little delays cost more than their "raw time" because they interrupt flow. And I'm arguing with people on the internet about it because 1. It's fun to argue with people who are obviously wrong, and 2. I care about other people and I would like them to not have to endure this idiotic paper cut.
- hnlmorg 3y agoIf I'm obviously wrong then I assume you can point me to an independent study that proves a 1 second delay in `reset` has measurable significant impact on peoples productivity?
- IshKebab 3y ago> If I'm obviously wrong then I assume you can point me to an independent study that proves a 1 second delay in `reset` has measurable significant impact on peoples productivity? That's the wrong question. Nobody has done that study because it's obviously bad to have 1 second delays that aren't needed! Show me an independent study that proves a 1 second delay has no negative impact on productivity or satisfaction.
- hnlmorg 3y agoYou're the one making a claim. Not me But I can see nothing further is going to be gained from this conversation so I'll end it here
- phone8675309 3y agoHow often is your terminal getting scrambled to the point where you're running 'reset'? I have to run it, tops, maybe once a day when a remote screen session gets disconnected.
- IshKebab 3y agoVery often unfortunately. But even when it doesn't I use `reset` to clear the scrollback history so it's easier to get to the start of a command. I'd really like terminal emulators to support marking the default top of the scrollback so I don't lose the earlier history but still get the benefit of being able to easily find the start of a command, but I'm not aware of any terminal emulators having any features that do anything like that. So `reset` is the next best thing.
- 3y ago
- hnlmorg 3y agoYes. Because those "tens of thousands" of people have other options available, as has been discussed in this thread. But for people who have physical terminals, which I know is exceedingly small, there is no other option. Hence why the behaviour still exists. If time is your only constraint then use a clear screen hot key or write a function and make it a single char, like the following: function r { printf '\033c' } I'm all for modernising the terminal but in this instance there are already other options that solve your needs better than `reset`.
- IshKebab 3y ago[flagged]
- _Algernon_ 3y agoWindows has also maintained backwards compatibility to a ridiculous extent, and there have been a bunch of "year of the Windows desktop", so I don't think it is detrimental that Linux does the same.
- IshKebab 3y agoThe issue is not about maintaining reasonable backwards compatibility. It's about refusing to fix things and using ridiculous backwards compatibility as an excuse. 1. Even Windows doesn't maintain full backwards compatibility all the way to the 90s, which is what you are advocating. 2. You could even fix this in a backwards compatible way if you wanted!
- hnlmorg 3y ago> 1. Even Windows doesn't maintain full backwards compatibility all the way to the 90s, which is what you are advocating. Oh yes it does! Win32 APIs have been around since the Win95 / NT4 days. And those APIs were themselves based on APIs from Windows 1.0. Then there's those magic files like `CON` that are a remnant of DOS (in fact its even older than that because it comes from CP/M). https://superuser.com/questions/86999/why-cant-i-name-a-folder-or-file-con-in-windows https://superuser.com/questions/86999/why-cant-i-name-a-fold... Also I never said anything about "full backwards compatibility". I just think this specific compatibility is worth preserving because your justifications are weak (by your own admission, you're only arguing about it because you enjoy arguing with people on the internet). > 2. You could even fix this in a backwards compatible way if you wanted! It has been. You objected to those backwards compatible fixes. I've also suggested a way of patching `reset` without relying on buggy usages of `$TERM`. That also apparently isn't good enough for you.