Ok, there are no numbers from 2024 yet in the source.

I think the solar capacity in 2023 for China was 525GW.

So a 277 GW increase in solar means it increased by (277 / 525) 52.76% (that’s great!)

That same percentage increase over the current value in terms of production would not make it rise past Australia per capita yet, but nobody can deny that’s an impressive pace.

Also, considering that the trend in population numbers for China is slowly inverting, that could also contribute to an increase in the per capita numbers in the future.

Doesn’t that table show Australia has double the consumption? also that consumption number is in total primary energy, regardless if the energy comes from solar or not.

I believe that to see how much of the TPES for each country comes from solar we would need to divide the solar production per capita by the total consumption per capita:

- Australia: 1774 kWh / 63257 kWh = 2.80%
- China:      410 kWh / 33267 kWh = 1.23%

Sources: the 2023 numbers from his link, and the 2023 numbers from the source in your wikipedia link.

The article is talking about storage space, not about access to files in any particular filesystem.

Previous versions of Android 15 Terminal app only allowed 16GB of space to be used by the guest system. The article mentions it.

So even if you had 128GB in your phone, previously you could only use 16GB of them in the environment Google set up for the Linux Terminal subsystem, which made it very limiting. What the article says is that now they are removing that limitation.

True, but then you have bigger problems than just the journal.

Then simply write it in a text editor without saving it into a file, it’ll be lost after closing the program.

Can you point to a specific law that the EU has passed in this direction?

Cos according to the article all attempts to pass something like this that have been presented in the EU have been blocked. By the EU.

An alternative title could have been: “EU Possibly The Only One Who Has Been Explicitly Rejecting Backdoor Mandates Until Now”

Sure, proposals keep being presented… but I feel it’s kind of a bit early to call the EU “greatest threat” just because yet another attempt has been made. Specially when you compare it with many other places where they apply things like this without batting an eye.

I’m not saying we (Europeans) shouldn’t push (yet again) to make sure this also fails… but the title of the article is a bit misplaced, and after a history of successful rejections I feel a lot more optimistic.

This. I’m moving to a place where I cannot use ethernet cable and I was looking for a good Wifi 7 router. Most big brands are at around the same price.

It’s just unfortunate that I need it now and not on late 2025… I might just rent a Wifi 6 one from my ISP and wait for the OpenWrt 2.

interoperability == API standardization == API homogeneity

standardization != monopolization

Yes, but the loophole I was mentioning allows companies to not release the code even when it’s GPL, that’s why I was mentioning the AGPL (which is different from the LGPL).

I think many hobby developers also see “hobby” developing as part of their career, so they would happily try and have their hobby align with future employment possibilities. Since companies avoid GPL, those devs will rather choose a license that is more attractive to those potential employers when they see their portfolio.

Thunar is a much better alternative, in my opinion.

To me, the problem is not really so much about “locking people in” (it’s also unclear what you mean by that, if they were already using that ecosystem before using uutils aren’t they already locked in?)

To me, the problem is how the MIT removes legal protections when it comes to ensuring accountability to changes in the source… how can I be sure that the version of uutils shipped with “X Corp OS” has not had some special sauce added-in for increased tracking, AI magic, backdoor or “security” reasons? They are perfectly free to make changes without any public audit or having to tell their users what their own machine is doing anymore.

If you are using a GPL library that is statically linked to code with a different license the result is one binary that has inside both GPL and other license code, which would not be allowed under the GPL terms, because it requires that the binaries that use the source code must have their source code available in full (including other source and modifications that are part of the same binary).

The only case in which you don’t need to provide the source for GPL software is if you don’t actually distribute the binary to customers… private binaries do not have to be published with their source, as long as you never made the binaries public and never gave it to anyone else. Only when you give it to someone you need to provide the code.

This allows for a loophole in which if you are providing a service, then you can run the software privately in your private server without sharing the source code to the clients using the service, since they do not really run the server program although they indirectly benefit from its results. This is why the AGPL was created, since it has a clause to force also those offering services to make the source of the server available to the users of the service.

Yes. Did I deny that?

Can anyone confirm or deny if what I said is wrong?

