Windows Terminal to be the default for command line applications in Windows 11 Microsoft is to make its new Windows Terminal the default for command line applications in Windows 11. For last few years, the default terminal emulator for Windows was the Windows Console Host, conhost.exe, meaning that shells such as the Command Prompt or PowerShell opened up inside it. The open-source Windows Terminal …
Agreed, but the fact is that Borkzilla still doesn't know what a true kernel is.
Windows started out as a GUI layer over DOS, and Borkzilla still hasn't made the transition to a true kernel. Everything is tied to the UI.
Besides, if you think that Borkzilla is going to make the Windows Experience (TM) something you can stick another UI onto like in Linux, well I have a bridge to sell you.
You’re incorrect. Everything is not tied to the UI in Windows, and Windows systems can be run without any UI stack running at all (Windows 10 IoT). Just because a configuration doesn’t make sense to offer to a wide audience, it does not follow that it’s not possible.
If we’re speaking about “true kernels”, then as someone who uses Linux daily, generally likes doing so, and earns a living from it, I will still confidently assert that NT is a better kernel than Linux, any day of the week - it’s a shame it’s closed-source and unlikely to ever be fully opened. For that matter, so is QNX, and so is Mach or XNU, as Apple call their Mach-ish kernel. Linux’s killer advantage over all of those has never been its technological prowess, but rather its openness and fast update cycle.
In a better version of this world, the BSD networking stack would have been brought into Linux very early on, and someone would have taken the initiative early to make the output of the Linux-specific tools much more amenable to scripting than they are. Now, those early, poor, decisions have ossified, just like they do with every mature operating system.
(In a similar better world, MS would have got religion about twenty years earlier than they did, and would have provided a full Unix user-space on the first Windows NT release, to run beside the GUI, as Apple does on MacOS. In that world, though, I don’t think Linux would have ever got traction, and they would have extended their market dominance even further, so maybe it’s for the best on balance...)
I'll bite on the "...Unix user-space...to run beside the GUI, as Apple does on MacOS."
Apple didn't just provide a GUI over top of the *nix base; they perverted the file system so badly that it is virtually impossible to do what would would be very simple on other platforms. We're wrasslin' with this right now, trying to get a basic, simple, JavaFX application running on their beasts.
I honestly don't understand the Apple fanbois. Have you never worked with real *nix systems to think that perversion is a "real" OS? Is a fancy GUI shell so important to you that you're willing to blow off thousands of interaction and platform mistakes just so you can click an icon that is semi-transparent and created by an Apple Artiste(tm) instead of "hacked" by some open source project?
The foundation of an OS is far more important than the GUI to people who use these beasts to earn a living...
At launch, MacOS X was a BSD-derived Unix-based OS. Yes, that heritage means things were different to Linux (from the System V lineage), but Linux is not the definitive Unix, any more than McDonalds is the definitive meal out, or Windows the definitive GUI. Over time, the freedom to do whatever you want in MacOS has been limited (to a point where I no longer use Macs), but it fundamentally remains a Unix-based system, with fork() and file-descriptors.
I’d suggest your problem with deploying JavaFX applications is down to “JavaFX” rather than MacOS X, but the issues appear to be in not following the packaging rules for making desktop applications under MacOS. Blaming the OS for enforcing its rules, when you didn’t even check them doesn’t make the OS wrong. You might as well complain that your Linux software couldn’t dynamically link against the .so files you’d installed directly under /etc/.
That app-bundle folder layout might be a mild pain for developers, but it makes it really easy to completely remove applications on MacOS; and, having written tools to handle both, I can say that making an OS X app bundle is way simpler than writing a deb-file that ensures that everything gets restored properly on uninstall.
I don’t know how to answer your rant about icons, as I didn’t mention graphics. Still, if you felt better afterward, at least someone got benefit from it...
Personally I wouldn't be proud of torturing myself with the equivalent of green-screen technology. And if a Windows box is so far gone that I need a TTY session to fix it, then it is time to restore from backups.
You do backups of your Windblows workstations, being a good sysadmin, right? :)
Personally, I find wading thru' a GUI to be far more tortuous than targeting the problem with a well chosen command or three at a shell prompt.
In a well maintained system, the answer is almost never "reach for the backups". I have proper backups, mind ... not quite paranoid (yet), I prefer "pragmatic".
I'm not a good sysadmin, I'm a fucking excellent sysadmin. As such, I don't do windows. Far below my pay grade.
Not my downvote, BTW ... have a beer in compensation :-)
"it's been decades since I wanted or needed to login through a serial port."
Not a systems administrator, then?
If you are wanting to do that because the GIU has crashed , wouldnt you just use the network connection for that?
RDP? or even WMI?
It'd save you a walk too
"It is frustrating in 2021 to find Microsoft blatantly engaging in anti-competitive practices once again,"...
Here's another bit of mictosoft's shenanigans along those lines. Create a hyperlink from a ms word or other office doc pointing to Google Drive/Docs/Forms. Enjoy the quite unhelpful Google help screen. And if you click on the link it suggests, you're presented with an entirely fishy website to upgrade your browser. This bit of tomfoolery bit us today and has been reported at least since 2016.
Windows 10 makes a fine gaming platform that runs VMWare for doing the real work. As long as my VMs get backed up regularly, I don't stand to lose much except time if the box goes down hard.
I haven't worked on Windows in well north of a decade - since an Access/VBA (*shudder*) application back in 1999-2000.
Why would I want to develop applications for a gaming platform? :P
It's frustrating Vivaldi are calling out MS for this behaviour, when Google are far worse for anti-comptetive behaviour in the browser area and have been for a long time. That is NOT a defence of Microsoft BTW, it's really annoying when you get the Denholm style "ARE YOU SURE?" when you try and change the default browser.
My biggest annoyance with development on Windows was when I SSH in and there is no terminal multiplexer (i.e tmux, screen).
What do people do? Open up loads of tabs and make loads of SSH connections into the same machine? That feels janky. Or do you just add some POSIX layer and run tmux in that? Unfortunately that messes with the build environment.
I am surprised powershell never got it. Or at least a proper fg resumable job control system.
I absolutely love it. The first thing that launches as I log in is the new Terminal.
Mine is set up with a nice little logo in the upper corner to differentiate different systems. My ssh session to my synology box has a synology logo. My Ubuntu WSL2 installation has a penguin, and so on.
256 color VT-102 support and modern looking (unless you switch to the 'retro' look).
Um. VT102 was strictly a monochrome (IIRC, either green, grey or amber on black depending on the exact model).
The colour model in the VT100 range was the VT125, but that required and external monitor for the colour display (the internal one only being greyscale), at least in the docs. I've seen.
And the colour support was incompatible with the PC console colour escape codes that we know today.
So I would say that if it's ANSI compatible with PC colour codes, it's probably more like xterm-256color.
Using AWS, unlike Linux servers, there's no console to get onto a Windows server. If, for example, you disabled the network interface, messed up the IP, etc your system will automatically terminate unless you have some override. I suspect the same for Windows 11. I do not have experience is Azure but I suspect this is how you would get back onto your box if you fudged up the network stack or connectivity...
Can’t recommend SuperPuTTY highly enough, open source, easy to use, plays nicely with WinSCP and provides quick and easy windowing and multi-tab session layout. Windows Terminal feels very disappointing given how much announcement there has been. It’s a not very user friendly terminal (emulator) in comparison to Mobaxterm (which I avoid but has been around forever) and SuperPuTTY.
Agree with the tmux sentiment - tmux with a mouse would be super!
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
