Exactly the other way around for me! I've been using screen since forever, and had no idea it could do that. Minicom I still know from the dialup dark ages.
C-o here. And C-x or C-p on a few rare nested screens in one particular screen session that I always have open. Those are identified by differently colored tabs in the hardstatus bar which is always visible.
So, essentially, you have to disable mobile data as well as wifi calling, thus disabling the ability to be called entirely until they release the march patch. Nice..
I know in the Netherlands they have these little 'cars', that are essentially mopeds with a roof slapped onto them. They are speed-limited to 30mph and crash safety is on par with what you'd expect from a moped. You can drive these with a moped license (easy and early to get). You can only drive on roads limited to 50mph (most state roads and inner city roads).
I'm not sure why this is allowed as these things are noisy, unsafe, and hold up all other traffic. And they are not limited to disabled people either, anyone can drive these.
They used to look terrible and nobody wanted to drive them, but since they don't require a full driver's license and are not taxed annually, they have become more popular, and now look mostly like regular cars.
Search for 'brommobiel' or 'mini car' to get some examples.
I'm a power user and have been using linux since the early days. Support has actually never been this good. Mostly due to standards in buses and hardware. Even GPU support is relatively good despite the closed-natured mindset.
I'd still never recommend it to anyone who wants something that "just works" though. It will never be on the same level as that needs a ginormous organisation to provide testing, support, documentation. Especially if you follow the Windows model with all the hardware support vs the Mac model.
I like how most of the configuration in this setup is very similar to how I configured systems as far back as mid-nineties. Most applications have a simple single config file, and a single responsibility, true to Unix' philosophy. My window manager needs haven't really changed during all this time. Add a nice launcher that indexes your system and you have most of everything you will need.
I think many New Yorkers realize how bad it is in the rest of the US. HOWEVER! In NYC, the subway is essential, and many people don't realistically have any other option. Especially if you're in the outer boroughs. Even worse, there you also don't have the luxury of walking over to another line if yours is heavily delayed. Walking is too far, and biking is only recently slowly becoming a reasonable alternative.
Yup. Any delay in Manhattan during rush hour, and the trains just pile up waiting to get into Manhattan in the outer boroughs. And in the outer boroughs, you often don't have the luxury of being able to choose from multiple lines. So all in all this means that your morning commute could last anywhere from X ('scheduled' commute time) to X + 45 minutes, occasionally even worse. And you'll probably be packed like sardines inside the cars as well, hopefully with a working AC if it's not freezing outside.
As a EU import, I understand. Actually, most of the city is quite dirty, relatively. It's probably even a US issue. Non-rich neighborhoods simply don't get to spend much on anything serving the public, including upkeep. This goes for much of NYC as well, despite it being a 'rich' city.
The information on schedules and changes due to maintenance are overwhelming for a tourist. At nights and in weekends especially, there are often trains being rerouted in very creative ways. Though all of this information is posted, it's often hard to understand for a non-local. It often mentions station names, which mean nothing to you if you don't live here (and even if you do it's not always obvious). Luckily the locals are always happy to help you with directions, contrary to popular belief, so just ask away!
All of those things sound like they are mostly the product of someone before you being lazy and very poor at writing maintainable software or documentation. This argument is akin to blaming carpentry when someone has built a poorly constructed house.
Sure, it would be nice if you could spend the majority of your time on the fun stuff, and it looks like your predecessors certainly tried. But in that case you should probably not actually write software and choose a more theoretical career path if you can't be bothered to learn how to use a hammer.
In my similarly long experience, I have discovered that it's OK if the tools that you use nearly every day are "arcane", whether they have a GUI or not. Any time invested in getting to learn the tools will be paid back in efficiency later down the road.
As a simple example; an avid gimp user will not click through menus for most of the common actions, but will rather use keyboard shortcuts. It is no different for any CLI environment where you need to memorize a bunch of programs.
It certainly would be nice if your very first early start would focus more on the actual programming, and less on the weird abstract environment that most of us work in. But once you're hooked on programming, and that probably happens quite fast if you are into it, I find it hard to believe that you would not be willing to spend time to optimize your tool usage. The CLI does not get in your way there at all IMHO. The old unix philosophy of having a bunch of very simple tools that do one thing well and can be combined, is very useful in the day to day working environment.
Aha! I do own the Pebble Time Steel and couldn't identify with the issue of the poorly readable screen. I find it reads very well in direct sunlight, and when it's dark there's always the light button. I guess this explains the complaints.
Some nice examples:
A collaborative pixel-based image builder: https://peace-robin-a2dw95.manyminiapps.com/
Analog synthesizer controlled by accelerometer: https://magic-gold-z13d9k.manyminiapps.com/