Earlier quoted context omitted.
Nice! I'm working on a private Recipe bookmarking site that currently has no JavaScript and minimal CSS. https://github.com/bradly/recipin
Nice commit emojis
Just use HTML
181–188 of 188 posts
Re: Just use HTML
#182Earlier quoted context omitted.
Wait, this actually says to use the implicit ID mapping on the global object? That hasn't been good advice since about 1999! edit: I checked and wow, it really does. Good grief, did an AI write this? Use getElementById or querySelector or querySelectorAll or any other remotely modern web API method instead.
Genuinely curious (as someone who didn't know about the implicit ID mapping until today): given that IDs are global, why is doing this any worse (or in any way different) to using getElementById? I.e. why is it bad advice?
Offhand these days I would expect asynchronous loading and rendering both to pose additional concerns. You may not be able even to guarantee whether or not the element you're trying to reference by ID exists at the time of reference. Oh, you can synchronize on DOMContentLoaded or something like that, but that's not going to do anything good for performance. And for that matter, you'd probably have to toggle a TypeScript compiler option I've never heard of, to get this sort of thing to even sort of fly - and there again, the API methods dating from this millennium will be mostly the ones where the type system is able to offer some guarantees.
Re: Just use HTML
#183Earlier quoted context omitted.
I’m sure it’s possible, ChatGPT is trained on people after all.
Look - the content is good and some of us are not native English speakers. People should edit their chatgpt correction but we should stop calling everything AI generated without real proof. Anyway, if the comment is meaningful and adds to the discussion, why should I care if it was AI generated?
And no, I don’t think the content is good and meaningful in 99% of the cases.
Re: Just use HTML
#184Earlier quoted context omitted.
What ? Why ? Doesn't seem clear to me.
There’s more But it’s clear to me from the first word “Look — …“. No one starts a comment like that, except ChatGPT who does it all the time. I frequent subreddits where AI use is super common and the vibe is always the same.
Re: Just use HTML
#185Earlier quoted context omitted.
It’s not about what I want. It’s about what’s fact or fiction in the face of possible lies. I think you’re lying because you’re so offended. It hit a nerve. Whatever made your career front end react certainly seems like a big part of it.
You’re making stuff up. You should try your luck as a non sci-fi writer. Thanks for your psychoanalysis. Don’t think too much. It doesn’t seem to work anyway… You have your answers at the fingertips and yet you choose to make shit up. Like I thought, you’re an ignorant person who has a desire to judge others. You do live in a bubble, indeed.
Re: Just use HTML
#186Re: Just use HTML
#187Re: Just use HTML
#188Earlier quoted context omitted.
Oh? All things considered, I believe html and css are both great. Incredibly flexible and very easy to get a basic "framework" started for consistent design Everything else I've used to date (for UIs) was either extremely limited or way more complicated to use in comparison I personally feel like the only thing we're missing is a way more aggressive deprecation policy. Not actually removing the API, just clearly sign…
CSS is really great, and I've felt this way since it was introduced - but the lack of tooling around it today is anachronistic
Why can’t I click an element and see the css files that apply to it? Why can I get autocomplete for my utility classes and custom properties? I would happily nuke CSS from a project for a typescript library that could marry the two worlds with minimal trade-offs, but I’ve yet to have the time or courage to dive into a library like vanilla-extract: https://vanilla-extract.style