Live data from Hacker News

Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

github.com

51–60 of 99 posts

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#51
post #4

Microsoft is just on a roll when it comes to open source. - Windows Terminal is pretty solid, and fast. Dare I say, nearing rxvt-unicode/kitty speed. There are some remaining terminal corruption with tmux + vim sessions, but soon enough it'll be replacing hyper/conemu for me. - WSL 2 alleviates file system issues that plagued WSL. I recently wiped debian off my Thinkpad because there's no point, I get everything I ne…

- Windows Terminal is nice but the windows command line is not. I don't like PowerShell, it is too verbose. - WSL 2 is not stable and it is only available for the Windows Insider program. And it does not have X. - Windows 10 drivers sucks. For example, Intel Graphics drivers has a lot of bugs. - ClearType has been improved but Linux and Mac font aliasing is a lot better. - I cannot upgrade my laptop to the last Windo…

Regarding Windows updates, I'm not aware of anything the vendor can do to prevent you from upgrading?

Microsoft does stagger updates over quite a long period, my guess is that's whats happened. If you want, you can get the update early by using Windows 10 Update Assistant[0]

Regarding the command line, there are more options than PowerShell (which I also really dislike); for example, if you install Git for Windows, you also have the option of installing Git Bash - all the goodness of bash, in Windows!

[0] https://support.microsoft.com/en-gb/help/3159635/windows-10-...

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#52

Earlier quoted context omitted.

- Windows Terminal is nice but the windows command line is not. I don't like PowerShell, it is too verbose. - WSL 2 is not stable and it is only available for the Windows Insider program. And it does not have X. - Windows 10 drivers sucks. For example, Intel Graphics drivers has a lot of bugs. - ClearType has been improved but Linux and Mac font aliasing is a lot better. - I cannot upgrade my laptop to the last Windo…

>I don't like PowerShell, it is too verbose. alias >Intel Graphics drivers has a lot of bugs They suck everywhere. I've had nothing but problems with HD4600 on Linux. Frequent video player crashes, kernel lockups, glitches, the whole shebang. >- ClearType has been improved but Linux ... font aliasing is a lot better. I have the opposite experience. Depends on your display I guess. >I would like to remove the task bar…

I agree on the graphics drivers - you can't really hold that against Windows itself! IME I've had a lot of issues with Intel, AMD and NVidia drivers, on both Windows and Linux.

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#53
post #4

Microsoft is just on a roll when it comes to open source. - Windows Terminal is pretty solid, and fast. Dare I say, nearing rxvt-unicode/kitty speed. There are some remaining terminal corruption with tmux + vim sessions, but soon enough it'll be replacing hyper/conemu for me. - WSL 2 alleviates file system issues that plagued WSL. I recently wiped debian off my Thinkpad because there's no point, I get everything I ne…

Windows can be convenient, but what is the cost of your convenience? - Fewer hardware manufacturers will publish drivers for other OSes. - More computer manufacturers will sell computers with Windows preinstalled (and other preinstalled software that you will likely not want in your computer), making your computer more expensive and slower, and sometimes, less secure (search: eDellRoot). - Fewer game publishers will…

I have a Windows desktop, a MacBook Pro and a bunch of Thinkpads running Debian or OpenBSD. They are all fine and I don't understand why for some people it is such a big deal.

I don't think my tiny stupid computer is that important. What I run on the server is a much tougher decision.

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#54
post #47

Just tried Cascadia Code with Emacs. I think Monofur is still better for me. Larger, easier to read, and even more number of text lines shown on screen.

> Larger...more number of text lines shown on screen

Surely that's down to the font size, which you can change?

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#55
post #4

Microsoft is just on a roll when it comes to open source. - Windows Terminal is pretty solid, and fast. Dare I say, nearing rxvt-unicode/kitty speed. There are some remaining terminal corruption with tmux + vim sessions, but soon enough it'll be replacing hyper/conemu for me. - WSL 2 alleviates file system issues that plagued WSL. I recently wiped debian off my Thinkpad because there's no point, I get everything I ne…

- Windows Terminal is nice but the windows command line is not. I don't like PowerShell, it is too verbose. - WSL 2 is not stable and it is only available for the Windows Insider program. And it does not have X. - Windows 10 drivers sucks. For example, Intel Graphics drivers has a lot of bugs. - ClearType has been improved but Linux and Mac font aliasing is a lot better. - I cannot upgrade my laptop to the last Windo…

