It used to be 30 days. Apple and Microsoft complained because it didn't give enough time to analyze the problem, fix it, test it, and then do a proper rollout to ensure there weren't unexpected side effects in 30 days.

I think what happened was a kernel flaw, meaning a fix could severely impact other subsystems in the OS and thus a fix would need to be carefully done and a properly staged rollout.

The problem isn't the AI tools - Project Zero has real researchers doing real analysis and making sure those AI issues are real. It's likely they're filing issues FFMPEG feels aren't really issues at all.

You might think a bug in a codec used in a 1996 console isn't relevant for security, but if someone can code up an exploit using it, it's suddenly a big deal. I don't have to play back 1996 console video game to hit the bug, I just need to trick someone into getting FFMPEG to see the file as that format and exploit the security hole. (Think sites like YouTube and such that ingest video, for example)

The problem is, there is no right solution. Is it a real security issue? I don't care if it's only for a platform that only only one game released and no one's ever going to practically use it. If it's a way to break into the software and escape my software stack, it's a security issue because all you need is to have someone pretend to be that file. If not, then let the issue be published - even if you don't want to fix it, people who use it might simply be able to disable ingesting that format at all and eliminate the security hole by not having the feature available.

Why don't you move your application to a normal 64 bit server?

Linux may be getting rid of 32-bit support, but that's only a 32-bit kernel on 32-bit CPU support which outside of the Vortex86 SoC no one makes hardware for.

Linux is NOT getting rid of 32-bit on amd64 userspace support, so your program will run just fine in 32-bit mode. Several distributions have tried to get rid of 32-bit usermode support but that was generally met with resistance.

You don't have to port the code to 64 bit - but it also doesn't need to be stuck on a 32-bit machine either. Linux can run 32-bit usermode binaries just fine.

Indeed, you want fun you try WSL1 - the Windows kernel does NOT support 32-bit Linux binaries and that results in it being basically useless. It works for maybe 70-90% of the things but you'll run into odd errors when you hit a 32-bit program. It's why WSL2 exists and it's running Linux in a VM so you can run 32 bit Linux binaries.

Still tons of 32-bit user space code out there. Even Windows 11 dropped support for 32-bit CPUs, but not for running 32-bit applications because I don't think it'll be possible to drop that ever. Even the OSes that did - iOS and Android - it wasn't completely painless and lots of apps just stopped working. On the desktop where there are far more legacy applications, probably not at all likely.

If you want a more flexible tablet, Apple doesn't make them, but they exist.

Android has tablets, and if you wanted a tablet laptop, they exist as well.

The problem is, they just don't work as well, which is why Android tablets are limited to either Samsung or Temu specials nowadays. And convertibles exist but always seemed awkward to use - probably Windows' fault but goes to show perhaps the demand isn't there.

The iPad is 15 years old now, if some tablet concept was the hot thing, the last 10 years of the iPad wouldn't havve been so stagnant. There isn't much new about the iPad now over a few generations past.

It's just a big screen device that does stuff your phone does in a less portable format. People seem to like that - they're at home and want to play games, watch content and social media except on a bigger screen. The fact you can do "creative" things with it is really just to satisfy the fact those people may want to create now and again, and whole social media networks (like TikTok) exist just for mobile and tablet created content.

Slashdot is basically old techy people and this is a fashion label's product not Apple's.

My wife and me just now:

Me: Look at this iPhone sock thing.
My wife's words after I showed her: Is it available in pink
Me: Yes
Wife: Sugoi! Interesting.

She then proceeded to buy one.

Fashion is whatever you make of it.

And just because you don't care about clothes, shoes or small things to hold stuff like purses, doesn't mean others don't. I'm sure there's probably something you care very much for, like a "Red Swingline Stapler" that has to be Swingline.

(And yes, you probably have your reasons, but they're likely going to fall on other's ears like the iPhone sock does on you).

