zack

zack, 1 month ago

@Edent Per MDN:

> To determine which list to use, try changing the order of the list items; if the meaning changes, use the <ol> element — otherwise you can use <ul>

So I'd go with <ol>

zack, 1 month ago

@matt @katzenberger @rysiek @MarkAssPandi

I don't expect them to be ad-free, I expect them to not use a shitty ad broker that tries to track everything I do. Ads can go directly in the HTML. Demographic ads like this are generally more relevant (despite the bullshit about all the tracking being for better targeting), don't require privacy invasions, aren't readily blockable, and the site can screen overly flashy ads. We don't have to put up with their shitty business practices.

zack, 2 months ago

@baldur With browsers, we prefer multiple implementations to keep the standards open. Isn't the same true for server runtimes?

Deno was one of the main drivers behind a new working group to update existing web specs to better support server runtimes.

I agree about JSR being weird and seeming unnecessary, though.

zack, 2 months ago

@ondra

I don't wanna start an argument in a comment thread, so I'll just offer one point. Feel free to hit me up directly if you want to chat about it more.

> opt-out service that unfortunately copies your data someplace else (beyond your control).

This is the crux of the issue. Ppl in favor of the bridge have the opinion that your description is how federation works within the fediverse, so a bridge isn't any different.

@torgo

zack, 3 months ago

@baldur
> Update to a living spec? But then you lose that stability and predictability.

What do you mean by that? "don't break the web" is one of the web's guiding principles. A lot of reference material that would have been printed in books decades ago is available on the web. What stability and predictability do they lose by using HTML/CSS?

zack, 3 months ago

@baldur But if the browser implementations are backwards compatible, wouldn't any document written for a previous version load correctly?

Oh, is that what you meant by predictability? It may load, but it could possibly look different?

zack, 6 months ago

@sebastianlaube Same thing for search engines. Browsers use to use an icon in the URL bar when a search engine was available on that website, but no more.

I guess when you get paid by the search engine(s), you don't want ppl to be as aware of alternatives

zack, 7 months ago

@lucas @simevidas

With inline styles, you have to change every element that uses a particular style to update your design. With utility classes, you update the style for the class (in one location) and every element uses the updated style.

This was always the biggest issue with inline styles and utility classes solve that.

zack, 7 months ago

@lucas @simevidas sure. Some are pretty static. I still think utility classes are an improvement over inline styles.

As for colors, most systems I've seen use numbers to indicate the scale. So red-100 thru red-800 should always be some shade of red for obvious semantic reasons but you could change the shades of red with proper care.

I'm not arguing for tailwind. I've never used it. But I have used utility classes, though always in combination with normal semantic classes, where appropriate.