Live data from Hacker News

Show HN: I made a modern web UI for Wikipedia

modernwiki.app

421–426 of 426 posts

Re: Show HN: I made a modern web UI for Wikipedia

#421

Earlier quoted context omitted.

for me, that's way worse, I much prefer to get full width, on my 32 inch monitor, it looks nicer on the default website, and fits way more stuff without needing to scroll. If I want a similar layout for "reading" I'll just use reader mode in the browser and get a very similar layout.

To each their own I guess, but to me you just described a terrible reading experience. Filling all available space with content may sound like a good idea on paper but columns of text should really limited in their width - that's just very basic and commonly agreed upon typography best practice.

except, that applies if you are reading something top to bottom, like a book. That's not what I do on wikipedia, I scan for information.... and it is much easier to do that in wide format. What you end up actually reading is a paragraph or two. As a speed reader, I read in chunks, and in wide format it's actually not that bad, its not a wall of text. Most paragraphs end up to be 3-4 lines long and are naturally chunked by citation notes. I find it really easy. There is no one rule of typography, there is general guidance, but context matters. If in your head you've translated that to a "rule", you are doing it wrong.

Re: Show HN: I made a modern web UI for Wikipedia

#422

Earlier quoted context omitted.

en.m. is NOT a seperate resource from en.. It is the SAME resource because it has the SAME content and because editing the content on EITHER changes the content on the other. It is a different PRESENTATION of the content, which should be served at the same URL. This is WHY HTTP has such headers as Vary and Accept. If en.m. is asking for the mobile version, then en. is asking for the desktop version, yes? So why does…

That's not true. There are functional differences between the en.m and the en. versions.

Okay, and? Again, they both display the same content, and edits made to either one affect the other. I don't know why you think it's relevant that there are (supposedly) "functional differences", sockpuppet.

Re: Show HN: I made a modern web UI for Wikipedia

#423
post #76

Earlier quoted context omitted.

This isn't so bad but consider new Reddit vs. old Reddit. If "new" were to become the only way to access Reddit, I would probably abandon it.

They don't need to force you to migrate, the new site pushes people into mindless meme sharing only, and completely altered the contents of the site already.

On desktop you can choose to remain on the old format.

On mobile you seem to need to do old.reddit.com every time.

Never installed the app on mobile.

Re: Show HN: I made a modern web UI for Wikipedia

#424

Earlier quoted context omitted.

I love my mobile app as well (RIF), but do you know about old.reddit.com? Still works great with RES, I couldn't imagine Reddit on the desktop any other way

Yup still do that on desktop, I have it automatically redirect me, I would hate to lose it!

Sometimes links to other subs go to the new site, sometimes stays on old, I suppose depending on how the links are set up.

Re: Show HN: I made a modern web UI for Wikipedia

#425

Earlier quoted context omitted.

That's not true. There are functional differences between the en.m and the en. versions.

Okay, and? Again, they both display the same content, and edits made to either one affect the other. I don't know why you think it's relevant that there are (supposedly) "functional differences", sockpuppet.

Sockpuppet? And who exactly would I be sockpuppeting for? Big Wiki?

It's relevant that there are functional differences because those are not presentational differences. HTML is for content, CSS is for presentation. If the HTML is different, then it's a different resource and, therefore, gets a different resource locator (URL).

Re: Show HN: I made a modern web UI for Wikipedia

#426

I am one of those people who actually like Wikipedia the way it is. It's what I hoped the web to become. But i am sure there are people who will appreciate your effort. Thank you for your work.

"Modern web" isn't bad because of it's design, it's awful because of the dark patterns and 5s+ load times.

You don't need 20MB React bundles to make a good-looking website, and OP proves that perfectly

Post reply on HN