"too strong coffee" - sorry. you lost me there.

i do not understand this phrase.

*sips on a cup of caffeine-based tar

by making everyone believe that this is just a distraction, while it actually _is_ the real vessel?

if it's free, you're not the customer, but the product.

you simply pay with your data instead of your money.

@BordedDev we're talking about "validating single form fields" - the total payload of this is significantly less than the HTTP overhead. bandwidth is of no significant concern here, unless you do it very wrongly.

@jestdotty you don't have to announce yourself, you know? you're not that significant.

@Grumm "problem solved" in the same way that jumping off a bridge does.

um... hot-reloading on anything but a dev-server is pretty dumb.

and if you deploy to prod _that_ often that the application start time matters in any significant way, then your whole infrastructure is screwed up in soooo many ways

@BordedDev "doing “real-time” validation — normally only possible efficiently in the browser." - that's where you are wrong.

proof:

implement your real-time validation with JS to your hearts content, but in your method `PerformTheActualValidationCheck`, you simply query the backend.

whoever designed that database... have they heard about "not sucking at their job"?

@BordedDev "but the screen jitter, the scroll resetting, having to find which field it doesn't like is even more annoying."

that's just a problem of "terrible and terribly outdated UX".

have a better, faster, smarter life, then.

the number is 10.

if you think it's wrong, then you're just thinking in the wrong number system.

@Lensflare trim those as well

@daniel-wu the problem about doing it twice instead of doing it once and reusing it: there WILL be discrepancies.

just last year i've inherited a project where the frontend would allow passwords that the backend declined, and vica-versa.

with the additional WTF-bonus of the login-form having a password-pattern validation that didn't match up with the signup-password-pattern.

keeping it in one place completely prevents this kind of problem.

@BordedDev well, i'm talking about implementing it in a non-terrible way. 3 seconds is too much. but 200ms - you wouldn't care.

@jestdotty lol you sound like an overly entitled karen (pardon the redundancy) with more mental issues than there are days in a 100-year-calendar

@null-pointer-ex not just in your opinion. that's just how it is.

and the thing is: if you're alread implementing it in the backend, why double your work by implementing it again in the frontend?

after all, you could just be smart about it and asynchronously check the form. you don't need to reload the whole page. and i doubt the user will notice if the info that "dick" is too short a password comes after 0 oder 100 ms

client-side validation never WAS recommended - if you're talking about "client side _instead_ of server side".

because anything and everything that happens client-side can be easily manipulated by a malicious user. or just circumvented by manually sending a request.

> Turns out I forgot to double check how the code generated by GPT

so... classic blatant user error, then?

@antigermanist "nobody left behind"? more like "everybody left rotting in the ground", because yes, it IS a suicide pact, and only an utter idiot would do it.

you totally should.

sounds like a good idea, you should start ASAP and set a sample.

because this joke has been done to death decades ago already

that's not a surprise.

it's javascript.

_brainfuck_ is better than javascript. at everything.

AI is just another tool.

no, it won't take your job, unless your job is garbage AND you're garbage at it.

realtek fucking sucks, period.

@PappyHans "those people" are usually the people in position to put others on improvement plans or sack them.

the world of careers is like a sewer. the scum floats to the top.

if the concept of "explosion" wasn't something the average person would perceive reasonably often? i mean... guns and fireworks have been used long before the motor.

neural nets, however, is something that eludes most people even if you hammer it into their brains three times a day.

"I like a lot of the design decisions to not make foot guns. Like you can't use an int as a bool." - you mean... Proper Typing?

@retoor happiness.. such a nostalgic word, does it even matter anymore in 2024?

@PappyHans yes. dumb people.

nope.

the internet was at maximum weirdness from day one.