Thinking of "compiling" CSS to x86 instructions directly to make matching even faster and basically do away with any sort of data structure for the selectors since it'll just become a stream of instructions... apparently I'm not the only one who thought of doing this.
Cudder is all booster, no payload Cudder is all crown, no filling Cudder is all foam, no beer Cudder is all hammer, no nail Cudder is all hat and no cattle Cudder is all icing, no cake Cudder is all lime and salt, no tequila Cudder is all mouth and no trousers Cudder is all shot, no powder Cudder is all sizzle and no steak Cudder is all wax and no wick
>>930 Yes they did, they said Cudder would publish something.
Name:
Anonymous2016-04-04 20:21
>>934 Here's how the conversation went. ================================== ★ Cudder delivering his browser at 1001! ▲ Post 1001 does exist, actually. You just have to link to it specifically to see it. See the Crossposters threads on /lounge/. ★ No one said it didn't. ================================== Okay?
Name:
Anonymous2016-04-04 22:02
>>935 My joke was that Cudder will never deliver, thus the post he will deliver it in does not exist. I didn't work out well, so just never mind. I'm changing the subject. I love you, Cudder, 👭👭💑💑💑👺👺💆👄💋❤💙💚💛💓💜💔💕💖💟💞💝💘💗🐇🐰🐭🍭🍭🍦🍦🍧🍨🍨🍧🍬🍎🍌🍌🍌🍌🍌🍌🍌🍌🍌🍌🍥🍆🍆🍍🍍🌷🌷🌷🍓🍓🍓🌸🌸🌸🌹🌹🌹🌹🌋🌋🌋🗻🗻🗻💐💐💐💒💒💒💌💌💌💍💍💍💎💎👗👗👢👢👢🔰🔰💵💴💶💷💸🎃🎵🎵🎵🎼🎼🔥🔥💦💦💦👪👪👪👪👪👪👪👪👪👪👪👪👪👪👪👪, pleaze marry me!
Name:
Anonymous2016-04-04 22:16
Cudder is married to LAC!
Name:
Anonymous2016-04-05 4:56
Please do not bully Cudder-sama. I'm sure she is doing her best to create a releasable binary for us as we speak. We need to believe in her.
255 attributes per simple selector ([a1=v1][a2=v2]...[a255=v255]) 255 simple selectors per selector (#s1 + .s2 > .s3 #s4 ... s255) 4G selectors in total (theoretical limit, actually limited by memory available)
These limits should be sufficient for basically all the CSS out there... and if it's not, then fuck you. No page should ever have anywhere near that much CSS, and if you do you'll probably crash other browsers and deserve to have your page displayed unstyled.
>>950 Your are making for """more bloat""" because software has to try to get around your fucking bullshit limitations to actually work. There is no goddamn sensible reason for what you're doing, as computers are generating CSS and queries automatically and need room to work in.
>>958 Are there any sites (besides contrived limit-testing test cases) that come anywhere near those limits? How about showing some examples instead of spewing vague "generating CSS and queries automatically " bullshit? That's the sort of attitude that leads to insane ENTERPRISE solutions where 99% of the complexity is there just for 0.1% of the use cases.
There's no point in having more than 255 attributes per selector either, since HTML5 doesn't define that many. Look at the discussion about CSS property maps above - why use a data structure optimised for thousands or more elements and is dynamic-everything, even if it's "theoretically more efficient", if you will never put more than a dozen or maybe 100 at most in it? Premature generalisation. That's real bloat.