Live data from Hacker News

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

github.com

21–30 of 99 posts

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

#21
post #13

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...

It looks different from that, let's have the spoiler: it looks like '=/=', but with the equal signs attached and the forward slash just 'on top' of it.

[deleted]

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

#22
post #3

MS can't really win against its own Consolas. If you haven't tried Consolas, you owe it to yourself to give it a try. Would be cool if MS opensourced that, if they can.

And Consolas with ligatures: https://github.com/somq/consolas-ligaturized

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

#24
post #3

MS can't really win against its own Consolas. If you haven't tried Consolas, you owe it to yourself to give it a try. Would be cool if MS opensourced that, if they can.

I completely agree, the only monospaced font I've used for the last 5+ years. I am however, giving this one a full go.

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

#25
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…

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.

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

#26
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…

As a linux user, the upsides of not facing toxic users who are constantly ranting about M$ beats most other things.

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

#27
post #3

MS can't really win against its own Consolas. If you haven't tried Consolas, you owe it to yourself to give it a try. Would be cool if MS opensourced that, if they can.

And Consolas with ligatures: https://github.com/somq/consolas-ligaturized

No license: can't use.

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

#28
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…

I am rooting for Windows Terminal to succeed, but currently it's definitely not fast. Complete redraws of the content are in fact painfully slow for me at the moment.

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

#29
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…

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 startup - not a biggie since you arent starting this off your WM

No X support - there are third party x viewers though but not officially endorsed. So no apps like xkeynav and xkill.

None of the intellij ecosystem have WSL support - sure you can set the terminal to be use wsl.exe but stuff like using your WSL2 distro's openssh config or using the agent running in your WSL2 etc... arent there or coming, VSCode is lightyears ahead in this department due to the way its modelled. Sadly intellij team aren't thinking in the same way of the vscode team, so instead of proxying through a remote demon they are thinking of doing something like reading //wsl$/distro/home/you/.ssh/config instead, hacking WSL support in their ssh/git bits

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

#30

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…

Need to set max memory in wslconfig too - not so well documented - otherwise your VM will just balloon to fill up all your RAM and windows and windows app will start swapping
Post reply on HN