If you think it's a useless accessory, visit a cell phone accessotry store sometime. They sell cases, and they're not all one design - you'll find cases with lots of designs and patterns and other stuff. It's why Apple has a whole lineup of relatively boring cases. It wasn't too long ago when a cellphone case was just a cheap polyurethane sleeve or pleather condom on it coming in black.

Or you see people with laptops that are covered in all sorts of stickers (also common in the tech crowd, too).

Phones are basically flat rectangular prisms. They contain tremendous opportunity for customization and a huge industry has sprung up trying to make your flat rectangle more interesting.

I like my stuff plain and unadorned, but I get others who see it as an opportunity to get a little creative and make their person device a bit more them.

Lots of people spend hundreds (or thousands) of dollars to see someone stand in front of them to do something for a few hours too. Or they buy fancy metal boxes to move around in over more basic metal boxes that do the same thing.

The problem with a linear layout is it's linear. You're going to eventually run into a situation where you have no choice but to have to travel the entire length of it and back just to do anything So you will be traversing the entire city just to get anything done. Anyone who's lived or worked in a skyscraper knows what it's like because those are relatively linear and you have to have multiple tier of elevators where you go from one local to one that serves only certain floors, etc.

It's why towns developed cross streets and eventually into a grid.

And circular cities exist - except we usually call the circles "ring roads", but that's really just a non-Euclidean grid in the end.

Unless everything is planned out properly, your commute and errands will literally involve driving down the city one way until you reach the end, then travelling back to the other end of the city and driving back to your starting point requiring two full traversals of the city. In an era where you want to promote "local" so people can walk to what they need most, this is the antithesis to that, requiring some form of long distance transportation to do anything.

Even the enclosed circle with a central courtyard is a common design to minimize travel time. And it doesn't have to be enclosed - the "quad" having been around for centuries on college campuses and universities was to allow students to traverse multiple buildings in minimal time.

A line is just a tourist attraction. It's not practical because people don't have the patience for it as they'd want shortcuts as the reality of having to cross the city multiple times gets real old real fast.

Or rather, unnamed unions:

struct my_struct {
        int a;
        union {
                int b;
                double c;
                void* d;
        };
        int e;
} foo, *bar;

You can then reference t as foo,a, foo.b, foo.c, foo.d, and foo.e.

Without it the union must be named:

struct my_struct {
        int a;
        union {
                int b;
                double c;
                void* d;
        } u;
        int e;
} foo, *bar;

and referenced as foo.a, foo.u.b, foo.u.c, foo.u.d, and foo.e. Or the less useful bar->a, bar->u.b, bar->u.c, bar->u.d, and bar->e. (And who has NOT gotten confused in a complex structure of structures with pointers and such?)

Using bar->a, bar->b, bar->c, bar->d, and bar->e can make code far more legible.

Often a data structure will have a header that tells you what type it is, followed by a union of available types - so you might have a "type" field that specifies if the following data is an int, for a float, or a double, or a string and then followed by a union of all them.

Or because it's a Microsoft extension, Windows makes use of "size" parameters in structs to be binary compatible. So you might declare a struct, then the first parameter is sizeof(struct), which is used so if the API internally adds more elements, it can switch back to older behavior when given a shorter struct so old programs using the old struct still work with APIs that could take either version.

Javascript is still part of PDF. So are freaking 3d CAD models. They just added HTML to the spec so you can't even rely on PDF being a high-fidelity representation of a printed page anymore. (You might ask, why not just use an actual HTML file instead of embedding it into a PDF file? GOOD FUCKING QUESTION.) ActiveX was never part of PDF though. Flash kindof-sortof was, it was part of Adobe's version but was left out of the ISO standard, and then Adobe removed it from its version.

Because you can't send HTML files around without including their dependencies, and doing so might require manually editing all the links because the dependencies require going through multiple CDNs.

Every browser has its own independent format for saving an HTML page with dependencies making life fun if you want to send HTML around. Like maybe mock up a page or something.

Maybe PDF could be the universal format where instead of simply printing a web page to PDF and dealing with limitations, it could contain the webpage and dependencies and then be reflowable and scalable. (PDF did allow for reflowing of pages so you could choose to be pixel=perfect or reflowed to suit your screen). It could also allow you to previous your web page on multiple devices without needing a staging server.

