Google argued that duplicating largely (I know JpegXL does support a bit more, but from most users' perspectives, they're largely right) what AVIF provided while being written in an unsafe language was not what they wanted in terms in increasing the attack surface.
And it really was the right move at the time, imo. JXL however now has better implementations and better momentum in the wider ecosystem and not just yet another image format that gets put into chrome and de facto becomes a standard.
I can confirm.
I found multiple problems in the "official" cjxl encoder back in 2023 contrary to the webp2 (cwp2) implementation where I could not find any bug or error.
If the encoder have obvious problems it is not a big deal, but it doesn't bode well for the decoder.
That graph is number of questions asked being posted: very often the question already exists (although obviously with technology and frameworks changing over time, things aren't constant, and answers can be out of date at some point), so you don't need to post the question.
Also: Would LLMs be as good for answers if they hadn't been trained on scraping StackOverflow in the first place?
I very much disagree with the first point that there had somehow been a critical mass of questions achieved to explain the slowdown. With the change in tech, outdated answer, and increasing population of people writing code, I just don't buy it.
Roughly that figure (45%) was used to get to Mach 2.0 at 60,000 feet, about 45 minutes after takeoff from LHR (normally over the Bristol channel) to JFK.
Takeoff and climb / accel to Mach 1.7 was done with re-heat (afterburners), which did use a lot of fuel. After that, normal power (no re-heat) was used to get to Mach 2.0 and cruising (supercruise).
There's experimental/nightly support for things like: `push_within_capacity()` which is a more manual way (user-space code would have to handle the return code and then increase the capacity manually if required) of trying to handle that situation.
Vec::push_within_capacity is a nice API to confront the reality of running out of memory. "Clever" ideas that don't actually work are obviously ineffective once we see this API. We need to do something with this T, we can't just say "Somebody else should ensure I have room to store it" because it's too late now. Here's your T back, there was no more space.
It takes over 10 seconds to turn off fully. I had to go back and try it after your comment, because I thought that button just turned the page yellow, which was worse than the blue.
I ended up using reader mode to read the page. The whole site design undermined the point being made. One of the first things mentioned is not to be distracting. Yet they went out of their way to make their own site distracting. "Do as I say, not as I do."
I literally didn't notice that the snowflake icon turned it off:
1. I scrolled through the article getting more and more frustrated with the snow
2. I scrolled all the way back to the top and saw the snowflake icon
3. I clicked the snowflake, saw the hideous yellow, said WTF and clicked again to go back to blue
4. **I never noticed** that the snowflake *does* stop the snow, but *only* stops *new* snow, so the existing snow continues to fall across the screen
5. I clicked several other things, then came here to complain and saw this thread
Just to clarify: Unless I've missed something, this is only with WAL mode and concurrent reads at the same time as writes, I don't think it can handle multiple concurrent writes at the same time?
As I understand it, there can be concurrent writes as long as they don't touch the same data (the same file system pages, to be exact). Also, the actual COMMIT part is still serialized and you need to begin your transactions with BEGIN CONCURRENT. If two transactions do conflict, the later one will be forced to ROLLBACK although you can still try again. It is up to the application to do this.
Also just a note: BEGIN CONCURRENT is not in mainline SQLite releases. You need to build your own from a branch. Not a huge deal but just something to note.
Guessing it’s what he said in 2002? But the Tablet EIC made these remarks last week. Not really equivalent, although you’re entitled to your media choices.
A referendum to dissolve parliament and give the prime minister power to make law was submitted to voters, and it passed with 99 per cent approval, 2,043,300 votes to 1300 votes against.[83] According to historian Mark Gasiorowski, "There were separate polling stations for yes and no votes, producing sharp criticism of Mosaddeq" and that the "controversial referendum...gave the CIA's precoup propaganda campaign to show up Mosaddeq as an anti-democratic dictator an easy target".[84]
A person has to be very gullible to believe 99% of the vote went one way in a fair election involving 2+ million people.
I had a Thinkpad T480s that was absolutely perfect with Linux (Mint), although very underpowered, but that was due to Intel CPU.
This year I got a T14s Gen6 AMD as a replacement, and it's essentially unusable on Debian-based distros (Ubuntu, Mint), but works fine with Fedora and with Windows.
On Ubuntu and Mint, X just locks up every 80 seconds or so, and I have to hard-reboot it (or switch ttys and restart X). Nothing in syslog, nothing in dmesg, nothing in X.org.log to show what might be going on.
I have the T14s Gen3 AMD and everything just works with CachyOS and Fedora. In general I tend to use as recent kernel as possible with AMD. They do update their drivers a lot in every Linux version.
Some modern films are still filmed with anamorphic lenses because the director / DP like that, and so we in the VFX industry have to deal with plate footage that way, and so have to deal with non-square pixels in the software handling the images (to de-squash the image, even though the digital camera sensor pixels that recorded the image from the lens were square) in order to display correctly (i.e. so that round circular things still look round, and are not squashed).
Even to the degree that full CG element renders (i.e. rendered to EXR with a pathtracing renderer) should really use anisotropic pixel filter widths to look correct.
reply