In my opinion it is unclear what you are referring to because many people have different views on what the term piracy actually means.
In my opinion it is unclear what you are referring to because many people have different views on what the term piracy actually means.
Edit: another commenter mentioned something about treaties needing to go through the EU parliament and council if the areas of concern aren’t delegated to the EU. Not sure which side of the fence this falls under, and I bet there are some potential legal challenges waiting regardless. So perhaps France is hedging its bets by signing on as an individual nation, indicating its willingness to implement the treaty no matter what happens with the rest of the EU. But I am no expert on EU bureaucracy and politics!
That depends on the topic of the treaty.
The EU member countries have delegated their decision making powers on certain limited number of topics to the EU institutions, like The EU Commission, The EU Council or possibly others. One such topic is the trade. As a result, all EU countries share the same trade policy.
For other topics, where there is no such delegation in place, everything needs to be ratified by every member country individually.
I am unsure into which category this particular treaty falls.
The only valid agreements require the party seeking the agreement to make efforts in that pursuit. Did a human view the signed agreement afterward? Do they store that signed agreement in such a way as to be able to retrieve it if they need to contest the terms later?
Then no agreement was made.
And as for the CFAA provisions, if they put those resources on the public internet, then the public has the right to interact with them. You can't fence off the sidewalk and claim that someone trespasses when they walk on it.
Perhaps a better analogy would be:
If you go out into a public space, you have to accept that by doing so you lose a certain portion of your privacy. You cannot expect that other people will agree to your "terms and conditions" before being allowed to talk to you. They will just talk to you if they so like.
I do not understand how such a requirement would be legally enforceable for public endpoints.
> There is no support for power-efficient sleep
"power-efficient sleep" refers to discharging 1-2% battery over night rather than 10-20%. I.e. there's room for improvement, but the device can still be used without worrying much about battery life regardless (especially given how far a full charge gets you even without sleep).
> Display Port, Thunderbolt
Big item indeed, but it's actively worked on and getting there (as you mentioned).
> video decoding or encoding
Hurts battery performance, but otherwise I never noticed any other effect. YMMV for 4K content.
> touch ID
Annoying indeed, and no one has worked on this AFAIK.
> The speakers overheat and turn off momentarily when playing loud for a longer period of time. The audio stack in general had to be built from ground up and it seems to me like there are bits and pieces still missing or configured sub-optimally.
Sad to hear since I thought the audio heat model was robust enough to handle all supported devices. On my M1 Air I've never seen anything like this, but perhaps devices with more powerful speakers are more prone to it?
My experience is also based on a M1 Macbook Air. I have repeatedly experienced sudden muting of the speakers for a second or two while playing conversations on a high volume.
I only assume it is caused by thermal management of the speakers but I did not actually verify it.
The argument was originally about merging some Rust code into some parts of the Linux kernel if I remember correctly. It did not involve Linus Torvalds directly. Rather, the respective maintainers of those specific parts were unwilling to merge some Rust code, mostly because they did not know Rust well and they did not want to acquire the responsibility to maintain such code.
Much less active than it used to be when it was run by Hector Martin. The core development is a lot slower. Although the graphics stack, for instance, has reached a very mature state recently.
> Is it ready as a daily driver?
It depends. Only M1 and M2 devices are reasonably well-supported. There is no support for power-efficient sleep, Display Port, Thunderbolt, video decoding or encoding, touch ID. The speakers overheat and turn off momentarily when playing loud for a longer period of time. The audio stack in general had to be built from ground up and it seems to me like there are bits and pieces still missing or configured sub-optimally.
> Is it getting support from Apple?
Not that I am aware of.
> are they (Apple) hostile to it?
Not to my knowledge.
> Are there missing features?
Plenty, as described above. There has been some work done recently on Thunderbolt / Display Port. Quite a few other features are listed as WIP on their feature support page.
> Can I run KDE on it?
Of course. KDE Plasma on Fedora is Asahi Linux's "flagship" desktop environment.
So carrier can choose to whitelist/blacklist phones depending on extensions available
That would be, I believe, fine. Those are capabilities-based restrictions.
From my point of view, the issue would be if the same phone worked with the same technology over the same mobile network when connected via a carrier A but the same phone on the same network refused to work with the same technology when connected via a carrier B.
It should work based on standards, mobile carrier's capabilities and phone's capabilities. If a phone supports capability X, such as VoLTE, then it should just work with all mobile carriers that support that capability. No conditions.
As an imperfect analogy, consider a road, representing a mobile network. This road has some capabilities, such as speed limit. There are cars driving on this road, representing mobile phones. And then consider that a road management company, representing the carrier, would impose different speed limits on different cars, depending on whether they are affiliated with the road management company or not.
Would that be acceptable in a physical world?
If not, we should not accept anything similar in a digital world either.
If you treat it like a rubber duck it’s magic
If you think the rubber duck is going to think for you then you shouldn’t even start with them.
That is an interesting metric but I think it is not that important.
I would be careful with (AI-generated) code that no one at the team understands well. If that kind of code is put into production, it might become a source of dragging technical debt that no one is able to properly address.
In my opinion, putting AI-generated code to production is okay, as long it has been reviewed and there is a human who can understand it well, debug it and fix it if needed.
Or, alternatively, if it is a throwaway code that does not need to be understood well and no one cares about its quality or maintainability because it would not need to be maintained in the first place.