Live data from Hacker News

The Oldschool PC Font Pack v2.0

int10h.org

61–70 of 73 posts

Re: The Oldschool PC Font Pack v2.0

#61
post #47

Earlier quoted context omitted.

> X is deprecated technology That is false, X and Xorg are being under continuous development. Some Wayland fanboys use this as weaselwords to convince less informed people to migrate to it in an attempt to increase its user share, but Xorg still has dedicated developers working on it and it wont go anywhere for the foreseeable future.

Please don't do flamebait or name-calling here. It degrades discussion and evokes worse from others. https://news.ycombinator.com/newsguidelines.html

So what should i call what bitwize does in a comment below where he essentially writes that not being into Wayland is like not being into social distancing and wearing a mask?

Re: The Oldschool PC Font Pack v2.0

#62

Earlier quoted context omitted.

> X is deprecated technology That is false, X and Xorg are being under continuous development. Some Wayland fanboys use this as weaselwords to convince less informed people to migrate to it in an attempt to increase its user share, but Xorg still has dedicated developers working on it and it wont go anywhere for the foreseeable future.

> Some Wayland fanboys use this as weaselwords to convince less informed people… This is some first-class flamebait in really poor taste. Anyway—from what I understand, Xorg is is nearing the end of its life as an actively developed project. You can see that the release cadence is much slower than it was a couple years ago, it’s gone from something like a six-month cadence to a two-year cadence. The lion’s share of t…

> Xorg is is nearing the end of its life as an actively developed project.

There are people like Keith Packard who work on it exclusively. Xorg is open source, open source software - especially when it has actual users with technical knowledge - doesn't die because some company wishes so.

> You can see that the release cadence is much slower than it was a couple years ago, it’s gone from something like a six-month cadence to a two-year cadence.

Xorg isn't really a single thing as it was in the past but a collection of libraries - some of these libraries are at a very stable point where they do not need updates, others are shared by some Wayland projects so they should be up to date and others... if they need any update i'm sure someone will do it.

> The lion’s share of the development is sponsored by orgs like Red Had and they’ve publicly warned people that this may not continue into the future.

There is no "they", only Red Had wrote a blog post some time ago that they wont do much new development in Xorg but Red Had doesn't own Xorg nor they control its development.

> You simply can’t use X font rendering to achieve what is, in 2020, considered to be the bare minimum for text presentation.

The bare minimum for text presentation is to render text. You can do that perfectly fine with the core X font API - many people (including me) use xterm and similar minimal software just fine. What you cannot do is render antialiased font using that API (though IMO this is an oversight).

However you can use Xft to do that and as of a couple of months ago you can use it to render colored fonts like emoji, which basically covers most of font rendering use for 99% of applications out there (Xft doesn't handle complex text layout, which is where Pango enters the picture, but most GUI software doesn't use that anyway).

> Up until recently, this was papered over by libraries that could abstract over the differences between old-style X fonts and modern TTF fonts (TTF is almost as old as X!) For various reasons, the backwards compatibility was ditched a few months ago. The abstraction had just grown too unwieldy and had too many special cases.

Pango isn't the library for font rendering (even if it is popular) for X11, it is just one of several choices. Pango removing support for bitmap fonts is only a drawback for those who use the library but it doesn't affect anything else.

Re: The Oldschool PC Font Pack v2.0

#63

Earlier quoted context omitted.

>not constantly changing equals it's end-of-life No, it just means that its stable. I understand that it's probably habit to justify constant changes to your software projects, but in my experience, it's a good thing to be conservative, and a very good thing to maintain compatibility over a very long span of time. EDIT: I swear, what is it with people opportunistically virtue-signalling on HN comments? Masks? Really?

Compatibility comes at a cost—by supporting old users, sometimes you fail to support new users. This is not hypothetical, this is at the core of the problem with BDF fonts.

How does supporting BDF fonts makes a project fail to support new users? It sounds like a problem with the library's architecture, not an unsolvable technical hurdle.

Re: The Oldschool PC Font Pack v2.0

#64
I'm using it for my latest bootsta/386¹. It's really the best version of these fonts out there. It's exceptionally accurate. I've gotten accuracy that just simply wasn't possible for the last 2 versions of bootstra. The fonts are really quite something

[1] you've probably already seen it, it's this one https://github.com/kristopolous/BOOTSTRA.386

Re: The Oldschool PC Font Pack v2.0

#65

Earlier quoted context omitted.

>not constantly changing equals it's end-of-life No, it just means that its stable. I understand that it's probably habit to justify constant changes to your software projects, but in my experience, it's a good thing to be conservative, and a very good thing to maintain compatibility over a very long span of time. EDIT: I swear, what is it with people opportunistically virtue-signalling on HN comments? Masks? Really?

Compatibility comes at a cost—by supporting old users, sometimes you fail to support new users. This is not hypothetical, this is at the core of the problem with BDF fonts.

Nothing prevents an X-server from running within Wayland. BDF will live forever for those who need it.

Re: The Oldschool PC Font Pack v2.0

#66

For linux users, you can open the .FON files with fontforge, then go to file menu -> generate to create a .bdf file (I prefer to use bitmap over ttf to avoid any artifacts).

You can just convert it on the command line with FF as well.

I didn't even know FF Even Had a GUI until I read your comment

Re: The Oldschool PC Font Pack v2.0

#67
Did anybody else get a strong emotional reaction to these? I connect them to my BBS years. Reminded me of chat sessions on Terminate, ZMODEM downloads that take just too long to finish (only to discover at least one corrupt zip file part after all that wait!). Mild PTSD memories of my mom chasing me with a telephone bill... :-)

Re: The Oldschool PC Font Pack v2.0

#69
post #68

I wish somebody made a bitmap font based on VGA 8x16, but scaled up to look nice on 4K screens. I'd seriously pay for that.

You could make your own, using pixel art scaling algorithms. (It's also very easy to scale binary images programmatically in something like GIMP by converting to true color, using low-artifacts Lanczos scaling and then going back to b/w binary. That gives you a very similar rendition to pixel art scaling, with no pixelation or blur but a smooth, painting-like effect.)

Re: The Oldschool PC Font Pack v2.0

#70
post #68

I wish somebody made a bitmap font based on VGA 8x16, but scaled up to look nice on 4K screens. I'd seriously pay for that.

https://int10h.org/blog/2018/05/flexi-ibm-vga-scalable-truet... ? :) (Edit: not a bitmap font, but to make it scalable to arbitrary sizes it pretty much has to be an outlined .ttf).
Post reply on HN