71–80 of 467 posts
Earlier quoted context omitted.
I can resize, copy/paste and change font/color/transparency settings on my cmd.exe without any problems. I get your point but they really improved it since Win7/8
I've used it regularly on Windows 10 and I still have to "mark" text to copy paste. Am I missing something?
Earlier quoted context omitted.
I've tried to adopt the alternative bash systems on Windows, and they are nowhere close to terminal options on OS X (or Linux!). It still boggles my mind why we have to stay within the limits of the cmd.exe UI, with the lack of window resizing, easy copy/paste, and proper font rendering. Then, on top of that, Windows will never have a proper unix-like filesystem. I just can't go back to that. The only thing windows h…
I don’t use cmd.exe for anything. It’s Powershell all the way. Powershell, while different from the BASH way of doing things, is a really nice commandline tool.
Earlier quoted context omitted.
FTA: Most people that I showed the Surface to were impressed by what they saw, but almost always came back to the same thing: it doesn’t run macOS. I’m increasingly frustrated by this because it’s almost always a misunderstanding of how far Windows 10 has come, and how compatible the workflow now is regardless of what you might do for a job. I suspect most people haven't touched Windows since years ago and it's time…
I've tried to adopt the alternative bash systems on Windows, and they are nowhere close to terminal options on OS X (or Linux!). It still boggles my mind why we have to stay within the limits of the cmd.exe UI, with the lack of window resizing, easy copy/paste, and proper font rendering. Then, on top of that, Windows will never have a proper unix-like filesystem. I just can't go back to that. The only thing windows h…
Such articles always give too much importance to the hardware (which is somewhat important, no doubt) and not enough importance to the software. Many people are looking for quality alternatives to Macbooks, Mac Mini, etc (myself included). Mac Mini hasn’t been updated for 4-5 years. So, I started setting up a Windows desktop as a Mac Mini replacement. But when it came to finding all the alternatives to the OS X softw…
Agreed. Windows updates and the fact that it still doesn't have a viable shell after 30 years make it a no go. Powershell and Ubuntu Bash on Windows10 isn't as nice as having built in native support.
Earlier quoted context omitted.
All of those things were fine, as far as I can tell. What did you run into specifically? I could run npm stuff, compile with Gulp or webpack..
It's been like six months since I tried, because Fedora does great for me now, but in Visual Studio Code Ruby/Rubocop threw a rod, using a Linux-based .NET Core confused it, and anything Java was a nonstarter. For JavaScript, I do usually run `yarn watch` (workspace-level through oao) in a terminal and that works fine, but stuff like eslint/tslint integrated into VSCode was regularly a real pain. Worse: because VSCod…
It would be neat if the config file were JavaScript that's executed on startup like Emacs does. My init.el has a couple functions that behave differently under Mac (it still calls it NextSTEP, how cute) and Wayland (which it nostalgically calls X). After "accidentally" destroying my last corporate issued Windows install, I never went back and ripped the Windows-specific part of "set-perfect-font-size".
Earlier quoted context omitted.
It's been like six months since I tried, because Fedora does great for me now, but in Visual Studio Code Ruby/Rubocop threw a rod, using a Linux-based .NET Core confused it, and anything Java was a nonstarter. For JavaScript, I do usually run `yarn watch` (workspace-level through oao) in a terminal and that works fine, but stuff like eslint/tslint integrated into VSCode was regularly a real pain. Worse: because VSCod…
> doesn't really support per-platform configurations It would be neat if the config file were JavaScript that's executed on startup like Emacs does. My init.el has a couple functions that behave differently under Mac (it still calls it NextSTEP, how cute) and Wayland (which it nostalgically calls X). After "accidentally" destroying my last corporate issued Windows install, I never went back and ripped the Windows-spe…
With the pounding I've put on my hands, emacs is mostly a nonstarter, so I'm jealous.
Earlier quoted context omitted.
FTA: Most people that I showed the Surface to were impressed by what they saw, but almost always came back to the same thing: it doesn’t run macOS. I’m increasingly frustrated by this because it’s almost always a misunderstanding of how far Windows 10 has come, and how compatible the workflow now is regardless of what you might do for a job. I suspect most people haven't touched Windows since years ago and it's time…
I've tried to adopt the alternative bash systems on Windows, and they are nowhere close to terminal options on OS X (or Linux!). It still boggles my mind why we have to stay within the limits of the cmd.exe UI, with the lack of window resizing, easy copy/paste, and proper font rendering. Then, on top of that, Windows will never have a proper unix-like filesystem. I just can't go back to that. The only thing windows h…
Such articles always give too much importance to the hardware (which is somewhat important, no doubt) and not enough importance to the software. Many people are looking for quality alternatives to Macbooks, Mac Mini, etc (myself included). Mac Mini hasn’t been updated for 4-5 years. So, I started setting up a Windows desktop as a Mac Mini replacement. But when it came to finding all the alternatives to the OS X softw…
As a Linux user (who also owns a Macbook), I find OSX to be a weak substitute. Many features (that we take for granted in Linux-land) require downloading binaries from unknown sources, vastly inferior package management, can use 32 gigs of RAM, relative lack of server-side packages, installs and updates take longer, poor support for NVidia etc. But this is all just my opinion - I'm quite used to running Linux.
Windows is actually a fine OS too - just different. In fact, running on an uncountable number of hardware configurations is a feat of engineering. Not to mention backward compatibility.
Even less ports. Not upgradeable. Not serviceable. Author wants UNIX tools but Linux doesn't even work correctly with the device yet.
Earlier quoted context omitted.
It's everything around baseline development that sucks when using WSL, not WSL itself. WSL itself is really cool. What's not cool is dealing with linters and compiling tools and all the other bric-a-brac that has to cross the Windows/WSL divide. Some of them have been fixed to support WSL, others haven't, knowing which have and which haven't is a crapshoot, and WSL is a third-class citizen at best so good luck waitin…
Try Cmder.