Earlier quoted context omitted.
This is better than 50% of websites out there today. I can find all the buttons, the functions of things are clear, and I know how to contact the owner. The menu is text instead of PDF, and the whole thing appears to run properly without javascript enabled.
The brilliance goes beyond the web design. From that menu: "DINO would like you to know that more than three toppings will be expensive and won't be any better."
Convincing-looking 90s fonts in modern browsers
151–160 of 177 posts
Re: Convincing-looking 90s fonts in modern browsers
#152WWW should never have enabled use of custom fonts or colours. The fonts and the colours used for particular elements of a page should be configured system-wide. I always block web fonts anyway.
If that's how you like it, you can configure your user-agent as such and get that experience today.
Re: Convincing-looking 90s fonts in modern browsers
#153Earlier quoted context omitted.
topgun.mid actually exists.
And now I have a new ringtone. Finally, I can wear my love for top gun on my sleeve and—for the first time in a decade—take my phone off vibrate. Edit: why is this so hard to do on an iPhone? Guess I shouldn’t be surprised.
using many apps with sound enabled is shocking after long periods of app silence. Social media apps sound like slot machines! So much pavlovian conditioning... Not sure how all that is still legal.
Re: Convincing-looking 90s fonts in modern browsers
#154This font looked perfect on Firefox on Android, but when I read it on my desktop (Firefox on Linux) it looks wrong. It seems as though the scale is wrong, and the character 'o' gets a white line though it.
Re: Convincing-looking 90s fonts in modern browsers
#155I need to send this to the people who designed the website for one of my favorite local pizza places, Dino's ( https://www.dinostomatopie.com/ ) -- they did _really_ well, generally, but no matter how hard you try, some things come through: the fonts rendered as text are perfectly crisp at whatever absurd DPI this Chromebook has.
This place is great. A few commenters seem to think this is a joke or not a real pizza place. I assure you all, it is!
http://www.seattlemag.com/article/three-impressions-dino-s-t...
Re: Convincing-looking 90s fonts in modern browsers
#156I need to send this to the people who designed the website for one of my favorite local pizza places, Dino's ( https://www.dinostomatopie.com/ ) -- they did _really_ well, generally, but no matter how hard you try, some things come through: the fonts rendered as text are perfectly crisp at whatever absurd DPI this Chromebook has.
>the fonts rendered as text are perfectly crisp Didn't you read the note at the bottom? "This site is best viewed with Netscape. Download v4.7.2 by clicking here." Clearly, you didn't follow the instructions for best viewing experience!
Ah, that's where it all went wrong, moving beyond Netscape 4!
Re: Convincing-looking 90s fonts in modern browsers
#157Earlier quoted context omitted.
> ten times the resources for doing the same thing Is it really ten times the resources, and really doing the same thing? My computer today uses much less power than what I had in the '90s, and cost less too. It has an internal 4K display and two external 4K displays. My '90s computer had a single 1280x1024 CRT where I always had to tweak the focus and alignment to get readable text. With no GPU, scrolling in an edit…
Watching text repaint line by line is a feature of 9600 baud serial terminals, not of 90s PC GUIs.
He must be a kid faking it, he looks ridiculous. W98 on a Pentium II was so low level that scrolling was several times faster than any composite based OS from today, even faster under NT4.
Re: Convincing-looking 90s fonts in modern browsers
#158I hate antialiasing. I absolutely cannot stand blurry fonts. First thing I do on a Linux box is install the ambiguously licensed "mscorefonts" and disable antialiasing everywhere possible. That is explained in the font-howto that may be a bit outdated now. Verdana for the interface, Times New Roman, Courier New for monospace ... aaaaahhhhh!
The first thing that comes to my mind is: Are you joking? But I wonder to myself: what does he call blurry fonts. Anti-aliased fonts, of course. But I've never seen them as blurry and I guess most other people don't, otherwise we'd not like them better. Don't you think there could be a sight specificity? Do you have extremely sharp eyesight?
There is certainly a taste specificity, but no sight specificity. I must admit none of the laptops at home are very new, and at work I still use the 2 monitors I received when I arrived 8 years ago.
I like my fonts sharp (and pixelated if required) and I truly think e.g. Verdana 8 and 10 are a marvel of legibility, without antialiasing but with hinting, as explained below or in the font-howto.
There is one of my daughter's laptop, Windows 10, where I never succeeded in having the fonts right, whichever Cleartype setting or without Cleartype. This is so disappointing when tech that used to work so good gets broken.
Re: Convincing-looking 90s fonts in modern browsers
#159I hate antialiasing. I absolutely cannot stand blurry fonts. First thing I do on a Linux box is install the ambiguously licensed "mscorefonts" and disable antialiasing everywhere possible. That is explained in the font-howto that may be a bit outdated now. Verdana for the interface, Times New Roman, Courier New for monospace ... aaaaahhhhh!
I'm the opposite. First thing I do on a Linux box if I don't have a HiDPI screen is that I'll turn off hinting everywhere. Without hinting antialiasing truly shines.
Re: Convincing-looking 90s fonts in modern browsers
#160Regarding the complaints on both kerning and blurriness that you're getting in the thread: the original font likely included a ton of kerning and hinting info, but it might've been all stripped when going through the conversion process. Seeing as character metrics should be practically identical to the original, you might want to copy that info into your result font—if that's possible (I think it should be, but dunno about tool support).
However, there will probably still be a problem if the intended font height doesn't match the actual one in the user's browser—and you can't control that with accuracy to a pixel (CSS pixels aren't screen pixels).