#hottake CSS is too hard to read
As a #UX designer, I want code to have a clear, clean syntax that is easy to understand. I was excited that Nesting would improve how to write/read CSS but I'm horribly confused, e.g. when to use &. Here is the 'help text':
"Nesting classes without `&` will always result in descendant selectors. Use the `&` symbol to change that result"
This means nothing to me. I understand it's a complex problem but does the syntax need to be so baroque?
Scott Jenson /
npub1rx…qjq60
2023-09-27 12:19:11
Author Public Key
npub1rxsaaak8vdzlfg3lcsg2vnx8v9vnf98ec55v6qv0g4xhqu22kpzq9qjq60Published at
2023-09-27 12:19:11Event JSON
{
"id": "8ef678e4f546a1602f1a9ea440b0cae9712a8fff31971d99adb9734223374338",
"pubkey": "19a1def6c76345f4a23fc410a64cc761593494f9c528cd018f454d70714ab044",
"created_at": 1695817151,
"kind": 1,
"tags": [
[
"t",
"hottake"
],
[
"t",
"ux"
],
[
"proxy",
"https://social.coop/users/scottjenson/statuses/111137072871364130",
"activitypub"
]
],
"content": "#hottake CSS is too hard to read\n\nAs a #UX designer, I want code to have a clear, clean syntax that is easy to understand. I was excited that Nesting would improve how to write/read CSS but I'm horribly confused, e.g. when to use \u0026. Here is the 'help text': \n\n\"Nesting classes without `\u0026` will always result in descendant selectors. Use the `\u0026` symbol to change that result\"\n\nThis means nothing to me. I understand it's a complex problem but does the syntax need to be so baroque?",
"sig": "bb182d63397eb3070595ee5e659e9742969588d92a49c2bb7c7a3e22b70f83c34468f2fa6ae402c44d62bdba47028c9c617ad0b5d4445a631cc4474087d91b21"
}