Looks like a lot of people are mentioning this one, so buyer beware that it's in the kickstarter stages & it's not currently possible to buy outside of kickstarter
Yes but they actually ship hardware right now (laptops), just raised a round of funding, and post regular updates on tangible progress. A safer bet than most, I'd say.
That might be, but by the late 90s my first few stabs at Linux were using Red Hat because it was far enough along that books were published and available at my local book store (I did also try Yellow Dog, a Red Hat variant, when repurposing an old PowerPC). By the early 2000s I saw box sets in Best Buy. In my industry, most of the large companies moved from IRIX to Red Hat and have been using them since. Most of the others moved to a different free distro, then to CentOS.
Sure, and it seems like he's happy to take credit for that era, but most of Red Hats value came from the time after Young left, and I don't really think it's modesty for him to not take credit for that
I love windows, but multi-desktop is nicer on mac because it's all controlled with touchpad gestures. The way we (or I at least) interact with windows and apps makes sense that we can just see all apps as thumbnails and then drag them to any desktop we like
This. Also on Windows, all monitors switch desktops together whereas I really like being able to switch desktops on monitors independently, and I like being able to drag desktops between monitor which I seem to remember not working on Windows. And on Windows I can't drag to rearrange desktops. I don't know if rearranging desktops is possible at all.
There seems to be a misconception that you need to go all-in on utilities when using a framework like Tailwind.
If you have 500 buttons using the exact same set of classes, you should of had a button class in the first place. Almost all my projects have their own button and form input classes for this exact reason!
Where utility-based CSS frameworks really start to shine is the other 75% of your codebase, where you're inventing clever class names, only to end up using them once.
This is also why Tailwind calls itself a utility-FIRST framework. Build things with utilities, and extract components to classes when the need arises. Avoiding early abstractions provides a lot of value (in any programming language for that matter). Not having to invent a name for every single piece of UI also saves a ton of headaches down the road.
In my experience design revamps of this magnitude has always needed fresh markup, CSS, Javascript - aka an entirely new front-end. But in case it is just the color of all buttons, then you'd change them in the components. 700 components is quite a stretch - for example there are at most 50 components in Morning Star's design system - http://designsystem.morningstar.com/.
But let's say there are 700 components, what's the alternative if we were using BEM? You'd have to change all the 700 CSS classes, breaking things everywhere thanks to cascades, inheritance, multiple selectors, and specificity. With Functional CSS, all you have to do is go to the markup, and change "bg-white" to "bg-offgrey", and nothing breaks.
In my (limited) experience when I'm repeating the same set of classes over and over again I extract to a named component; You shouldn't have 700 identical buttons that all specify the classes that compose their look. 5-7 times = a use pattern and time to extract it.
In tailwind, you have a config file. You can just change the variable in the config file to the colour you need to change it to and it changes globally.
That’s incorrect. What your missing is that in the config file you define a new color; say ‘rose’ and then the framework auto provides bg-rose, text-rose, border-rose, cutting duplication and bringing consistency.
I think the big shift started to happen when people started to say, let’s treat CSS like code and what would we expect of good code, and then all of these CSS Sacred Cows were then seen in a new light. The biggest of them all for me was ‘naming things are hard’, traditional CSS implies naming your classes is easy, and for a once off example it is always easy, but that approach is a lifetime commmitmnet to generating names on names just to add styles and this adds a naming things complexity burden that until recently has just been a generally unacknowleged invisible cost.
I'm fairly sure this is the primary reason, just like a11y is shorthand for accessibility and i18n is short for internationalization. It also helps that F8 looks like "FB" and sounds like "fate" but those were likely just bonuses.
