CREATE TABLE display ( id INT PRIMARY KEY, display_property TEXT ); INSERT INTO display (id, display_property) VALUES (1, 'block'), (2, 'inline-block'), (3, 'flex'); CREATE TABLE divs ( id INT PRIMARY KEY, inner_html TEXT, display INT REFERENCES display(id) ); INSERT INTO divs (id, inner_html , display) VALUES (1, 'div1', 1), (2, 'div2', 2), (3, 'div3', 3);.users { id: int !primary-key; name: text; } .users::insert { id: 1; name: "John doe"; } @query (max: 10) { .user { display: table; } .users id { display: none; } }Thanks, I hate it.
They both feel so wrong, I love it.
I think I need to lie down.
I prefer SQL, because you can pronounce it “sequel” or “es-cue-ell”, and it’s fine. CSS just doesn’t have that kind of flexibility as a language.
CSS also pisses me off because it clearly doesn’t cascade… to contrast SQL is a language, it is used for querying… and it’s structured horribly. Please for the love of God let me
FROM foo WHERE bar SELECT bazI have also heard some say “school”
i’m leaning towards “skull” tho
“I dropped a table with skull”
it has a nice ring to it
Oh. Now I want one of these for every pairing. Vim vs Windows. Bubble Sort vs. SODIMM. The beauty is, with LLMs, I can have it! Enter two of any computer terms, and ChatGPT spits out a comparison. And why stop with computer stuff? Eukayryotic vs Republican! The War of 1812 vs The Kessel Run!
I think the real question on all of our minds is which is better: JavaScript or megabytes
Having worked with tables in both I’m partial to French.
Is this chatGPT generated?
Filing cabinets or oil paints? Which is better?
Tried to store documents in paint and it ruined the documents, 0/10
I’ll let you know how my file cabinet art show goes
O.o
C
Ss
Of cour
Se
What in the actual fuck
Obviously CSS
deleted by creator
This is a pretty roundabout way of saying back-end vs front-end.