I get downvoted for stating one advantage an AGPL fork would have, and yet nobody seems to be disagreeing with what I said… *shrugs* 🤷

But, whichever command I put in autostart.sh will run as if I run in terminal with the & sign. E.g: dunst & to run in the background.

Well, only if it’s one single command, if you have multiple commands inside of the script, they will still run sequentially (the next command will only run after the previous one completely closes) unless you add & to them as well.

The difference is that dwm itself will not have to wait for the autostart.sh to complete before launching itself (thanks to it being run in the background with &)

However, autostart_blocking.sh (which isn’t run with a &) will stop dwm from fully launching until the script completes… I guess this is useful if you need certain things to be set up before dwm actually starts… but it would potentially add a delay on dwm startup.

Personally, I don’t think the problem is the risk of companies not contributing back… I honestly wouldn’t mind if they don’t contribute at all and instead they just use the community-developed GPL software as-is, without making any changes to it.

In my mind, the problem is that I cannot trust that a piece of non-copyleft software that’s provided by a company actually does what I expect it should do, and does not have extra bits doing things I do not want it to do. Like the changes Google does in their Chrome version of Chromium, for example. It’s much harder for me to trust any random Chromium fork than it would be a GPL licensed browser, because all Chromium forks can legally include changes without disclosing them openly, they don’t even have to let you know if the binary actually matches the code.

If, for example, MacOS / Microsoft Windows include a copy of OpenSSL with the OS, how can I be sure they are not adding their own sort of malicious spice into it? Can I trust that the keys generated with it will be truly secure? How can I audit it?

At least with the GPL there’s some level of legal accountability in that any change that is not openly shared would be illegal. But with MIT there are no legal barriers against malicious code, it’s totally legal for companies to force feed me totally legal changes that I wouldn’t want and/or that I might not even notice they are there.

developers should be able to license code that they write under whatever license they like

What if they choose a license that limits the freedom from all other developers to improve that copy of the software? is allowing a developer to restrict further development actually good for the freedom of the developers? Because I would say no.

The spirit of the GPL is to give freedom to the developers and hackers (in the good sense of hacker). The chorus of the Free Software Song by Stallman is “you’ll be free hackers, you’ll be free”.

the GPL restricts freedom without adding any that MIT does not also provide

“Your freedom ends when the freedom of others begins”

The only “freedom” the GPL restricts is the freedom to limit the freedom of other developers/hackers that want to edit the software you distribute. This is in the same spirit as having laws against slavery that restrict the “freedom” of people to take slaves.

Would a society that allows oppression (that has no laws against it) be more “free” than a society that does not allow oppression (with laws to guarantee the freedom of others is respected)?

It doesn’t even say “you should use the GPL”

That sounds a lot more confrontational and less diplomatic.

The ticket was actually indirectly asking it, by explaining the potential problems with non-copyleft. They just added “If you plan to carry on…” to introduce a compromise, which actually allowed for at least some minor change to be made, and made it clear that the different license is intentional and not just for lack of awareness (which would imply the devs have no intention on switching).

it says “you MUST say GNU doesn’t agree with you”

Somehow you added the “MUST” to this sentence, but not to the first one… even though the github issue did not say they MUST, instead it even used the word “please” and appealed to having some deference to the GNU coreutils.

At least this issue managed to get a change through for clarity… I don’t think you would have gotten anything at all with the other approach.

Note that AGPL can take changes from MIT but MIT can’t take changes that are purely AGPL without following the AGPL.

So, as far as I can understand, any improvements done to the AGPL version cannot be carried over to the MIT version (without very painful and careful re-implementation / re-engineering). That alone would be a big advantage to the hypothetical AGPL fork.

It would be a bit of a legal nightmare, since it’s theoretically possible that, even without really knowing it, the same feature might be implemented the same way in both forks separately, and the MIT devs might have no sure way to prove they did not copy it. So this would be like walking on eggshells for them.

Thanks. I wasn’t planning to go there anyway…

It’s annoying how the title throws such a general open question and then they don’t clarify this at all… there isn’t even a single match for “USA” or “America” in the whole article, you have to sort of guess.