> Windows really need a package manager.

I feel like you only have this mindset because that's what you're used to, coming from the 'nix world. I came from the Windows world, and not even once have I wished that there was a package manager for Windows. In fact I think it's safe to say I've hated dealing with pretty much every package manager I've ever touched, with possibly the sole exception being pacman.

> NTFS is getting old and it is very slow if you have a lot of small files.

"Old"? So what? That means it's robust and well-tested with lots of tools designed for it. It's not a Javascript framework. And 2 seconds of benchmarking on FAT32, exFAT, or whatever other file system you want would easily demonstrate that the performance difference has nothing to do with NTFS. NTFS is fantastic; I'd take it over extwhatever any day. It doesn't deal with small files quickly simply because Windows and its performance trade-offs weren't designed around programs dealing with lots of tiny files individually. Yeah it sucks, and I wish it was better just like I wish ext was better in other ways, but it's not really surprising; you're trying to program on Windows with a 'nix mentality, so of course you'll hit an impedance mismatch. It's like going from Windows to Linux and complaining that you need to drop into the terminal all the time (or the reverse direction for that matter). It sucks, but the tool just wasn't designed to be used that way.

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#56
post #4

Microsoft is just on a roll when it comes to open source. - Windows Terminal is pretty solid, and fast. Dare I say, nearing rxvt-unicode/kitty speed. There are some remaining terminal corruption with tmux + vim sessions, but soon enough it'll be replacing hyper/conemu for me. - WSL 2 alleviates file system issues that plagued WSL. I recently wiped debian off my Thinkpad because there's no point, I get everything I ne…

- Windows Terminal is nice but the windows command line is not. I don't like PowerShell, it is too verbose. - WSL 2 is not stable and it is only available for the Windows Insider program. And it does not have X. - Windows 10 drivers sucks. For example, Intel Graphics drivers has a lot of bugs. - ClearType has been improved but Linux and Mac font aliasing is a lot better. - I cannot upgrade my laptop to the last Windo…

Windows drivers being bad is the fault of the hardware manufacturer; at least they provide some drivers!

Ironically windows has had a kind of package manager for years in the form of MSI and the "add/remove programs" system. It just didn't wire this up to a repository.

NTFS performance is becoming a serious problem. That and process spawning are the two things that Linux systems inherently do much faster. The tendency of Windows systems to hook antivirus into everything that the filesystem does is also crippling but still seems to be mandatory.

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#57

Earlier quoted context omitted.

I'm seriously considering moving back to Windows from Arch. I miss some software. Can you give some downsides of WSL2 so I know you're being impartial (I am) and to help me make a decision. I wasted a few days with WSL1 and don't want to repeat that.

Just minor issues: You need to be on the insider programmer which forces telemetry and means you have a PITA windows style upgrade every other week (and the nagging associated with it). Whilst you can read /mnt/c/ you can't read virtual file systems such as Google drive stream /mnt/g/ is just empty. You need to do a bit of fuckery like pinning your ssh-agent to a known file socket and test this in your bash/zsh start…

> You need to be on the insider programmer which forces telemetry and means you have a PITA windows style upgrade every other week (and the nagging associated with it).

FWIW you can upgrade to the Fast Ring version of Windows that gets you WSL 2 and then switch to the Slow Ring that only gives you updates every month or so.

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#58

Earlier quoted context omitted.

> You'll be surprised how `!=` looks like with this font […] For anyone curious, you can see it here [1] (check the last character) . [1] https://raw.githubusercontent.com/microsoft/cascadia-code/ma...

Not the best decision I think, too much resemblance to the division assignment operator: x /= 10;

[deleted]

Re: Show HN: Cascadia Code, a Font for Windows Terminal and VSCode

#59
post #45
post #44

Earlier quoted context omitted.

WSL2 aren't shipped with systemd (or any other init processes) out of the box. So you, as an Arch user especially, will have much trouble managing Linux daemons. If you are an embedded dev keep in mind that USB or any native devices on WSL2 is not supported. If you are a web dev keep in mind that localhost is not available so that you need to figure out the IP address of WSL2.

> If you are a web dev keep in mind that localhost is not available so that you need to figure out the IP address of WSL2. Which sounds like a non-issue, but is actually quite annoying, as almost every unconfigured daemon binds to localhost...

This is fixed at least in the fast ring
Post reply on HN