Javascript on PDF has a use - for fillable forms it does a verification or provides a helpful way to do things. Like it could verify your phone number is in the form-accepted format, or let you use a date picker instead of manually entering a date.

It's sort of a universal viewing format - where you could print it out, or you can view the content in an enhanced way. Perhaps your 3D CAD drawing is an example where having someone be able to zoom in and out, or rotate the part around or even pick off dimensions. Without having to have a copy of the CAD program

You can get permanent residence easily, this gives you access to the all-important Chinese ID card and all the rights of residents. Including an ability to register a business. Naturalization is possible and technically you don't need anything special for it, but it's exceedingly rare. You also need to renounce your other citizenship(s) for that.

China is now becoming a popular emigration destination for Russian scientists. It's now very hard for them to emigrate to Europe/US, but China is easy. It's also helpful if the emigrants still want to visit Russia from time to time.

I'm not moving to a communist country.

The idea of living in a totalitarian shit-hole infested by a national surveillance network, people being taken in the middle of the night by masked and unidentified government agents, having protestors shot in the streets and generally living under the thumb of a dark and malevolent ruling class did make communism seem real bad.

Now it sounds like Trump's America.

Such as high-resolution image editing and high-definition video editing. Compared to a web browser, these aren't quite as amenable to splitting an application into numerous "content processes," each with their own separate 2 GB RAM.

For a while, Linux supported an x86-64 ABI called "x32" that limits each process's address space to 2 GB so that more pointers will fit in the processor's data cache. It didn't become popular, in part because of a need to load three versions of the system libraries: 32-bit i686, x86-64, and "x32". In addition, porting x86-64 applications to use less pointer-heavy containers gave most of the cache advantage that "x32" would have provided. This includes switching from linked lists to gap buffers (or other dynamic arrays), from B-trees to T-trees, or from pointers to indices in a pool. Rust in particular has encouraged use of appropriately sized indices as a workaround for the borrow checker.

There's a widespread misconception that a 32-bit operating system is limited to 3 GB of physical RAM. I think this comes from Microsoft's practice of requiring drivers for 32-bit Windows Server to support PAE as a condition for certification, but not drivers for 32-bit Windows desktop. I seem to remember 32-bit desktop Linux being more PAE-friendly. PAE and content processes are how Firefox for 32-bit Linux managed to hang on this long.

Yeah, but you see, from marketing perspective what sounds better? The Line or the Dot or the Pimple?
They had these 3 choices, they made the more sensible one even though it has nothing to do with a good or sensible city outline.

Woke is being aware of the racism and xenophobia that cause abuse by police/government in many places around the USA. You have to be really clueless to not be aware that there is a "crime" called "driving while black", or "driving while latino", or really, just being alive and out in public if someone isn't white. Seriously, that's still a major problem across much of "The South" and Midwest.

No one should be blind to what is going on, people are "awake" when they realize what is going on around them, even if they don't act on that awareness. The same thing with LGBT+, even if you don't like it, trying to suggest that people who don't share YOUR tastes shouldn't get the same rights that you have is wrong.

Which is to be commended, but also... The US started from one of the worst positions too. The the absolute worst, but certainly the worst of all the major economies.

Each function could be loaded the first time the user uses it. The device has to be online to query what is in stock at any given moment anyway. And I'd be interested in others' speculation about why the client side of the most widely used functions can't all fit in (say) 5 MB, which is twice the size of Doom.

I accept that, adding a clarification that I suggested the solution for the purpose of asking other people what these companies might know that I don't.

If they were cheating by any significant amount, we would know because emissions are visible from space. This article has an image showing how emissions can be traced to individual sources, even: https://theconversation.com/tr...

Satellites can also see reduced smog over China.

We can also see the massive solar and wind installations from space, or you can just get a visa and go look at them for yourself. Plenty of people have. Take a PM2.5 and CO2 monitor with you, for good measure.