This is not open source? There is no license just a statement saying free to use for personal and commercial projects, but don’t redistribute or resell.

This freeware at best but if you contribute to this project it’s not clear who owns the work.

A prediction for the 2024 US election

The metaverse a resounding failure, Facebook has latched on to the AI hype train in hopes of making the company relevant. They’re basically put of ideas on how to feed the beast of “forever growth” the markets demand.

I don’t have specific experience with the tools you list, however on googling it looks like Ableton Live does work under wine. Wine is what underpins playing windows games on Linux too; it’s very powerful and effective.

You can install Mint into a VM environment on your current PC (such as Virtual Box) and see how you get on with software you really can’t live without. It won’t run as fast as real life in a VM but you should get an idea whether any tools you can’t live without can work.

As for OneDrive there are unofficial clients to get it working with Linux if you want to sync to your local filesystem. However Microsoft doesn’t officially support it beyond Web browsers, so if you want something slick and supported you probably would be better migrating to other solutions. You’d certainly be able to migrate with the unofficial clients but I’m not sure I’d want to rely on them long term as things xna break if Microsoft unilaterally changes something.

There are PPAs with different builds of ffmpeg for Ubuntu. It also depends what codecs are needed as to whether this is even relevant?

Bearing in mind some (many) encoding codec libraries are not installed by default as most people don’t need them but can readily be added from the official repos via apt or synaotic. Each codec is usually provided as a library of its own; ffmpeg is more than just one set of binaries. There is a big difference between an incomplete build and incomplete default install of all available libraries/codecs. Most people don’t need or want every possible encoding codec installed by default.

However some codecs are more strictly licensed and may need to be installed or acquired via different routes - that is the nature or proprietary software (as on Windows).

Which codes are you saying are not available in Ubuntu official repos?

Quick FYI - Exa is no longer fully maintained; there is a fork called Eza which is maintained. They couldn’t take over the original Exa repo as the original creator is unreachable. Eza is in many distros; I’ve installed it on OpenSuSe Tumbleweed with ease from the factory-oss.

https://github.com/eza-community/eza

For the Flatpak apt upgrade how about “flapt”.

That’s rather simplifying history and not the main reason Netscape failed.

Netscape lost because Microsoft used it’s dominant monopoly position to bundle Internet Explorer with windows. By 1999 the writing was already on the wall - IE had already overtaken Netscape market share and was growing rapidly.

The Mozilla project and code base change was a gamble to try and fix the problems. When Microsoft released IE6 2001 they didn’t bother releasing another major version for 6 years as they were so dominant.

So while the code base change was arguably mishandled, at worst it accelerated the decline. Instead the whole story is a poster child for how monopoloes can be used to destroy competition. The anti trust actions in the US and EU came too late for Netscape.

Ironically Microsoft was the receiving end of the same treatment when Google started pushing Chrome via it’s own monopoly in search. They made a better product than the incumbent but they pushed it hard via their website that everyone uses.

Genuinely, nothing so far.

I’ve tinkered with it but I basically don’t trust it. For example I don’t trust it to summarise documents or articles accurately, every time I don’t trust it to perform a full and comprehensive search and I don’t trust it not to provide me false or inaccurate information.

LLMs have potential to be useful tools, but what’s been released is half baked and rushed to market as part of the current bubble.

Why would I use tools that inherently “hallucinate” - I. E. are error strewn? I don’t want to fact check the output of an LLM.

This is in many ways the same as not relying on Wikipedia for information. It’s a good quick summary but you have to take everything with a pinch of salt and go to primary sources. I’ve seen Wikipedia be wildly inaccurate about topics I know in depth, and I’ve seen AI do the same.

So pass until the quality goes up. I don’t see that happening in the near future as the focus seems to be monetisation, not fixing the broken products. Sure, I’ll tinker occasionally and see how it’s getting on but this stuff is basically not fit for purpose yet.

As the saying goes, all that glitters is not gold. AI is superficially impressive but once you scratch the surface and have to actually rely on it then it’s just not fit for purpose beyond a curio for me.

Flatpak is supposed to be a sandbox, so if there is a vulnerable dependency then in theory any attack would be limited to the sandbox.

However, it depends on the software - some Flatpak need quite low level access to use, and in that case an attack or mlaware could get into the main system. And unfortunately Flatpak itself has vulnerabilities which cna negate the whole idea of a sandbox.

Flatpaks should be using up to date secure dependencies, but the reality is many do not. I would not rely on Flatpak for security. Even fully up to date Flatpaks can be insecure, and Flatpak itself have vulnerabilities that have needed fixing. And for many Flatpaks it’s not even clear who is maintaining them.

Flatpaks are useful for deploying software that’s just not available in your distros repos. But when deploying any software outside your repos - including App Image, build from source or 3rd party repos - you are opening your system up to security vulnerabilities. That’s the nature of installing 3rd party software. Flatpak offers some reassurance compared to some methods but it’s far from perfect.

If security is your prime concern, then Virtual Machines may be more secure route to sandboxing software (if done properly). Building from source would be the other option, as it means you take ont he responsibility for security by using the latest code including for dependencies. But there is no perfect option, it’s always about balancing risk vs convenience.

It’s also worth noting that software repos are also not perfect. But good distros invest a lot of time and effort in keeping them as up to date and secure as possible, usually via the hard work of volunteers.

This is badly written and ignorant article. Fat32 supports up to 16Tb partition size (depending on cluster size - 2Tb -16Tb).

Its microsoft’s windows tools that arbitrarily only allow users to create 32Gb partitions, and it is this that is being changed. This is not a change to Fat32, this is a change to windows. 3rd party tools on Windows and other systems like Linux have long offered more options for partition size.

That its taken to 2024 for Microsoft to fix the command line tool (and still not fix the GUI tools) is ridiculous.