I don't think punishments should be decided relative to social media anecdotes. If there's some area of the country where local police routinely show up in assemblies or other gatherings and arrest people for driving past school busses, I support reforming their laws; in my local jurisdiction it's a traffic violation and police don't do that.
But you can not disable predictive button resizing.
Predictive text replacements are very bad, but they mitigate the worse issue of the fact that the keyboard is incessantly shifting with every single keypress.
Harper Lee's novel To Kill a Mockingbird is a creative writing exercise which didn't actually happen and isn't verifiably true to any degree. There were never any Finches, Ewells, Robinsons or Radleys, yet readers often find it quite powerful because they're perfectly aware the story's events have played out between real people many, many times. They don't need to be told the real names of people who have been in lynch mobs to know real people have been lynched.
Email servers aren't quite as heavy a subject, but we know these things happen.
The truth is not a defense against libel laws in all countries. Depending on where this is the poster could be out a lot of money just for naming names. As such not naming names is the safe answer.
Even in the US where the truth is a defense, you still can be out a lot of lawyer fees because you can be sued for things you say and it can cost a lot of hours in court.
The author is located in Italy, where "it's the truth" is not an absolute defense against defamation like you say - basically, here, causing "reputational harm" is actually against the law, even if you are telling the truth. There are a few exceptions like social interest which may apply, but it is a dangerous game to play because you need to prove that to the courts, as opposed to just proving what you wrote is what actually happened.
Plus, any court proceedings in Italy can routinely take decades, destroying one's life even if they are completely innocent, even if the complaint is trivial, even if the complainant is obviously malicious.
In the USA it used to be very rare for companies to directly mention competitors in ads. Products would be compared to "Brand X" or some other genericized name instead.
I think it still is somwhat rare. Why even let a potential customer know that a competitor exists?
a company with a history of threatening baseless lawsuits, combined with possible NDAs, or possible professional backlash when lawsuit-happy company threatens former employer. not worth it for a blog post.
Moral of the story is that going to open-source is only part of avoiding the traps that vendors set. You also have to trust the vendor you're working with and make sure that the contract isn't full of lawyer tricks.
Naming names is exactly what prevents a witch hunt. By keeping it vague, everyone here is wondering which company this is and whether they're currently doing business with them.
Blink supports Windows, Android and Linux better than WebKit or Gecko does, to name at least one one reason. If it weren't for uBlock I'd probably be using a Chrome fork right now.
Google has already shown that they will slowly and methodically use every lever at their disposal to nerf ad blocking, regardless of what the user base thinks.
It's the exact same playbook Microsoft is using to block users from logging onto their own computer without using an online Microsoft account.
Given that Google has already started working to limit sideloading on Android, those days seem limited.
Blink is an open source project. If Google updates Chrome and Android to refuse sideloading at all, you can still fork both projects.
Your entire argument relies on a hypothetical you can't prove and doesn't scare anyone. To Android users you sound more like Chicken Little than the Boy who Cried Wolf.
Wipr and UserScripts on Safari prove to me that that's not a real issue...I understand compatibility problems are still issues, but ads/etc. are a fully solved one for Safari users.
For me it’s a lot of layout and rendering bugs that I run into with somewhat normal CSS transforms.
Anytime I build a site that has any kind of animation, there’s at least one weird rendering bug on iOS.
Also that stupid playsInline prop that if you forget it makes any video in the viewport hijack the browser and go fullscreen.
WebKit is not lacking in things your average dev needs and it’s not that big of a deal to work around, much like it’s not that big a deal to work around things in Gecko - or presumably Ladybird whenever it becomes usable enough.
This might work for you, but doing this to an untrained, unexpecting, or visiting Apple user on your LAN will make their Apple device experience 1,000x worse.
I run several PiHoles — for guests, DHCP issues the IP of the least-restrictive blacklist (which does allow Apple; just seven rules to block largest always-advertisers).
But also, I don't care about anybody's user experience on my home network, but my own =D
