Introducing Windows Terminal
devblogs.microsoft.com
devblogs.microsoft.com
Meanwhile, macOS will get new emojis in 10.15.
Also, I don't recall macOS terminal being open source.
How has Microsoft surpassed Apple in hardware when Apple’s main product is a phone and Microsoft doesn’t even make a phone?
Agree, one of many reasons why I prefer Linux.
> I’ve never seen a good one on windows. Perhaps this is it.
There is cmder, which IMO was not only usable but also pleasant (looked nice, tab completion, history).
> How has Microsoft surpassed Apple in hardware when Apple’s main product is a phone and Microsoft doesn’t even make a phone?
It is a bit unfair to suddenly stop considering Apples laptops just today, again IMO.
Ive and Newson are more interested in making useless aesthetic baubles for the Gulfstream V set than utilitarian devices for work.
https://www.cnn.com/style/article/jony-ive-diamond-ring-soth...
In general I just get the impression that the top executives at Apple treat the Mac as their neglected red-headed stepchild which they'd like to throw down a well at the first opportunity.
I’m not complaining about any of these updates btw, I just think bringing in a comparison to Mac about terminals doesn’t make much sense
MacOS + brew + iterm2 and ZSH make it the best developer setup
As long as WSL v2 has better filesystem perf, it'll be pretty great.
(To be quite honest I agree - but Apple doesn't make any hardware of interest to me to run MacOS on).
I use an external Magic Keyboard 2 without the 10-key as it fits on top of the keyboard of my MacBook as if it should have been the keyboard all this time. But it was an expensive keyboard and not a suggestion I would give many people -- the keyboard should just work.
So after a long time having been OS X-exclusive, for the past year I've used both Windows 10 and Linux. I've really been equally happy and frustrated with each - all 3 of the majors have their strengths and weaknesses. I think OS X overall has the balance I prefer, but it's by a far smaller margin than I would have thought, say, 5 years ago.
I want a new MacBook but will likely wait until my late model top-of-the-line 2013 MacBook Pro dies and buy the Arm based ones they're rumored to release because I simply can't afford a 3k+ laptop now.
In my country, Apple computers moved into the must depreciate for 4 years territory, which is simply unacceptable to corporate buyers there (as depreciated asset, it the paperwork is more involved, and therefore needs additional time and expenses). Meanwhile, Lenovo or Dell sales know how to make the price right, so everybody is satisfied.
My 2015 rMBP was 1 EUR below this limit. I don't know what to replace it with, if needed.
For machinery and buildings, OK. But for a laptop, that maybe barely survives it's depreciation period? Well, no. Folks have other things to do than paperwork for laptops.
The entire point of the asset depreciation is, that the state wants the tax money as soon as possible, and shift your deductibles into future. What you want, is to shift as much as possible of your deductibles into the current year (and it is cash out in this year, after all). I and many others don't see why small, relatively quickly consumable items like laptops should be handled the way big assets are, and the sales at other vendors understand that very well.
If you are a small company with external accountant, it will be significantly more than 1 EUR in labor and paper.
I use the keyboard that came with my 2001 Mac Cube. You can't get a more real keyboard than that.
(At this point Windows 10 offers more ways than macOS to transparently see all the telemetry by turning on and using the Diagnostic Data Viewer, and through many pages of Privacy information documentation on Microsoft websites.)
macOS and iOS have as many in-box first, second, and third party apps in the out-of-box experience as Windows 10, have similar "advertisements" of suggested apps in the app store and search (Siri suggestions), areas which are similarly "core OS experience". Everything is far more alike than it is different between Apple's operating systems and Windows right now, even if you don't see it.
The telemetry that Home is not allowed to opt-out of are the same bits of telemetry that Windows did not allow opting out of nearly at all in versions of Windows 10 prior to 10. (Especially, Windows Error Reporting has been opt-in by default in Windows since XP.)
Personally, I need my OhMyZSH config to make sense of all the git stuff I deal with.
Early versions of OS/X were dire, I remember being able to consistently crash a machine just by unplugging a USB stick.
It would be nice if the unix tools were updated but you need to blame GPL 3 for that rather than Apple.
Do you? I am not trying to be snide here, but WSL seems to show that you can effectively include GPL3 userland in a proprietary system. WSL provides full interoperability with the native Windows system and NTFS filesystem on Windows 10. The next version will even include the Linux kernel.
If Microsoft can ship an experience as part of the OS that includes these applications in userland, why can Apple not?
How can I be expected to trust a computer/OS that I can't fully configure.
I've been looking for a Windows replacement to Cathode [1], a macOS app that makes the terminal look like a CRT monitor. Not just the colour scheme & font, but with screen jitter, image persistence & glow, static, scanlines and even sound effects sampled from old computers. For the times I have to use a terminal, it really makes me smile & enjoy the work.
Linux has Cool Retro Term which is similar, and there have been efforts to port that to Windows that have failed. I could probably run Cool Retro Term under WSL2, but Windows deserves something native.
It seems more likely that an indie developer might be able to fork Terminal & create their own than Microsoft building this in. (As much as I like the idea of Windows having a Fruity IIe terminal theme built-in.)
Cathode charges $5 which is much too cheap - I'd pay $20 easily (maybe more) for something that brightens up my work day the way Cathode does.
But I'm not a fan of the ligatures they've shown in the video / screenshots. This was discussed on HN recently after this article got posted: https://practicaltypography.com/ligatures-in-programming-fon...
Luckily, the font seems to just be an option and not something forced on you.
I’m excited to use the new terminal with WSL2 - maybe it will come close to iTerm2 with Docker.
Also Powershell is a shell not a terminal and it's awesome.
Last time I checked ConEmu still lacked horizontal scrolling, so it looks ugly when the text gets word wrapped.
I've been using it for a while and have been very happy with it and have for all that time wished that they would just adopt it as a default app. Oh look :-)
I haven't been able to find this out. I even tweeted at someone on the Windows Terminal team and didn't get a response.
EDIT: I looked through the github repo and it does appear to support sane key equivalents. Nuggan be praised!
I think you may be referring to the old, awful, architecture.
ConPTY may be pretty cool given the compatibility requirements but only a madman would port it to unix.
[1]: https://devblogs.microsoft.com/commandline/windows-command-l...
Saying "shipping a new command shell". Unfortunately the URL gives me a 403.
> So good luck with your replacement command shell. I hope you figure out how to run batch files.
Yep, seems passive aggressive
The article is at https://devblogs.microsoft.com/oldnewthing/20050909-24/?p=34... but the link is specifically to a comment that isn't preserved. At any rate it was probably just a comment where someone asked why MS can't ship a new command shell.
This was a late-breaking change and for a few versions of DOS you could set SWITCHAR=- in CONFIG.SYS to get the Unix behavior. When set "dir /s C:\whatever" becomes "dir -s c:/whatever".
You can literally blame IBM for this divergence. Without them pitching a fit about it DOS/Windows would have had the same switch syntax and path separators as Unix.
I've been using Unix for 20 years, switch to pwsh 2 years ago, never typed backslash ever.
In other words, you can balance your environment for speed vs features.
I believe Pwsh will get considerably faster in the future given that optimizing it will pay out on nano server which currently boots faster then PowerShell is loaded in it afterwards (which rly sux).
bash requires scraping everything and is inherently brittle as a result, which has always bothered me much more.
Case in point: I compiled it quite easily and it crashes on launch. Not ready for widespread use, yet.
Hopefully it will also work on the Windows 10 LTSB builds when released.
They’re chipping away at each little thing that holds devs away and making sure the world knows it.
It's worth keeping in mind why, it's to get developers interested in their proprietary platforms. These are the embrace and extend steps.
Let me know when they switch to GPL licenses and can't pull the extinguish step.