113 karma · joined May 20, 2011
Using hand-tuned CSS will undoubtedly be the most performant option, but it leaves you with very difficult problems at the boundary of your styling and content/structure concerns. If you have even a sliver of dynamic content in your website, it will quickly become near-impossible to verify that your content and styles work together as expected, or even to verify that your class names match between your CSS and HTML.
On the other hand, if you use CSS-in-JS, what you lose in performance you gain in compatibility guarantees between your concerns, regardless of how you prefer to separate. Are you putting your styles in the same files as your layout components to fully separate one feature from another? Great, you can unit test those components and be reassured that the elements are styled as expected. Are you isolating your styles to only a certain subset of components that deal directly with styling concerns? Also great—if you're using TypeScript, you can guarantee correct use of those styles at build time.
For a large enough team, those guarantees really pay off. If you have lots of customers using 2G/3G networks and want to hand-roll your CSS, I commend you! For most products, I think there's a better way to make that tradeoff and your users won't mind a slightly slower experience that has fewer bugs.
[1] https://www.studioscratches.com/secrets-of-the-crab-scratch/
If you’re interested specifically in organizations that make breakfast, there are organizations like People’s Breakfast Oakland, which does great work. Not sure if they do omelettes though. [2]
For example, at almost any university in the US, European music theory will be taught in the mainline music curriculum classes, whereas musical systems of indigenous Americans will be taught in specialized classes or sidelined to an “ethnomusicology” curriculum, if it is taught at all. It’s hard to separate this from the history of how America was colonized.
This is a pattern that repeats itself throughout the world, helped both by “traditional” colonization as well as the economic colonization via the dominance of European and American products and cultural artifacts, including music and music software.
So, I don’t think it’s a stretch to say that the overwhelming conformity of music software to European musical patterns is a direct result of the age of European colonization that continues to have an impact both on music education as well as the software industry.
BEFORE STARTING
Connect fuse at starter motor. Turn on gas under dash. Retard spark, which is the lever up position. Open up gas mixture at choke lever a turn. Turn over the car while pulling out the choke in short bursts, usually the car starts on the first choke pull.
WHEN THE CAR STARTS
Advance spark which is the lever down position. Gradually close the fuel mixture down to a 1/4 to 1/2 turn out (in the 9-12 on the clock range).
WHILE DRIVING
Retard the spark at stop signs and the care while idle more smoothly. Open the fuel mixture up to 6 o'clock if the car lags on hills.
PARKING THE CAR FOR THE NIGHT
Turn off gas under dash. Disconnect fuse at starter motor. put up top to keep dust and water out.
GENERAL THIINGS TO CHECK
Water level, if you can see water everything is fine. The radiator temperature gauge works by the way Tires, 30-35 psi is about right. Oil, not apt to be a problem.
THINGS TO REMEMBER
THIS IS A 6 VOLT POSITIVE GROUND CAR, WHICH MAKES JUMP STARTING ALMOST OUT OF THE QUESTION.
WHEN CHARGING THE BATTERY, THE BLACK CLIP GOES ON THE STARTER MOTOR POLE, RED ON THE FRAME.
It feels very fast—has anyone worked with this who can speak to its effectiveness in a production environment?
For once though, the problems I'm experiencing aren't my fault. Nice!
It seems that this is yet another consequence of the bizarre split responsibilities universities hold—balancing the long-term goals of a large institution with the needs of its students, for whom the experience is much more ephemeral.