Tiny Awards for Small Websites • Hacker News Board

Re: Tiny Awards for Small Websites

#81

Post by vintagedave » Mon, Jun 12, 2023, 9:42 AM UTC

nicbou wrote: post #78

2b3a51 wrote: post #63

Earlier quoted context omitted.

Try palemoon perhaps. Seamonkey is an old school fork of Netscape before they pulled out Firefox. I suspect the CSS rendering is marginal CSS 2. I use Seamonky on OpenBSD i386 arch as Firefox no longer supported. I am using deliberately low spec computers for personal surfing. The links render shows the 'skip to main content' link which is always a good sign that accessibility has been addressed.

If you have a few minutes to kill, I'd love to know how allaboutberlin.com feels on such a device. I sometimes choose convenience over coverage, but I still try to make the website accessible.

Not the person you asked, but I just opened it on Firefox on Mac. That website is _blazing fast_. It opened in a fraction of a second. Really good job!

Re: Tiny Awards for Small Websites

#82

Post by ilyt » Mon, Jun 12, 2023, 1:56 PM UTC

Solvency wrote: post #52

ilyt wrote: post #44

Earlier quoted context omitted.

> What happened to "I'll edit this .html file and FTP it up, with maybe a light sprinkling of CSS and js for any interactive elements"? What happened are people being annoyed with hand-fucking html every time they want to write a blogpost started writing/using static site builders

So instead of typing ("hand fucking") a few HTML characters around your blog post you trade it in for a big complex orgy of additional abstractions, tools, and processes.

Yes. HTML is not great and when you have to fuck with CSS to it becomes distracting. Just put the effort once into making template I want then just write markdown.

Re: Tiny Awards for Small Websites

#83

Post by philistine » Mon, Jun 12, 2023, 3:48 PM UTC

baobabKoodaa wrote: post #77

philistine wrote: post #73

Earlier quoted context omitted.

I don’t understand how something like Jekyll could be considered big and complex. What examples do you have in mind?

Well, I run my own blog on Gatsby, and about once per year I have to dedicate a weekend to figure out how to make it run locally again, because the entire JS ecosystem is an unstable hellscape of ever-changing complexity that morphs from one shape to another for absolutely no reason at all.

While I totally understand the node.js idea of building the backend with the same language as the frontend, I don’t understand why anyone should use JS for a static website. The point of a static website is to get away from server troubles, and it seems like building something static on top of JS is just the worst house of cards. I’m happy with my tech choices because I always think about the people behind my choices.

I moved from ConTeXt to XeTeX because the people making context didn’t care about documentation.

I moved to Jekyll because the people behind it were making Github. They built something rock solid.

I moved from Apache to Nginx because the people making it were trying to build something simple to configure. It showed and I could solve my redirect issues in minutes.

Re: Tiny Awards for Small Websites

#84

Post by 2b3a51 » Thu, Jun 15, 2023, 5:56 PM UTC

nicbou wrote: post #78

2b3a51 wrote: post #63

Earlier quoted context omitted.

Try palemoon perhaps. Seamonkey is an old school fork of Netscape before they pulled out Firefox. I suspect the CSS rendering is marginal CSS 2. I use Seamonky on OpenBSD i386 arch as Firefox no longer supported. I am using deliberately low spec computers for personal surfing. The links render shows the 'skip to main content' link which is always a good sign that accessibility has been addressed.

If you have a few minutes to kill, I'd love to know how allaboutberlin.com feels on such a device. I sometimes choose convenience over coverage, but I still try to make the website accessible.

Thinkpad T42, 1Gb ram, slackware 14.2, seamonkey 2.53 with noscript legacy plugin operating.

Loads fast, looks clean, content seems to be available - each of the 'cards' opens a page with a graphic, a table of contents in a contrasting grey colour and then text giving information. There is then a 'classified ads' section with links at the bottom.

Looks identical on my 'normal' machine with Firefox 102-esr and ublock origin and more ram/faster processor &c.

A quick look in the text mode browser links in a uxterm window showed that text content was available. The home window links show as two rows of text links - works ok.

I'm on a pretty fast G4 'mobile broadband' connection in UK with around 2.5Mb/sec (probably the old Thinkpads wifi limit) and around 45 mSec latency from ping.

Just one observation:

https://allaboutberlin.com/ works fine

https://www.allaboutberlin.com/ gives a page not found.

This reply is not very timely - I'm not logged in on HN that often!