deno is refreshing, but i don't like the fact that it is married with typescript and has built-in support for this and that library. should've been framework agnostic from the start and not marketed as this batteries-included thing.
also, this creates more fragmentation in the node/web community which i don't really see the need for. being compatible with node/npm just carries with it the warts and problems instead of getting rid of them.
Those popups are not only necessary for cookies but for any kind of tracking that requires consent, e.g. all tracking for purposes of advertisements. So if you do browser fingerprinting instead of setting cookies, you still need that popup.
For using FloC data, if the granularity is sufficiently coarse so that a person cannot be identified by it and no specially protected groups can be identified (i.e. sexual orientation, religion, minors, etc.), then presumably using FloC data won't need that popup. But that remains to be seen, I guess it will take a few years of discussions in court until this is settled.
Same site cookies aren't going anywhere for the foreseeable future, the vast majority of user session capability is built on the existence of cookies. 3rd party cookies only affect embedding of sites hosted on other domains, (mainly ads), which don't use cookies for user sessions but user tracking... or to use the ad industries euphemism "personalisation"
A solution that works in every browser and gives the user choice is hardly nonsense (also cookie law != GDPR). It's much, much better than a dominant ad company forcing through a solution that works in their browser and which users presumably can't opt out of.
ah, the old web vs java discussion. "why does the browser not come with all the components i want built-in, having the exact look n feel that my OS has?". "i have to actually write code to get a popup?". "markup language? style sheets?? bollocks!". "surely, java is more mature and will enable me to make better apps, in less time". "it's running on a JVM, didn't you know?". "so it's more performant".
ok. js css html won the web platform. and they have an increasing piece of native. oops! this is not a random trend, but for a good reason.
java for GUIs is not going to be popular again. it's already been tested and it failed the test.
the old timer java mindset still wants the web but it does not want to learn web.
working with the web is not a "hack", nor is the DOM only suitable for representing "documents". you left in 1995 and failed to catch up with modern standards. it's a flexible system, but does not come with all the batteries. but to counterweigh that it has a massive ecosystem, a package manager with plenty of off the shelf parts, if you want them. performancewise, the browser engines are getting faster and faster every day, optimised for rendering. v8 is hugely successful natively. the DOM is very suitable as a generic GUI model to work with. back in 1995 it was not.
wake up Java devs. your arguments are getting increasingly flaky..
but, there is no harm in getting an extra b12 dose for meat consumers as well! plant-based milks are not meant only for plant-eaters (to put it simply) they are of course meant for everyone
