221–230 of 529 posts
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
Earlier quoted context omitted.
>it's an example of malicious compliance So how would you do ePrivacy Directive compliance/risk avoidance in a non-obnoxious way?
Don’t use a bunch of unnecessary tracking cookies? Completely eliminates the need for a cookie permission bar.
This feels about 2 - 5 years out of date now. There isn't enough dark theme with slop-neon accents.
I should modernize this?
Should load much slower. Also, where is the unrelated autoplaying video that will unmute if you actually click it, that follows your scrolling and only becomes smaller when you dismiss it? Plus, it should probably have text that cuts off letting you know you can have access for just $10/month. Plus, isn't this website undissmissably "better in the app" after a few minutes of attempting to use it on a phone? Where's t…
Earlier quoted context omitted.
"No." If every webdev who would say no can be trivially replaced by webdevs who won't say no, then yes, it is webdevs.
"Damn, I'm being asked to put a cookie into this site that will maybe result in some guy seeing an ad about a toothpaste he might buy at some point in the future. I'm going to risk months of unemployment and explain to my family why this is more important than eating when I get home. The internet is serious business, they'll understand." -- the hypothetical webdev in that scenario, I guess?
Should load much slower. Also, where is the unrelated autoplaying video that will unmute if you actually click it, that follows your scrolling and only becomes smaller when you dismiss it? Plus, it should probably have text that cuts off letting you know you can have access for just $10/month. Plus, isn't this website undissmissably "better in the app" after a few minutes of attempting to use it on a phone? Where's t…
Earlier quoted context omitted.
"Damn, I'm being asked to put a cookie into this site that will maybe result in some guy seeing an ad about a toothpaste he might buy at some point in the future. I'm going to risk months of unemployment and explain to my family why this is more important than eating when I get home. The internet is serious business, they'll understand." -- the hypothetical webdev in that scenario, I guess?
If you can get replaced over something so minor, it means there's dozens of capable bootlickers lined up and ready to do it as soon as you're gone, so yes, there is a webdev problem.
Mate, it's just a cookie on a site.