Windows is case INsensitive. Just merged two repositories accidentally because of that.
$ cd /tmp
$ mkdir Abc
$ mkdir abC
mkdir: abC: File exists21–30 of 58 posts
Windows is case INsensitive. Just merged two repositories accidentally because of that.
$ cd /tmp
$ mkdir Abc
$ mkdir abC
mkdir: abC: File existsSo, whats the best windows ssh client these days? Still putty ? bitwise? other new hotness? I've been getting pretty frustrated with my new mac and im supe r tempted to try out a Razer Blade.
Tried this recently as an exercise in broadening my horizons. - Expect not to be able to SSH into your machine, for example when you really need to remotely make that git push you forgot before you left work. - Expect either a very slow unix emulation through Cygwin, or a very glitchy one through the new Ubuntu subsystem for Windows. - Expect installing software to be a royal PITA, and expect to start trusting binary…
HiDPI is a mess on Windows. Apple got this right and everyone else still seems to be playing catch up.
Break your habits. Windows 10 has a very specific workflow that is highly efficient, trying to shoehorn Linux, Mac or Windows 7 workflows into it will frustrate you. Learning powershell is part of that.
That's pretty subjective, right? I think plenty of folks would argue that they have a highly efficient workflow on other operating systems already. I would say the ability to pipe things around in UNIX is pretty efficient, or macOS' ability to drag almost anything almost anywhere is pretty efficient. Other than PowerShell, what makes Windows so efficient for you?
Earlier quoted context omitted.
*highly efficient meaning you stick to the full Microsoft-paid stack. Otherwise, not so much.
* VSCode: open source, multiplatform. * Powershell: open source, multiplatform. * .Net: open source, multiplatform. * MSSQL: running on Linux, but there's always Postgres. * Clang: works beautifully on Windows. * Node: first-class citizen. That statement is nothing more than dogma.
Yes, but what does it help when 99.9% of Node deployments is on *nix and they don't match the Windows dev environment 1:1?
Classic Shell (simpler start menu)
7-zip (lzma, etc.)
SyncBack Pro (local/s3/on-insert backups)
JetAudio Plus (BBE harmonic extrapolation mp3 HF restoration)
USBDLM (external hdd serial # based drive letter assignment)
So, whats the best windows ssh client these days? Still putty ? bitwise? other new hotness? I've been getting pretty frustrated with my new mac and im supe r tempted to try out a Razer Blade.
So, whats the best windows ssh client these days? Still putty ? bitwise? other new hotness? I've been getting pretty frustrated with my new mac and im supe r tempted to try out a Razer Blade.
As another commenter said, Windows has its own way of doing things and expecting it to act like Linux or MacOS will just frustrate you.
My recommendation would be to, if you don't build the machine yourself, buy a Microsoft Signature PC. These don't come with all of the crapware that Windows machines tend to come with.
If you decide to install the OS on an existing machine, make sure you find the appropriate network driver and save it on a USB stick first. This is probably the only driver you will actually need - once Windows can connect to the network it can download the drivers for everything else from Windows Update.
Some Windows stuff doesn't work as well as the Mac and Linux equivalents, and vice-versa. The built-in MacOS VPN client and the NetworkManager StrongSwan CPN client are both a lot better (for me, anyway) than the one in Windows 10. On the flip side, accessing network files (through SMB, of course) is lightyears beyond the way Linux and Mac do it - UNC paths are at the top of my list of things I miss about Windows.
Earlier quoted context omitted.
* VSCode: open source, multiplatform. * Powershell: open source, multiplatform. * .Net: open source, multiplatform. * MSSQL: running on Linux, but there's always Postgres. * Clang: works beautifully on Windows. * Node: first-class citizen. That statement is nothing more than dogma.
> * Node: first-class citizen. Yes, but what does it help when 99.9% of Node deployments is on *nix and they don't match the Windows dev environment 1:1?