rezonant

yeah it was right there

Isn't that like a day worth of tokens?

I think the article summarizes pretty well what the drawbacks of POST are: unclear idempotency (well it's actually pretty damned clear: they are not cacheable). That complicates caching logic, and that's not just for the application server itself, but any reverse proxies in front of it as well as the user agent itself.

I'm not sure QUERY is a great solution, because in the context of a web application absolutely no one enjoys using a page that does not keep its state on refresh, so that really limits where QUERY makes sense, but if you have a case that is not driven by navigation, great.

Yeah its definitely inconsistent level of specificity. It's "roughly" 197 thousand files, and yet at that scale a human would call it 200 thousand lines of code, and then an exact count of files at 1,816 instead of a similar level of estimation.

For instance I might write this "The pull request alone adds nearly 200 thousand lines of code spanning almost two thousand files", or even better just "The pull request alone adds nearly 200 thousand lines of code" because really who cares how those are broken up into files.

While I agree with your assessment, these data centers cause substantial noise and water pollution-- even if people didn't have a problem with AI the data centers would be a problem for people.

There is a thing called Google, "Linus Sebastian Hard R" is full of information.

...What? Is this the Linus Sebastian misconception of what the hard R is?

Once you are squarely in a Typescript program and not a "Javascript program gradually adopting Typescript", it would be a good idea to enable Strict mode which forbids implicit-any, effectively meaning the only places you can omit type declarations is where the language will infer the type. Typescript for instance does not infer types of function arguments via their usages (like Flow does), which means in strict mode you must explicitly provide a type for all arguments within a function declaration.

I used to be a bit of a pragmatist when it comes to strict mode, but over the years that has subsided, nowadays I think it is plainly obvious that all Typescript programs should use strict mode unless there's a damn good reason. And I'm not sure there are any legitimate damn good reasons.

True there is no ability to forbid an explicit-any type declaration, though.

Are you sure about that? Creators aren't too excited about all of their content being hoovered up and used without compensation or permission, or the AI industry manufacturing economic pressure that devalues quality and the skills they've developed for a craft they are passionate about.

Absolutely same. I have been with Angular the whole time and it's only getting better and better.

I hope more teams give it serious consideration as I just am not excited about dealing with React and it's numerous spinoffs.

Seems the original ::contents proposal is where it's at now, though there hasn't been action on it for some time. Not sure if they hit a snag or it's just on the back burner

https://github.com/w3c/csswg-drafts/issues/2406

This proposal has the benefit of not violating the tree structure should multiple :wrap rules apply to overlapping elements.

So what? I can also open an image in Photoshop and make sure it saves out some Photoshop specific EXIF data and try to claim the image was doctored. What I can't do is go and put my deceptive altered file up in place of the original in all the places on the Internet it exists.

The tropes that AI introduces into articles are very noticeable, quite annoying, and very unnatural -- they unfortunately don't write well. It seems people use them to "polish" up their writing but in reality it would have read better if they hadn't.

My current pet peave is using period instead of comma, as in:

My people lived the other side of this equation. Not the factory floor. The receiving end.

Ostensibly this is supposed to add gravitas, but it's very often done in places where that gravitas isn't needed, and it comes off as if I'm reading the script for an action movie trailer.

i think it's actually a whoosh for you :-)

*Pronunciation

It's actually a third party terminal emulator: https://iterm2.com/

As the article shows, it is a bug in iTerm2. cat is just one program that could trigger it, the key thing is outputting attacker controlled text to the terminal when the attacker can control what files are present (ie unzipping a folder that includes a specific executable file at a well chosen location that gets triggered to run when the readme is output to the terminal)

Nginx has a built in recaptcha page based on rules? News to me.

Even if it does, the point of Cloudflare's WAF is to avoid the traffic touching the origin if the security check doesn't succeed, so any nginx solution isn't really providing the same value.

Or they'll (the site operators using Cloudflare proxy) make ill considered firewall rules like "If not Chrome, require security check".

You had me at "is not Oracle"

Ah, progress!

Except the domain did not expire, if you check WHOIS.

It's only the blockquotes that are out of order. If this were a valid reason to disable user selection, then no website with a sidebar would have it enabled. Besides, you could just disable user selection on the blockquotes if that were the reason (not that I'd ever recommend that)

Why is user-select: none and pointer-events: none applied to the content here? In the DOM it's perfectly serviceable content, even if the divs are absolutely positioned to achieve the editorial layout. If you disable these CSS properties the text is selectable and pastes in the right order as expected, since its based on the DOM ordering which matches the line order...

Additionally overflow is hidden, so you cannot read the entire text on desktop without using a very small zoom... and as others have noted, mobile is fully and completely broken. If the bubbles weren't so huge at least you could read a paragraph or two on mobile.

Full of emdashes and AI comparisons like "The performance improvement is not incremental -- it is categorical" too :-\

This 1000%. Whoever came up with the idea of closing and locking issues because no one has posted on them for awhile is at best not all that bright and at worst downright sinister.

Closing an issue due to staleness is one thing, locking it is another.

Being an asshole? For saying "could have fooled me" to one of the 6 posts on a brand new account heavily advertising video.js benefits in response to my post mentioning that the video element is already both powerful and easy to use, and that adding HLS.js to add HLS support to it for browsers that don't support it natively is dead simple?

I guess your threshold for calling someone an asshole is a bit low.

I don't have a problem with using video.js for the reasons the parent poster mentioned, but HTML5 video is insanely easy to implement, and there's no reason to take on a dependency like this if you don't need something beyond what the web platform already gives you.

We definitely aren't trying to convince anyone to use our free, open source library that doesn't need it.

Could've fooled me...

Using plain video element plus HLS.js is not complicated or difficult.

No one who loved themselves wrote Xlib apps directly either.

Oops yes you're correct. Edited post and put a note about the correction and a link to my previous post describing the correct details.

But it's only 365 days if you install the app on day 1 of your $99 subscription period.