this post was submitted on 09 Nov 2023
297 points (95.1% liked)

Programming

17504 readers
13 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] muhanga 17 points 1 year ago* (last edited 1 year ago) (4 children)

And sadly one more font I will never be able to use due to missing support of non-latin characters.

Sadly some features are nice.

[–] [email protected] 8 points 1 year ago (3 children)

You'd think after that page of "texture healing", alignment, etc. etc., Microsoft would actually make a fully, complete font first and foremost...

[–] muhanga 1 points 1 year ago (2 children)

And release zip contains a _MACOSX folder which is a clear indication of sloppiness and/or rushed release. ... and ligatures don't work out the box in JetBrains product IDEs.

And if only they slapped beta on this there will be not problem what so ever...

[–] [email protected] 1 points 1 year ago

Rushed, that’s just how they roll lol

[–] [email protected] 1 points 1 year ago

The ligatures don't even work in visual studio. It made me look for a different font with ligatures, landed on fira code for now. But hyphenated ligatures just seen outright broken on VS and have been for a good amount of years. Think it's time to change IDEs soon. Might try and get VS Code to act more like it's counterpart at some point.