It's just a different way of looking at primary storage. Object memory is an even finer grain version of the old idea, and it offers some security advantages that linear memory cannot.

Yes, but half the people have below-average intelligence.

We won't have a stable society if they're constantly scammed.

And I know some High-IQ people with no street smarts who got scammed by "Raj from Microsoft Support".

Really some dude from a trailer park might have a better BS detector, having lived a less coddled existence.

That, or your project gets sidelined. Which is where the danger lies.

I work for a big multinational software company that uses a lot of Open Source Software. We have a security office that audits all of our products several times a year. If any piece of our stack shows any open CVEs we have a fixed amount of time to fix the issue, with the amount of time varying from a few days (for CRITICAL severity issues) to roughly half a year for the lowest severity issues. A lack of a fix for a published CVE isn’t an excuse for not fixing the issue on our end — the software still has a security flaw in it, and the organization is so incredible security averse (thanks in part to having contacts in the defence industry) that they don’t want to risk expensive lawsuits and the loss of reputation if a vulnerability is exploited.

A lot of bigger organizations now work this way. We’ve all seen what has happened to organizations that have had significantly security breaches, and it’s not pretty. Our customers are big corporations and government entities — and if they even sniff a risk there are going to be problems. So if there is an unpatched exploit, we’re expected to either switch to something comparable, or DIY a solution (either replacing the library in question, or potentially patching it ourselves).

If ffmpeg allows known and published vulnerabilities to languish, the risk here is that organizations that use their code will simply stop using it and will look for other solutions. That’s a tough pill for an Open Source Software developer to swallow, especially when they make it as big and important as ffmpeg. You might wind up in a situation where an entity like Google forks your code and takes ownership, and eventually gets everyone to migrate to using their version instead (like what they did with WebKit to Chrome), leaving you sidelines. Or maybe someone else jumps in with a compatible solution that works well enough for enough users that they switch to that instead.

Now in an ideal world, the Google’s of this world would not only submit a CVE but would also submit a patch. Having been an OSS developer myself I’ve always encouraged my staff if they find a bug in a piece of software we use to file a bug report and ideally a patch if they know how to patch the issue correctly — but I know that is hardly universal within our organization, and probably even less so elsewhere.

TL;DR: a lot of OSS success relies on having lots of users, or at least some big and important users. But you risk losing those if you leave CVE’s open for too long, as company policies may require scrapping software with unfixed CVEs. That loss of users and reputation is dangerous for an OSS project — it’s how projects get supplanted, either by a fork or by a new (and similar) project.

Yaz

Over the years I have used as my main development machine:

* 2011 17" Macbook Pro with 8GB RAM
* 2016 iMac with 8 cores and 32GB RAM (with 2 additional 4K screens)
* M3 Max 14" Macbook Pro with 36GB RAM (and an additional 4K screen)
* M4 Max 16" Macbook Pro with 48GB RAM (and an Apple Studio screen)

I havent really ever run into a resource issue - I had to retire the iMac just last month because the screen was ghosting, but it was still perfectly usable for development purposes right up to that point (ie I never get frustrated with it in terms of performance). The M4 Max MBP tho is worlds ahead of it in performance, so I dont regret upgrading - I just didn't upgrade for performance reasons).

The filter that was working no longer does

There is no reason why applications which choose to implement both types of interfaces can't do so. There's also no reason why users should be limited to one type of interface or the other. Both things coexist completely peacefully on Android. You can connect a mouse to your tablet (or even phone) and treat it like a desktop system with shitty storage (practically all phones, it takes a lot of power to have fast storage.)

The primary use case for tablet computers in olden times was data entry and acquisition, for example the military used their magnesium-case gridpads to do inventory.

I have used Jetbrains Rider now for the past 7 years and I can definitely recommend it (and I pay for it as well). I switched because I moved to Mac for .Net development, and really hated Microsofts .Net story for VSCode - and since switching to Rider, I haven't found myself wanting Visual Studio at all.

Slashdot has progressively got shitter over the past decade, and its noticable that that also correlates to a decline in the number of comments being left on stories.... The community has shrunk.

Slashdot used to allow me to give them money to avoid ads, but they took that away - so I have no moral or ethical issue with blocking ads on this site. Especially as they also used to provide an option to hide ads for long term users - which they started to ignore for specific ads, and then got rid of entirely.

> It's impolite to ignore robots.txt, but it's not illegal.

Put something fake in your robots.txt and block the IP that accesses the fake URL.

AI people: "oh, that's where all the good stuff is!"

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.

But thats the entire point - at that point you arent scratching your own itch, you are voluntarily scratching someone elses.

If people stuck to scratching their own itches, we would either have fewer large projects or more involvement from users who are scratching their own itches.

But in the meantime, many OSS projects exist on the following flow:

1. Scratch your own itch, and make the solution public because it might help out others
2. Someone else finds your scratching to be valuable to them, so uses your solution
3. You like being involved with something someone else finds valuable, so you start scratching more of other peoples itches to increase your solutions value
4. Growth
5. You complain that other people are having their itches scratched without helping out

All of that is voluntary, and you put yourself in that situation - but you end up blaming others because thats easier than accepting that you made your own situation.

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.

Not like they arrest anyone in the country legally and for "reasons" luckily he was released after 73 days. Imagine the mayhem this hospital chaplain could have done! https://ohiocapitaljournal.com...

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.