I'll second that, this is extremely annoying and exhausting.
It feels like the slightest occurrence of a less-than-ubiquitous pattern or any word not regularly used by the majority of the population instantly spawns a sleuth of newfound linguists who'll pitch in to explain how this certain marker ought to be proof of AI origin.
This does nothing for the conservation, except helping the claim that AI will erode and dumb down our language become a self-fulfilling prophecy when people start feeling pressured to use the most dumbed down, simplistic and rhetorically bland way of expressing themselves to avoid any "suspicion"
We've been running our services on Hetzner for 10 years, never experienced any significant outages.
That might be datacenter dependant of course, since our root servers and cloud services are all hosted in Europe, but I really never understood why Hetzner is said to be less reliable
this is the way. Modern CSS brings most of the capabilities to the table that SASS & LESS used to provide, and in part even much more functionality that could never be adequately solved with preprocessors (runtime calc(), light-dark() and layers come to mind)
I'm still a fan of LESS, but quite specifically because it _does not_ try to force another languages syntax into my preprocessed stylesheets, rather keeps everything as css-like as possible. This makes it much easier to transition things to vanilla-only when possible, absolutely dreading "mostly js"-types of SASS frameworks
Being from Germany our history classes in school went into great depth about the countries past - and I can't help but feel increasingly scared and left utterly speechless by all the parallels I'm seeing unfolding in the US ...
when technological advancements that actually would allow for BETTER privacy and security, and MORE local-only features are misappropriated for constructing bogus and dishonest justifications to rather erode the least-effort user-minded safeguards that already had been present, it's become plain obvious that the claim to create a product that serves the user has always been a lie. It's about capturing data and influence, and always has been
supposedly idealistically opposed parties doing something that is in the sense of the argument doesn't prove the argument. Walz might very well have been just as wrong
almost everything you have in your home is built for humans, so adopting this form factor is the likeliest to fit everywhere and be able to operate everything
Honestly with those numbers, I'm pretty surprised it's even an independent company. Wouldn't such a community of 3-4k people in a very remote location be a prime example where providing internet could just be a gov/municipal service, subsided by an extraordinary tax if needed?
nitpick on your nitpick on the nitpick: a "metacommentary" would be if you'd be commenting on your own text. That's even less important, but I thought you might appreciate such asides
This makes me anxious about net neutrality. Easy to see a future were those bots even get prioritised by your host's ISP, and human users get increasingly pushed to use conversational bots and search engines as the core interface to any web content
I'm quite surprised by the impression in the first place, since "dancing events" as a way to meet others and connect seems more ubiquitous than ever to me.
It may not look much like typical social dances performed with a partner, but I'm definitely thinking of clubbings, raves and festivals as happenings were "dancing connects people" - and it's one of the primary ways almost anyone I know has been socializing, at least throughout their 20s and 30s.
I didn't feel that way, since she specifically points it out and also explains (quite correctly) why this matter is to be treated differently for a newspaper than for any other business
Hits the nail on the head. I was surprised they even removed the ability to customize the taskbar location - but it still employs the same registry entries, so you can relocate it by messing with obscure manual modifications.
Yet half the menus will just ignore it. The start menu will pop up at the correct location, but then glitch to bottom left as soon as you start typing/searching
What's beyond is that even if we were to accept all the dumbing down and reduction of the UI as a sacrifice to make the OS more touch/hybrid friendly - it'd be really bad design, since keeping the taskbar on top makes it quite ergonomic to access on touch ultrabooks.
I'm picking this specific example, since it really questions the "trust us it's how it's best" excuse, and makes it much rather feel like 11 was simply rushed into production
This is one of my main topics when integrating design systems for UI concerns, and imho this site does well at demonstrating a central problem and misunderstanding:
The author talking about "4 colors", when really he means 4 "color roles" or "theming swatches".
First of all, 4 don't cut it.
You'll need accents for all of them, to fade sidenotes, visual hierarchy and disabled elements; to differentiate states of interactive; for borders, separators, and other parts of the chrome, and visual distinction of illustrative elements like icons; to give just a few samples ..
But the shortcomings of building a design system on 3 swatches for "text, bg, button" will become obvious much sooner, since defining which of the text/bg colors works for the button text depends on the button color itself, etc.
What most frameworks, complex and simplistic alike, get wrong imho, is that you need TWO "layers" of color definition, not to cram your palette definition into semantic concerns of the ui to be decorated. Those are separate concerns!
Or better said: the purpose of design tokens is not to be an abstraction for css properties of distinctive components.
- One Layer is your brand definition, or the color palettes that will serve to define the GUIs design. These are your design tokens
- The other layer is a semantic abstraction of the requirements in the design context. These are your "text, bg, button text, button bg, ..."
The library of design tokens need to acommodate ANY context the brand design could be applied to, and thus provide a wide range of shades for whatever amount of base colors want to use in the brand design.
These will then be mapped to the second layer of "roles", and populate whatever distinct use cases in the design.
TLDR: there is no "text, bg, highlight" color. There are "primary, secondary, accent, neutral, ..." color palettes, and "copy text, copy bg, button text, button icon, button bg, hovered button, .." swatches to be populated with them.
there could be better ways to ease the burdon of naming things, while preserving cascade and the actual full features of CSS
Tailwind is a mirage, a shortcut to not having to do the important stuff by stacking wrappers on top of wrappers and redundancy
And the "fragile" part is exactly the same thing with tailwind, it all remains low specificity class names