Or meson is a serious alternative to cmake (Even better than cmake imho)

If the GDPR is simplified, the fines should be drastically raised. (At least for companies) E.g. to minimum 20% of the global last years revenue, for bigger companies (FAANG-Scale) to minimum 70% of the revenue. The GDPR must make companies afraid of breaking the law.

(looking at the DMA act) they know, they know.

The biggest symbol of a statically linked swift binary that I have, is icudt_swift65_dat with 27.98MB, so I think that's not so easy to remove (nm v3.1.2 --size-sort --radix=d|swift demangle) And I think if you strip debuginfo it will be smaller (For a statically linked program of mine: 98MB -> 56MB)

But I think for a distribution it makes more sense to link swift programs dynamically against the runtime libraries, like it's the case for e.g. the C standard library, OpenSSL etc., as you can assume they all work with the same version and are ABI-compatible.

I tested it with a nearly static build (Still links against glibc and friends): 55MB get stripped to 44MB, so not that much. 27MB of that is icudt_swift65_dat, so I guess you would have to optimise that first

With the new Foundation work going on, when you migrate to that, if you don't import `FoundationInternationalization` then you won't pull in all of ICU and it won't be bundled in

If I’m not mistaken, the embedded swift mode aims to make ICU (the 27mb file for Unicode support) optional (and thus easily removed where it isn’t needed)

One is a business decision, the other one is people exercising their rights.

People don't have rights over others private property that's the of the basis of human rights.

The company control their private property. The labour can only control their own labour, so they choose to use that control. How is that not in their right?

I totally agree, they all have the right to not work there, but they don't really have a right to prevent others from delivering packages to a building.

Nobody is preventing that. Other workers _voluntarily_ refuse to provide their services to Tesla.

Yes, but people still have the right to say "Pay us $X and ensure safe working conditions or we strike" Tesla can either withdraw or negotiate. Nobody's right is infringed here, it's just free market. Especially as usually the workers have it worse than companies.

> People don't have rights over others private property

Have the workers looted Tesla's plants? Are they burning down Tesla cars in transit?

No?

Then fuck off. Workers are simply negotiating for a fair price for THEIR private property - the labor services that they provide.

You can do that with m3u8 files. This is done for example by Pluto TV. Sure it is easily circumvented by simply stripping out these URLs, especially if they are marked as ads (And removing a m3u8 tag)

But in the end it would be again an arms race of adblockers and Google, so it would change basically nothing.

Wouldn't even be checking Microsoft's server be an unnecessary connection? You could argue, that VSCode would still work, as updates are basically optional and could be triggered manually, too

Yes, I meant connecting to update/install in response to a user action that wants to install extension for "X functionality".

It's easy to install on ArchLinux and Fedora. The build process seems to be just standard CMake, so calling it "borderline impossible" is really a stretch.

A lot of editors have available integrations for Shellcheck. VSCode and IntelliJ have a plugin, GNOME Builder comes with the plugin included, etc.

This really makes me reconsider buying an iPhone instead of some android phone in the future.

The only thing left is that jail-breaking an iPhone seems to be harder than rooting an android phone.

It's just a liability and risk. Imagine you have some mission-critical system written in such language, the vendor goes bankrupt or creates absolutely unacceptable terms. Then you have a problem.

Sure if something similar happened to an open-source project, you would still have to either hire engineers to work on the compiler/tooling/language or to rewrite it in a more supported language, but I would consider it a little less riskier as you aren't dependent on one vendor