Kwantuum

> The structure is identically to all of that, big title, graphic, list with icons

You're complaining about posters being structured like posters?

But also the structure is particularly similar between these posters themselves across styles because they use the same prompt to describe the desired content and that's on purpose. The model is not asked to rework or reword any of the content, this lets you compare the styles.

I think that's unfair. Many local community fairs happen to have a graphic designer or someone with some of the same chops who's willing to lend a hand to design a decent poster.

If you already know the bug is caused by a race between writing and checkpointing then it's easy. I'm unsure how the linked article makes your point at all though.

I don't think the people who opposed those things look foolish even today. Most of those things, in their early days, were implemented haphazardly and with an incredible lack of regulatory oversight, and the reason they were not quite as disastrous as they could have been is that people opposed them.

And people opposing data centers today who are opposing unfettered data center creations will not look any *more* foolish than those who opposed the things you cite.

The fact that this can happen at all without the security team's knowledge is telling.

I trust openAI's marketing team 100%

Interestingly, in the company I currently work for, if an employee encounters a problem with the product, the expected way to report the issue is to open a ticket. Not in an different system with different people responsible for handling it, in the same ticketing system that customers use.

Hackintosh refers to doing things the other way around: running MacOS on non-apple hardware. So no, this is not a hackintosh.

Both of the things you quoted are basically gone in practice, you just always use const/let and always use triple-equals for equality comparisons and that's that. Most people that write JavaScript regularly will lint these out in the first place.

OTOH I think JS has great ergonomics especially wrt closures which a number of popular languages get wrong. Arrow functions provide a syntactically pleasant way to write lambdas, let/const having per iteration binding in loops to avoid nasty surprises when capturing variables, and a good number of standard methods that exploit them (eg map/filter on arrays). I also think, though a lot of people would disagree because of function coloring, that built-in async is a great boon for a scripting languages, you can do long operations like IO without having to worry about threading or locking up a thread, so you get to work with a single threaded mental model with a good few sharp edges removed.

I've had to stop using FF as my development browser because it chokes on large source maps. I used to find lots of issues in our web app that were only ever tested on chromium browsers. I don't anymore because the devtools are unusable past a certain point.

> I guess you can attach a debugger for unit tests, but that's not very useful.

That is in fact incredibly useful

Surely this was meant to be cnt += a[i] > 0

The most egregious problem caused by this that I've encountered is an almost complete inability to use email 2FA on websites because my phone will kill the browser as soon as I switch to my inbox, and when I go back to the browser I'm back on the login screen which will generate a new one-time-password and make the one I have in my clipboard worthless. I've also encountered the exact same problem with 2FA using an authenticator app, though since the codes are valid for ~30 seconds or so, if I manage to enter my credentials fast enough or they auto-fill, at least the code I copied is still valid.