185 karma · joined January 30, 2023
There's also a remake of Ultima Underworld being made in Godot: https://github.com/hankmorgan/UnderworldGodot
Hoping for these projects to succeed, both U7 and UU sound like incredible games that deserve to be accessible to modern gamers.
Same here. But it often produces broken or bogus links.
With fantasy settings in particular it's crucial to keep the setting consistent, since the book is the only "source of truth" on the matter. This sounds like the way to go. Excited to check it out.
Bicycle is "a band that rolls across the country on bicycles and rocks in towns and cities along the way. ... 'Heavy metal folk rap' is how the New York Times coined the band's sound."
Unfortunately the link to the band's page appears to be gone, and there's nothing on google about them. Rare to find something these days that has almost 0 web presence!
Of course, as with any convention-based, getting everyone to follow the rules might be difficult, although the stylelint-config helps.
It would be helpful to see an example of the ruleset applied to a large-ish solution. There are a lot of rules, so it's kind of hard to imagine what it would look actually look like in the css.
Could you elaborate a little on what you mean by “just-in-time” rulesets and how rule 22 ("Component styling should only be served with live components.") works in practice? Are you referring to web components?
However, one thing I'm still wondering about is how easy it would be to maintain visual consistency in a large project with lots of components, and lots of different developers working on different parts of the app.
Say the branding guidelines a certain style, like rounded corners with some shadowing and a hover styles, something that can't be done with a simple utility class. This should be consistent across many different components and pages. Then, someone in design updates the guidelines to have a different value for rounding and shadows.
With Tailwind out of the box, each component now has to be updated separately, and developers have to remember, or at least be able to check in documentation if that exists, which components use this particular style.
Is the answer then simply to use @apply for combinations of style? Doesn't this simply re-invent CSS classes, and create another layer of abstraction (you now have a class, which is composed of other classes, which themselves are composed of values set in custom properties).
I'd be very interested to hear how people manage this in large teams, over time.