eajakobsen

From the FAQ:

> How are stories ranked?

> The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way.

> Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action.

So if a story gets points very quickly, it will appear on the front page. If it don't keep getting points it will disappear.

There is some fine print at the bottom of the screen in the shot where the phone is connected to the handlebars:

> Always use a dampener with your iPhone when riding as shown. Use only with low-powered bikes and avoid prolonged use.

To be fair this video was recorded before the tunnel officially opened.

If you want it to be even more readable you could do the following:

    font-size: clamp(1em, 1.3vw, 1.3em);

I would also consider using `rem` instead of `em` incase you want to use it anywhere other than the root element.

I really like CSS, and in my personal projects I don't use Tailwind.

However, I use it in my day job, and here it is useful to us as a team. The variables combined with the tooling ensures we write consistent styles across our site. The color names and text sizes also correspond to what our design team uses in Figma, making implementing and updating designs quick.

That said, I still find it a pain to read, and we could probably have set up something very similar with CSS Custom Properties.

Ah, I missed that :)

Looks great and works great! A reset button would be nice to undo the horrible mess I made.

A minor note, when I load the page I get console warnings about an Audio Context being prevented from starting automatically, but once I click play everything works perfectly fine.

I think the point in the comment you are replying to is that they _prefer_ having markup and styles in separate files.

One can provide feedback and encourage people to learn about more efficient coding practices without ridicule and comments like "my eyes are bleeding".

To be fair, browser already provide a bunch of accessibility. Unfortunately, the tech we use to build websites also provide a whole host of footguns that are too easy to trigger when building UIs of any meaningful complexity.

Absolutely worth it. Has helped me a lot, finding small issues like buttons with no meaningful label or custom checkboxes that don't announce their state.

I don't know what platform you're on, but I use VoiceOver on Mac. My blind relative uses JAWS on Windows.