What proper window manager shows tab group list at the top of the current app window and allows shortcuts/mouse to reorder the list and also allows moving a tab outside of this list to another tab group?
Sway and i3. But when a WM does it, you can mix different apps in the same tab group, and your tab key binds can be the same as your WM key binds. You don’t have to remember alt+h for tabs, win+h for windows, etc.
But I’m just busting your chops, don’t listen to me. I don’t even use i3/Sway, or use tabs at all. Everyone has their own workflow that works best for them.
Wait, really? So I’ve used the terminal for everything for decades, and now, because of vibe coding, all The Kids have joined me? I don’t even know how to feel about that. Better terminals are nice though.
Right? It’s been kind of funny watching everyone “rediscover” the terminal and I’m over here feeling like a true graybeard “silly kids, I’ve been here the whole time.”
What’s old is new again is apparently just as true in tech as it is in fashion.
It's because the web developers who destroyed the web are now taking their mess with them into more obscure places, such as terminals, hardware and AI.
That's probably why it is so hyped up as it is right now.
The HN zeitgeist has something of a love/hate relationship with the web, I've noticed. HN in general seems to skew a little older than a lot of online communities, so a lot of HN users were adults back in the early days of the web/Usenet/etc. There's a tendency to view those days with nostalgia, leading a lot of people to feel like the "good old days" of the web were "ruined" by the modern shift into more interactivity, fancier/prettier design, etc. And "web developers" are the ones proximately responsible for the shift, so they get the hate too.
I laugh every time I see someone on HN asserting that the web "shouldn't" be used for anything beyond "documents and lightly interactive content", which is not uncomment. There's some real old-man-yelling-at-clouds energy there.
Have you used the web recently? It’s a mess. Most sites don’t actually work well. Everything is slow and bloated and ad-filled, pulling hundreds of megs from hundreds of hosts to display a single page covered in popup alerts, subscription begs, cookie warnings, and paywalls.
I think terminal workflows are intimidating for a lot of people, because the discoverability is lower than GUIs. You can't necessarily intuit how a CLI works, you have to read the documentation or watch a tutorial, which my 10 years in the IT industry has taught me a big barrier even for really experienced SWEs. The new coding TUIs are a more gentle introduction to that.
> ... because the discoverability is lower than GUIs.
The UI paradigm created by the emacs transient package [1] can improve the discoverability of CLI commands significantly. It's one of the components of magit, the famous git frontend, that makes it so awesome. It's discoverability is very close to that of GUIs and somehow even more pleasing to use than GUIs. I wonder if someone is trying this on terminals.
I remember the first time I heard a girl use the word "lol" (early 2000s) and thought to myself: Normies have hit the internet.
I've used a terminal as my main interface FOREVER, and I'm amazed that people are joining this healthy habit of interacting with the computer as CREATORS.
Doesn't Google have some agreement with Reddit? They are probably hooked into some kind of firehose stream and index everything in basically real time.
I've watched 30 kids get off at their school in the morning. It takes 15 seconds. By your logic, 30 stops adds 15 seconds to a bus's schedule, which is pants-on-head crazy.
Emptying a school bus completely is a lot faster than a city bus stop where people are simultaneously trying to get off the bus and then the new people are also trying to get on the bus and jockey for position and for a seat before the bus can start moving again
So this used to happen on Dublin Bus, but a while back they solved it with an astonishing innovation... a second door! You get on at the front and off at the back. Given that this has been common elsewhere forever, it's unclear why it took them so long, but...
(Bafflingly, they went through a transition period where ~all of the buses had two doors, but the driver rarely opened the back door. It wasn't really until covid that using the back door became standard. Improved things greatly.)
> and jockey for position and for a seat before the bus can start moving again
Do urban buses where you are require people to be seated? Didn't realise that was a thing anywhere. Any (urban, non-intercity) bus I've ever been on takes off as soon as the last person gets in.
A second door is good. Make it even better by people getting on and off from either - those getting off should be first. Many systems work this way and it works great. Trains oten have even more doors, but for a but that often isn't possible.
My point is that you're totally disregarding everything a bus does to stop apart from waiting for passengers to board and de-board. At the very least it has to slow down, then accelerate. Half the time it has to swing the ramp out, which takes forever. Maybe someone has to load or unload a bike. Then it has to re-merge with traffic, and maybe every 10th car will let it in, so that can take a long time too. I don't even know if waiting for passengers is _half_ the time spent, let alone all of it.
I've never been on a city bus where the driver waits for people to be seated. Hell, when I lived in Vancouver, they would start moving before everyone had even paid their fare, basically as soon as the door was closed.
Most optimization is a curve. Arguing for moving closer to the top of the curve is not the same as arguing for moving all the way to the minima on the other side. But why do I have to say that?
> I suspect that removing half of the bus stops in a city will piss people off and cause even less ridership.
Oh do you now? Where do these suspicions come from? How much time do you spend on city busses? Do you have any idea how absolutely infuriating it is to be sitting on a bus while it makes stop, after stop, after stop, after stop, every single one a block or two apart, crawling down the road at a walking pace? All the while backing up traffic behind it and eroding whatever support the transit system had with the majority of the tax-paying public that never uses it.
I suspect that people find a destination on Google Maps, click the navigate button, see that the bus takes 3x as long as driving, and take their car or an Uber.
You're making suspicions about suspicions without numerical data.
According to my cities 2022 annual report (where are 2023-2025?) they provided precisely 464344 unlinked pax trips (UPT) so someone stepped aboard a bus and threw money in the real or virtual fare box 464344 times that year. "Sources of operating funds expended directly generated" which I read as annual fare revenue was $660748.
We have a very simple two tier system $2 for adults and $1 for seniors and disabled. 2(464344-x)+1x=660748 x=267940
So we only had 196404 healthy young adult bus riders that year vs 267940 senior citizens. Your experience is not unusual but also is by far not the majority; a SUBSTANTIAL majority of the people on the bus in my city are too old or too sick or too blind to take long walks in the rain, snow, ice, heat, cold, etc.
Honestly the bus is so slow, if they could walk, they'd probably just walk. So it should not be overly surprising that most on the bus quite literally can't walk, and really need bus stops close together for disability reasons.
So all of this theoretical "well it would be so much faster if there were fewer stops" is irrelevant if the served population is primarily physically disabled, and the system can't survive. And we'd be talking about excluding one of the most powerful voting blocks in the city, that being old people. Eliminating stops would eliminate or reduce 58% of the current riders which would shut the system down, I don't think it could politically survive a hit like that.
Ironically that shutdown might be good as everyone would be better off both financially and environmentally in cars than in buses. Bus exhaust is not exactly perfume to mother nature LOL, and essentially our bus program is not a transit system, its a corrupt jobs program for drivers, mechanics, and especially for highly paid administrators.
> a SUBSTANTIAL majority of the people on the bus in my city are too old or too sick or too blind to take long walks in the rain, snow, ice, heat, cold, etc.
Maybe my city is different, but in every city I've spent substantial time in, there are little tiny busses for those who are not able to walk or roll the average distance between a stop and their home or destination. They are direct, point to point shuttles. If no bus is available, they will send a cab. Those buses and cabs are exactly why you don't have to run a bus up and down every road, with a stop in front of every house, and a driver who can escort passengers to their door. They are astronomically expensive to operate, but the only way to make a transit system that serves everyone.
But in my city, we pay a small fortune to run these little busses, and then _also_, for some reason, assume that no one riding the main system has any mobility.
Also, I'd argue that the reason a "substantial majority" of your transit population is "old, sick, or blind" is because it's such an unattractive option for anyone who has a choice. When the bus is slower than riding your bike, you're not getting Olympic athletes on that thing.
It's all the stuff that people always mention; they are not wrong. You spend a decent amount of time... conversing with the compiler about lifetimes and, in my experience, even more so about the type system, which is _extremely_ complicated. But you also have to keep in mind that Rust got very popular, very fast, and the tail end of something like that is always a negative reaction. The language is the same, despite the hype roller coaster.
I find Rust's complexity freeing, in that there are often at least a few ways to express what I want, and I can choose the one I feel best fits the use-case and my desired ergonomics. (I also like that there are often ways to express exactly a very precise want, owing well to the Rust principle of "zero-cost abstractions.") However of course, that very same complexity can make it unclear which approach may best serve a given objective, and lead to false starts, wacky implementations, or even giving up entirely.
> I think I need a lot more info about this migration
Doesn't sound like it's some Fish-style, full migration to Rust of everything. Seems like they are just moving a couple parts over for evaluation, and then, going forward, making it an official project language that folks are free to use. They note that basically every browser already does that, so this isn't a huge shakeup.
Then you're not really covered by the article? A colorscheme is all about... color. A TUI is about the content and function. I think there's room to have user-defined 256 palettes that are used by default, while colorschemes can use true color and be chosen by the user if they desire.
But you do have to run a proper window manager so you don’t have to require tab support in every single app. ;)
reply