5 ms·

Show HN: Windows 95 web components [MIT License]

19 points by themesberg 6y ago

BrS96bVxXBLzf5B 6y ago
This looks great. But curious: > 100% Valid W3C HTML Files and made for awesome developers just like you. Why does a README try to sell itself by talking down to the reader like they're a five year old?
- themesberg 6y ago
  Thanks. Well, I never thought of it that way. How would you rather change the text?
  - BrS96bVxXBLzf5B 6y ago
    "100% Valid W3C HTML Files". That's all. There are some times when mentioning the motivation is relevant and might be important, but "a developer's tool made for developers just like you, a developer" isn't it.
    - themesberg 6y ago
      Done :)
EgoIncarnate 6y ago
You might want to give it a non-Windows name. Classic95 UI Kit or something. Calling it "Windows 95 UI Kit" implies it's from Windows 95 and will likely attract the attention of Microsoft lawyers who are obligated to swat down any potential trademark confusion in order to protect the Windows trademark. Microsoft might overlook the copyright violation, but legally they cannot ignore the trademark violation or they risk losing the Windows trademark. Anything WinXXX isn't particularly safe. For example, they went after Winternals, who had to change their name to SysInternals (and were eventually acqui-hired by MS). See https://en.wikipedia.org/wiki/Microsoft_litigation#Trademarks https://en.wikipedia.org/wiki/Microsoft_litigation#Trademark... for others.
- themesberg 6y ago
  Any ideas for other names?
  - kthartic 6y ago
    I like the one he suggested - Classic95 UI Kit
me_bx 6y ago
Small issue, but maybe not worth spending too much effort to fix, given the low demographic it may affect: Using firefox 68 ESR on Windows (at work), the text in the demo page looks like it's been strike-through, it is barely readable. Each line of text has two horizontal lines (one pixel high each) filled with transparency... Disabling the "Windows 65" font family solves the problem - but then Segoe UI is used.
- themesberg 6y ago
  Thanks for pointing this out! I'll add it as an issue on the repo.

19 points by themesberg 6y ago

This looks great. But curious: > 100% Valid W3C HTML Files and made for awesome developers just like you. Why does a README try to sell itself by talking down to the reader like they're a five year old?

themesberg 6y ago
Thanks. Well, I never thought of it that way. How would you rather change the text?
- BrS96bVxXBLzf5B 6y ago
  "100% Valid W3C HTML Files". That's all. There are some times when mentioning the motivation is relevant and might be important, but "a developer's tool made for developers just like you, a developer" isn't it.
  - themesberg 6y ago
    Done :)

EgoIncarnate 6y ago

You might want to give it a non-Windows name. Classic95 UI Kit or something. Calling it "Windows 95 UI Kit" implies it's from Windows 95 and will likely attract the attention of Microsoft lawyers who are obligated to swat down any potential trademark confusion in order to protect the Windows trademark. Microsoft might overlook the copyright violation, but legally they cannot ignore the trademark violation or they risk losing the Windows trademark. Anything WinXXX isn't particularly safe. For example, they went after Winternals, who had to change their name to SysInternals (and were eventually acqui-hired by MS). See https://en.wikipedia.org/wiki/Microsoft_litigation#Trademarks https://en.wikipedia.org/wiki/Microsoft_litigation#Trademark... for others.

themesberg 6y ago
Any ideas for other names?
- kthartic 6y ago
  I like the one he suggested - Classic95 UI Kit

me_bx 6y ago

Small issue, but maybe not worth spending too much effort to fix, given the low demographic it may affect: Using firefox 68 ESR on Windows (at work), the text in the demo page looks like it's been strike-through, it is barely readable. Each line of text has two horizontal lines (one pixel high each) filled with transparency... Disabling the "Windows 65" font family solves the problem - but then Segoe UI is used.

themesberg 6y ago
Thanks for pointing this out! I'll add it as an issue on the repo.