I mean if you write malware "for a good cause" plenty of people will rightfully judge you for subverting their expectations, and the reasoning doesn't matter thst much. And it's not like they're completely in the wrong either.
amju_wolf
...but do yoz "understand libraries" by reading every line of their code, or by reading the documentation? And only in the parts you're actually interested in?
Yeah, and I'm never going to use it, just like I don't use any of the other existing fields - it doesn't matter.
No; I think these bills are terrible and should be resisted. But the outrage about (what is effectively) a database on your pc to store information that itself doesn't do anything is ridiculous.
If abyone wants or needs to implement a system like that (could be for work,for example), that's perfectly fine. What isn't fine is the existence of the laws in the first place, and they shouldn't be resisted with (just) technology.
I could imagine a parental control setup using this information, for example. Linux is really behind in this regard and it's time it started catching up IMO.
There are even open source tools that do the same thing.
Also, yeah, if something solves a problem, it can be worth it to pay for it even if it's proprietary.
There are genuinely useful use cases for it, and unlike what you suggest it is completely harmless.
I don't think you understand.
If you spoof your resolution and window size to the degree that it's undetectable you effectively have to render it in that resolution.
Guess how websites make it so that they work on any resolution? They use relative units and whatnot that make it work that way, and all that is detectable one way or another. So you'd have to spoof it all in order to resist fingerprinting - and that is either going to break the rendering, or it's going to effectively render that website at that resolution, making it a bad experience for regular users either way.
I do wish this was an option for more "normal" browsers, and that they resisted fingerprinting better in some other ways, but you have to make serious compromises to make it work fully.
Soooo you're not actually arguing for cURL but for bash scripts and potentially something else.
And now you come across all the issues that come with that, like portability, the inevitable messiness of Bash (and the fact that people actually need to learn it unlike a GUI tool that uses simple JS for scripting), and you lose all the convenience of a nice UX and stuff like validation that comes with it.
In other words your argument is about as valid as people who argue that vim is the peak of IDEs and noone ever needs anything else. Which - I really hope - you realize is a bit crazy.
Commissions are perfectly fine as long as they're upfront about the price and it's not percentage based. Then you basically just pay for a service / someone's time.
And title.search is a problem with the government... Civilized countries have national registries of who exactlx owns what, and in the best ones you can freely look it up online, too.
That does not really work for DX... Or collaboration. Or testing. Or documentation.

It can still be pretty difficult to jump ship for any large corporation, but yeah there's certainly harder things.