body { LLM(
"You are an expert web designer, completely fluent in CSS.
Create styling for this commerce website which is both
eye-catching yet professional looking, while being engaging.
Ensure it conforms to accessibility standards."
) }
Anecdotally I've found it better telling the llm it's in a high growth tech startup on an H1B, any mistake will risk termination and being sent back home where they'll have to become a trash picker.
I actually am really looking forward to a future where we have better tooling for a true "user agent" that knows my preferences and can style every page automatically just ust the way I like it (and letting me override anything by asking it once and having it remember). I'm so tired of UX designers choosing things for me assuming I'm a 5-year old.
It seems far more likely that we'll end up in a state where you won't be able to override CSS at all. You'll be allowed to use only the most modern version of Google Chrome because all the websites will simply require a private auth key that only Chrome possesses, and commands like cURL will no longer function properly. The devtools console will be locked behind a key that you must petition Google to get, and if you use it for anything other than what they want, your permissions will be revoked without further recourse.
I've had similar thoughts but replacing Google with Apple who I could easily seeing doing parts of this. They have the platform stranglehold and abusive history to support the behaviour and current browser "enforcement", with little to nothing in the way of consequences.
- A good designer will be able to produce a page whose looks are appropriately engaging, complementary to the content, unique, and easy on the eyes. For every abrasive CSS (or lack thereof) justfuckingusehtml.com, there's a masterpiece like acko.net, many of which just aren't in the mainstream.
- If everything ends up looking the same wouldn't that get... boring? I get the desire to avoid obnoxious design choices, but those obnoxious design choices are part of the web, and they should be embraced as part of the decision-making process about if and how you want to keep reading a site. A bit of friction is, IMO, a good thing when browsing the web. It's the minimum level of keeping the web an interactive medium rather than just a content pipe.
That said, you do you. You're well within your rights to browse the web how you want, up to and including using automation to re-style sites with extreme prejudice.
Uhhh, that reminds me of the super duper helpful way YouTube automatically enables dubbing and/or subtitles based on the last video I watched, my browser language, my account language, where I am in the world, phase of the moon, the colour of my shirt...
It would get him fired today... but my trig teacher showed up to this lesson shirtless in a floor length native American headdress, and ran into class yelling "I am Chief SohCahToa! Never forget my name!!".
In my school, it was "Some Old Hippie Caught Another Hippie Tripping On Acid," which succeeded in being quite memorable for me. In retrospect it seems a bit wild compared to some of the examples here, especially considering it was taught at a public school in the US deep south!
We made this up in school: "saya tak hensem, kalau saya hensem, tentu Tipah suka" [opposite = tentang, adjacent = sebelah, cos = kos]
Translation: I'm not handsome, if I were handsome, Tipah (our principal) would like me"
25 years ago and I still remember it clearly. Also it was middle school education on how to solve problems in a different space; this one solving math in a second language space lol
For us it was "Some officers have curly auburn hair 'til old age". Never seemed like a good mnemonic given that you have to shorten "until" to make it work and none of us had any idea what "auburn" was, but I still remember it 20 years later so...
For me, UK, posh school, 1980s it was just "sohcahtoa" - easy enough to be its own mnemonic. No need to gild a lily.
Your order is cosine, sine, tangent - CST. A quick look at the other examples here seem to prefer SCT - as do I but only because that is what I was taught.
I also note your mnemonic is very different to the one I learned in having the function name last. So AHC vs CAH.
There is no right or wrong here but I'm sure we can agree that there are loads of mnemonics for these basic trig formulae and nationality isn't involved.
Allegedly your grandpa, armed with his slide rule, has even more random violence:
"Spitfire or Hurricane come and hurry to our aid"
This works for me as the order of the functions matches the order shown on my trusty FX82A. Your version is kind of messed up.
I am giving this AI thing a wide birth, however, could we ask a LLM to invent a new aide memoire for this? We have got the silent generation and the boomers covered, but is there something we can do for kids today? Maybe it references Cinnamoroll, Hello Kitty or Octonauts characters that actual kids know, without it being ultra-violent.
If you know your trig well enough, you can derive the identities.
For example, knowing that cosine and sine are the exact same wave, just 90 degrees out of phase, it's trivial to know that sin(angle) = cos(angle + 90)
cos(a)^2 + sin(a)^2 = 1 is easy to show, too. If you use a=0, it's trivial. But try using 45 degrees. It turns into (sqrt(2)/2)^2 + (sqrt(2)/2)^2 which simplifies to 0.5 + 0.5 = 1.
Many of the others can be derived by just manipulating the Law of Sines or Law of Cosines. Fun fact: The Pythagorean Theorem is actually just a special case of the Law of Cosines:
c^2 = a^2 + b^2 - 2*a*b*cos(C)
Recall that in the Law of Cosines as I've written it, the lowercase letters are the sides, and the large C is the angle opposite that side. So if you choose your hypotenuse to be c, then the opposite angle, C, is 90 degrees. cos(90) is 0, so that whole last term gets cancelled out and you're left with the equation known as the Pythagorean Theorem.
I really wasn't kidding when I said I enjoyed trig.
Knowing that cos(45) == sqrt(2)/2 seems like something you would need to memorize, but if you just draw an isosceles right triangle with sides equal to 1 and use the Pythagorean Theorem you'll find that the hypotenuse is sqrt(2)/2.
It's a shame that sin and cos get lumped in with all the other trigonometry that you don't need to know, because the two basic formulas are incredibly useful and easy to learn:
x = distance * cos(angle)
y = distance * sin(angle)
Screw the rest. I learnt these as a kid writing a 2D computer game years before coming across them in high school maths.
It's still baiting you - why are they hated? The article is a good presentation and tutorial on this particular feature which is itself interesting, but the current title could mean many different things and isn't very clear. Is it a list of hated features? Is it a rant about CSS?
It's crazy to me that a significant number of people know "cos" and "sin" primarily though CSS. Is that really what this is implying? Or maybe people just find them hard in general, but it seems odd to think of them as features you dislike, rather than attributing the dislike to the underlying math, if you've ever taken a trig class before.
This seems like the type of thing that I'd want to like. But the necessity of inline assigning the `--i` CSS variables to each element bothers me. I have to use some template system or manually keep these variables in sync in my markup. Doing those things seems worse than doing this kind of layout arithmetic in javascript, loathe though I am to admit it.
He does mention at one point that sometime soon it won't be necessary:
> Note: This step will become much easier and concise when the sibling-index() and sibling-count() functions gain support (and they’re really neat). I’m hardcoding the indexes with inline CSS variables in the meantime.
In your CSS. Still not all that ideal given you need to ensure you have enough entries for all the entries you might have... but at least a more dynamic and self-contained option until the `sibling-index()` feature they mention roles out.
I just checked with some code that I wrote a while back to rotate a faux-3D pyramid, to see how I did it. The trigonometry was the easy part, it was the backface culling that was the hard part. Anyway, I decorated my elements with CSS variables in script and used lots of Math.sin/cos/tan. Also present were lots of radian conversion things and the fun that goes with animating things the 'right way'. Basically oodles of extra stuff that took me the best part of a week to do, to result in something that memory leaks if left running for a few hours.
Now I have seen this article, I might just have to mix and match JS and CSS, so I build out the elements in code and add the CSS variables to them, for everything else to be done in CSS. I will obviously need an intersection observer to trigger the CSS rather than my JS, and so it goes on!
Either way, the trigonometry is the easy part, fixing that memory leak the hard part, but CSS is the way to go because that will work perfectly, unlike with JS.
I would have thought the most-hated feature would be the `float` property. I guess alternatives have been around long enough that people just ignore it rather than nurture an eternal smouldering hatred for it.
Personally have not seen a float used in the wild since flex-box gained traction. And a simple .clear-float utility class usually addressed the most common float issue.
"What I find funny about cos() and sin()— and also why I think there is confusion around them — is the many ways we can describe them. We don’t have to look too hard. A quick glance at this Wikipedia page has an eye-watering number of super nuanced definitions."
I don't even know how to begin parsing this sentence.
Post-acquisition the Digital Ocean ran it for a little while with the same staff, then they let a whole bunch of people go (both digital ocean and css-tricks staff).
The css-tricks website was basically dormant for a few years.
Chris (the original creator of css-tricks) sick of seeing his creation stagnate tried to get Digital Ocean to get the website going again but it looked like Digital Ocean didn't know enough about the site to resume posting.
At some point the website's editor (Geoff) who had been let go as part of the layoff came back to work on the website and their was much rejoicing.
CSS-trick's content had a bit rocky at the start of its comeback, but it's feels much better now than it did when it first resumed.
The vibe is a little bit different now, but I think that's because so many webdev writers are experimenting and writing in the open on mastodon before posting on their own blogs and larger platforms like css-tricks.
We didn't get as much of a peak behind the curtain before.
I can't wait for the LLM() function to drop.
That's already the present. The result is just cached.
it is unethical to do this without stimulating the economy:
You forgot "Take a deep breath. Don't make mistakes. An old lady will die if you misplace a div."
Anecdotally I've found it better telling the llm it's in a high growth tech startup on an H1B, any mistake will risk termination and being sent back home where they'll have to become a trash picker.
I'm always surprised how eager are LLMs to role play.
That's what a LLM based template engine looks like.
I actually am really looking forward to a future where we have better tooling for a true "user agent" that knows my preferences and can style every page automatically just ust the way I like it (and letting me override anything by asking it once and having it remember). I'm so tired of UX designers choosing things for me assuming I'm a 5-year old.
It seems far more likely that we'll end up in a state where you won't be able to override CSS at all. You'll be allowed to use only the most modern version of Google Chrome because all the websites will simply require a private auth key that only Chrome possesses, and commands like cURL will no longer function properly. The devtools console will be locked behind a key that you must petition Google to get, and if you use it for anything other than what they want, your permissions will be revoked without further recourse.
I've had similar thoughts but replacing Google with Apple who I could easily seeing doing parts of this. They have the platform stranglehold and abusive history to support the behaviour and current browser "enforcement", with little to nothing in the way of consequences.
It’s a very sad future, but totally plausible at this point. We’ve got to fight this.
Two counterpoints to this.
- A good designer will be able to produce a page whose looks are appropriately engaging, complementary to the content, unique, and easy on the eyes. For every abrasive CSS (or lack thereof) justfuckingusehtml.com, there's a masterpiece like acko.net, many of which just aren't in the mainstream.
- If everything ends up looking the same wouldn't that get... boring? I get the desire to avoid obnoxious design choices, but those obnoxious design choices are part of the web, and they should be embraced as part of the decision-making process about if and how you want to keep reading a site. A bit of friction is, IMO, a good thing when browsing the web. It's the minimum level of keeping the web an interactive medium rather than just a content pipe.
That said, you do you. You're well within your rights to browse the web how you want, up to and including using automation to re-style sites with extreme prejudice.
> asking it once and having it remember
Uhhh, that reminds me of the super duper helpful way YouTube automatically enables dubbing and/or subtitles based on the last video I watched, my browser language, my account language, where I am in the world, phase of the moon, the colour of my shirt...
"Can you make it pop more?"
hallucinates ‘fluent’ and draws a net to catch eyes
Surprises me when people hate on trigonometry. I enjoyed trig in high school so much that I made it my internet alias.
Did you learn it as “sign on highway, cozy at home, tan on arm”? That’s basically the only high school math that stuck with me.
Oh and I guess negative b plus or minus b squared something something four a c over two a. I think there’s a square root to shove most of that into.
I always thought sohcahtoa itself was quite memorable. Sounds like a war cry!
Or something those wordy math textbooks would have had - the Sohcahtoa Indians who dealt in triangles …
It would get him fired today... but my trig teacher showed up to this lesson shirtless in a floor length native American headdress, and ran into class yelling "I am Chief SohCahToa! Never forget my name!!".
And by God, I never have. Thanks Mr. Wilkinson.
That sounds like an actual teacher! Amazing.
always made me think of krakatoa (the exploding island)
It sounded to me like something some colonists would carve into a fence, like CROATOAN.
SOHCAHTOA.
In my school, it was "Some Old Hippie Caught Another Hippie Tripping On Acid," which succeeded in being quite memorable for me. In retrospect it seems a bit wild compared to some of the examples here, especially considering it was taught at a public school in the US deep south!
We made this up in school: "saya tak hensem, kalau saya hensem, tentu Tipah suka" [opposite = tentang, adjacent = sebelah, cos = kos]
Translation: I'm not handsome, if I were handsome, Tipah (our principal) would like me"
25 years ago and I still remember it clearly. Also it was middle school education on how to solve problems in a different space; this one solving math in a second language space lol
I learned it as: Some old hags, can't always hide, their old age.
I guess this is the version we use in Australia.
Sex On Holidays Can Advance Happiness To Outrageous Amplitudes. Not suitable for a high school class, though.
No. Just "Sohcahtoa" was enough. Didn't need to create a backronym for it.
And the quadratic equation...yeah, I don't remember that one.
For us it was "Some officers have curly auburn hair 'til old age". Never seemed like a good mnemonic given that you have to shorten "until" to make it work and none of us had any idea what "auburn" was, but I still remember it 20 years later so...
Sorry, what are all these mnemonics for? I can't imagine what you are trying to remember with these, as we never introduced such mnemonics in school.
https://i.imgur.com/pyVZpqF.png
S - Sine O - Opposite H - Hypotenuse SOH is a way to remember sine = opposite / hypotenuse
A - Adjacent T - Tangent C - Cosine
In the UK it was “Attack Henry Cooper, outside his shop, on a Tuesday” no idea why the random violence but I never forgot it
For me, UK, posh school, 1980s it was just "sohcahtoa" - easy enough to be its own mnemonic. No need to gild a lily.
Your order is cosine, sine, tangent - CST. A quick look at the other examples here seem to prefer SCT - as do I but only because that is what I was taught.
I also note your mnemonic is very different to the one I learned in having the function name last. So AHC vs CAH.
There is no right or wrong here but I'm sure we can agree that there are loads of mnemonics for these basic trig formulae and nationality isn't involved.
UK, state school, late 90s/early 2000s, also just "sohcahtoa" - pronounced as a single word mostly. It never felt like it needed more than that?
It seems we have an agreement on this. There is no need to gild the lily!
I also went to a lot more schools than normal, thanks to living in multiple countries and my dad (army) moving every 18 months or so!
sohcahtoa is nearly a word.
UK, state school: “some officers have coaches and horses to order about”
For us it was: "two old angels skipped over heaven carrying a harp"
Allegedly your grandpa, armed with his slide rule, has even more random violence:
"Spitfire or Hurricane come and hurry to our aid"
This works for me as the order of the functions matches the order shown on my trusty FX82A. Your version is kind of messed up.
I am giving this AI thing a wide birth, however, could we ask a LLM to invent a new aide memoire for this? We have got the silent generation and the boomers covered, but is there something we can do for kids today? Maybe it references Cinnamoroll, Hello Kitty or Octonauts characters that actual kids know, without it being ultra-violent.
some old hippie caught another hippie tripping on acid
I find it conceptually cool, but I struggled in school with learning the identities, memorization being one of my weak areas.
If you know your trig well enough, you can derive the identities.
For example, knowing that cosine and sine are the exact same wave, just 90 degrees out of phase, it's trivial to know that sin(angle) = cos(angle + 90)
cos(a)^2 + sin(a)^2 = 1 is easy to show, too. If you use a=0, it's trivial. But try using 45 degrees. It turns into (sqrt(2)/2)^2 + (sqrt(2)/2)^2 which simplifies to 0.5 + 0.5 = 1.
Many of the others can be derived by just manipulating the Law of Sines or Law of Cosines. Fun fact: The Pythagorean Theorem is actually just a special case of the Law of Cosines:
c^2 = a^2 + b^2 - 2*a*b*cos(C)
Recall that in the Law of Cosines as I've written it, the lowercase letters are the sides, and the large C is the angle opposite that side. So if you choose your hypotenuse to be c, then the opposite angle, C, is 90 degrees. cos(90) is 0, so that whole last term gets cancelled out and you're left with the equation known as the Pythagorean Theorem.
I really wasn't kidding when I said I enjoyed trig.
Too late to edit now, but wanted to add a note:
Knowing that cos(45) == sqrt(2)/2 seems like something you would need to memorize, but if you just draw an isosceles right triangle with sides equal to 1 and use the Pythagorean Theorem you'll find that the hypotenuse is sqrt(2)/2.
This made my day. Great alias!
Some Old Horse Caught Another Horse Taking Oats Away
Obligatory xkcd: https://xkcd.com/809/
You think they hate trigonometry, then you tell them about radians and they really hate trigonometry. Which is... crazy really.
It's a shame that sin and cos get lumped in with all the other trigonometry that you don't need to know, because the two basic formulas are incredibly useful and easy to learn:
x = distance * cos(angle)
y = distance * sin(angle)
Screw the rest. I learnt these as a kid writing a 2D computer game years before coming across them in high school maths.
Nah, the rest is pretty great aswell. Lest you go to gamedev hell by saying you dislike atan2
Mods, new title suggestion: "CSS's cos() and sin() features"
I would wholeheartedly support the mods rewriting every clickbait headline on HN (there are just so many…)
But it's not really a clickbait title.
If it was clickbait it wouldn't say what the 'most hated' css feature is to bait you into clicking it to find out what the feature is.
> The “Most Hated” CSS Feature
> The “Most Hated” CSS Feature: cos() and sin()
It's still baiting you - why are they hated? The article is a good presentation and tutorial on this particular feature which is itself interesting, but the current title could mean many different things and isn't very clear. Is it a list of hated features? Is it a rant about CSS?
It's crazy to me that a significant number of people know "cos" and "sin" primarily though CSS. Is that really what this is implying? Or maybe people just find them hard in general, but it seems odd to think of them as features you dislike, rather than attributing the dislike to the underlying math, if you've ever taken a trig class before.
I take it as the second assumption, as in people who think "CSS has already gotten too complex, now this complicated trig shit is part of it too?".
Keep in mind it's only 9.1%, or 1 in 11, that actually had a "negative opinion" of it. This makes the phrasing/focus on "hated" seem a bit forced.
This seems like the type of thing that I'd want to like. But the necessity of inline assigning the `--i` CSS variables to each element bothers me. I have to use some template system or manually keep these variables in sync in my markup. Doing those things seems worse than doing this kind of layout arithmetic in javascript, loathe though I am to admit it.
He does mention at one point that sometime soon it won't be necessary:
> Note: This step will become much easier and concise when the sibling-index() and sibling-count() functions gain support (and they’re really neat). I’m hardcoding the indexes with inline CSS variables in the meantime.
The inline links there go to https://css-tricks.com/almanac/functions/s/sibling-index/, which is pretty nifty honestly.
Inlining isn't necessarily a requirement for how it's used here. E.g. you could put something like:
In your CSS. Still not all that ideal given you need to ensure you have enough entries for all the entries you might have... but at least a more dynamic and self-contained option until the `sibling-index()` feature they mention roles out.Agreed.
I just checked with some code that I wrote a while back to rotate a faux-3D pyramid, to see how I did it. The trigonometry was the easy part, it was the backface culling that was the hard part. Anyway, I decorated my elements with CSS variables in script and used lots of Math.sin/cos/tan. Also present were lots of radian conversion things and the fun that goes with animating things the 'right way'. Basically oodles of extra stuff that took me the best part of a week to do, to result in something that memory leaks if left running for a few hours.
Now I have seen this article, I might just have to mix and match JS and CSS, so I build out the elements in code and add the CSS variables to them, for everything else to be done in CSS. I will obviously need an intersection observer to trigger the CSS rather than my JS, and so it goes on!
Either way, the trigonometry is the easy part, fixing that memory leak the hard part, but CSS is the way to go because that will work perfectly, unlike with JS.
I would have thought the most-hated feature would be the `float` property. I guess alternatives have been around long enough that people just ignore it rather than nurture an eternal smouldering hatred for it.
Personally have not seen a float used in the wild since flex-box gained traction. And a simple .clear-float utility class usually addressed the most common float issue.
"What I find funny about cos() and sin()— and also why I think there is confusion around them — is the many ways we can describe them. We don’t have to look too hard. A quick glance at this Wikipedia page has an eye-watering number of super nuanced definitions."
I don't even know how to begin parsing this sentence.
That's three sentences, none of which are particularly difficult to parse
So why do people hate CSS's trigonometry implementation?
CSS trig functions, combined with mod() and friends, effectively enable seeded random noise functions as they did in shaders. Interesting times.
They are also planning to add random() although no browsers support it yet.
filter also had some randomness support (via svg <feTurbulance>
When I loaded up the page, something like 5 empty HTML files downloaded automatically, did this happen to anyone else? Firefox Linux
No such incident here. Firefox on GNU. Also using uBlock Origin, though.
oh wow first css tricks i've seen post acquisition
what's up with the magazine in general... is it doing ok?
Post-acquisition the Digital Ocean ran it for a little while with the same staff, then they let a whole bunch of people go (both digital ocean and css-tricks staff).
The css-tricks website was basically dormant for a few years.
Chris (the original creator of css-tricks) sick of seeing his creation stagnate tried to get Digital Ocean to get the website going again but it looked like Digital Ocean didn't know enough about the site to resume posting.
At some point the website's editor (Geoff) who had been let go as part of the layoff came back to work on the website and their was much rejoicing.
---
You can read more about it here: https://chriscoyier.net/2024/02/28/where-im-at-on-the-whole-...
---
CSS-trick's content had a bit rocky at the start of its comeback, but it's feels much better now than it did when it first resumed.
The vibe is a little bit different now, but I think that's because so many webdev writers are experimenting and writing in the open on mastodon before posting on their own blogs and larger platforms like css-tricks.
We didn't get as much of a peak behind the curtain before.
brb gonna see how much of DOC’s Demons Are Forever can be collapsed into simple css animations (https://m.youtube.com/watch?v=3tSI8gw_yUQ)
Is it just me or did none of the examples show up in Codepen? The code was there, but nothing showed in the display.
Hmm, worked for me on macOS, Linux, and Windows across Chrome/Firefox/Safari.
It didn't work for me the first time I opened it, but did after the second.
[flagged]