Live data from Hacker News

98.css – design system for building faithful recreations of Windows 98 UIs

jdan.github.io

141–150 of 216 posts

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#142

Earlier quoted context omitted.

Me asking myself "how long is this article" before I start reading it is a distraction? Too bad, I can't help but want to know. I could've learned that instantly by unconsciously glancing at the scroll indicator, but instead I have to move the whole content down for it to appear (possibly with a whizz-bang animation, no less), introducing friction and further distracting me from the content. Good job, I guess.

I don't know what you tell you - most people don't think about user interfaces like this. As we can clearly tell by people not designing them like this anymore.

If I were to find a causal relation, it would be the opposite: people not expecting affordances such as scroll indicators would be a result of designers hiding them in the first place.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#143

Earlier quoted context omitted.

Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.

You just scroll a tiny bit and you can see. Doesn't need to on the screen all the time, taking up space, distracting from the content which is what I care about, rather than whizz-bang user-interface elements.

There are margins on the screen 95% of the time, it's a perfect place for a tiny 1-3px scroll indicator.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#144

Earlier quoted context omitted.

Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.

> You may as well argue against page numbers in books. Actually, yes, when was the last time you looked at a page number in an e-book? They don't make sense anyway when you can resize the reader.

Actually, they very much do:

1. As a relative marker of a current position.

2. As an absolute number when your ebook/reader screws up saving its state.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#145

Earlier quoted context omitted.

An always visible scroll bar or indicator is conceptually simpler than one that disappears randomly. Knowing that a view is scrollable and there's more content to see is absolutely not an obscure edge case but a basic accessibility feature. Relevant past discussion: https://news.ycombinator.com/item?id=20951580 Also relevant, what happens when the user doesn't realize more content is available: https://news.ycombinat…

Well I just subjectively disagree - as apparently do the legions of professional experts at multiple distinct companies who research user interaction and design these interfaces.

The "professional experts" are not interested in usability. They care only about sales and/or engagement. You can see this in every consumer product, not just software.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#146

Really nice. I tried to get Windows look and feel in the headers for the Yazz code editor, but maybe I should have used this CSS lib instead. Great Job! https://yazz.com/app/homepage.html

> https://news.ycombinator.com/item?id=21734845

This (yazz/pilot [i]) needs more exposure... the webapp form designer is gorgeous and useful.

[i] https://yazz.com/app/homepage.html

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#147
post #105

It may as well be called 2000.css, at least I won't be able to tell the difference.

Windows 2000 used Tahoma for its UI font, but 9x used MS Sans Serif.

https://en.wikipedia.org/wiki/MS_Sans_Serif

https://en.wikipedia.org/wiki/Tahoma_(typeface)

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#148

Really nice! One minor nitpick: the title bar buttons actually need to be a pixel or two larger in each direction (so 2 or 4 pixels more of height and width, while remaining centered).

Also, the font needs to be MS Sans Serif, not Arial.

https://en.wikipedia.org/wiki/MS_Sans_Serif

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#149

Earlier quoted context omitted.

You're in luck: https://codepen.io/matthijss/pen/wzYjJQ

Haha. I was just thinking of that. Been wondering if there's any operating system I can theme to look like Win3.1 any more - the aesthetic of Windows 95 is better but Windows 3.1 seems to fit our contemporary standards of flat and fewer colors better. I did like the more rounded buttons of Windows 3.1 better than the harsher edges of the Windows 95 buttons. The mistakes a driving me crazy. I assume the fonts are just…

They've been irking me too, along with the ones in the original article. They need to be blockier and more precise. Not bad starts, though.

Re: 98.css – design system for building faithful recreations of Windows 98 UIs

#150

Earlier quoted context omitted.

Knowing how long a document is, and whereabouts your current view is, seems pretty fundamental. You may as well argue against page numbers in books.

> You may as well argue against page numbers in books. Actually, yes, when was the last time you looked at a page number in an e-book? They don't make sense anyway when you can resize the reader.

>Actually, yes, when was the last time you looked at a page number in an e-book? Every time I read an ebook, I look at the page numbers. I would be frustrated without knowing where I am or how much longer I have to go
Post reply on HN