I blame the prevalence of package mangers in the first place. Never liked em, just for this reason. Things were fine before they became mainstream. Another annoying reason is package files that are set to grab the latest version, randomly breaking your environment. This isn't just npm of course, I hate them all equally.
> As in, things were fine before we had commonplace tooling to fetch third party software?
In some ways they were. I remember how much friction it was to take a dependency in your typical desktop C++ or Delphi app in late 90s - early 00s. And because of that, developers would generally be hesitant to add a new dependency without a strong justification, especially so any kind of dependency that comes with its own large dependency tree. Which, in turn, creates incentives for library authors to create fairly large, framework-style libraries. So you end up with an ecosystem where dependencies are much more coarse and there are fewer of them, so dependency graphs are shallow. Whether this is an advantage or a disadvantage in its own right can be debated, but it's definitely less susceptible to this kind of attack because updating dependencies in such a system is also much more involved; it's not something that you do with a single `npm install`.
I mostly share GP's sentiment, although they didn't argue their point very well.
> As in, things were fine before we had commonplace tooling to fetch third party software?
Yes. The languages without a dominant package manager (basically C and C++) are the only ones that have self-contained libraries, that you can just drag into your source tree.
This is how you write good libraries - as can be seen by the fact that for many problems, there's a powerful C (or C++, but usually C) library with minimal (and usually optional) dependencies, that is the de-facto standard, and has bindings for most other languages. Think SDL, ffmpeg, libcurl, zlib, libpng/jpeg, FreeType, OpenSSL, etc, etc.
That's not the case for libraries written in JS, Python, or even other compiled languages like Go and Rust - libraries written in those languages come with a dependency tree, and are never ported to other languages.
While visiting a friend in Russia I was perplexed by the candle in his flat - it had zero flicker, was stable and unmoving. Eventually I learned how they heated the flat, with water flowing through pipes and heat radiation - so little to no air movement.
No, central heating + radiators are somewhat region specific. For example Australia runs almost entirely on split system reverse aircons and electric heaters.
In northern North America forced-air natural gas is pretty for single family homes. You have a gas furnace that blows heated air through ducts. It's supposed to be relatively inexpensive compared to electric baseboards, presuming you have all the natural gas infrastructure (or a big tank outside).
Same, I had to Google it too but didn't even understand the pictures since they were so alien.
Eventually found this page [1] which includes a basic description:
A baseboard heater is a convection heater. In such heaters, cold air coming in from a window enters the heater through a vent and hot air is dispersed through metal fins that are heated through electricity.
But it's still confusing because if it's cold outside (=you need heating) why would you have your window open to let in the cold air? That would also make your already-heated air escape ... duh.
Agreed, it's amazing how something that "feels" like it would get the same solution everywhere it's needed still does not, due to cultural differences, history, and stuff.
My Massachusetts home has both radiant floor heating (water pipes in floor) and baseboard water pipe heating (separate part of the house). My son’s New York home has radiators driven by hot water. I can’t recall a home where heating was vented air and not circulating hot water in North East USA.
We didn't set out to hide our GDPR requests, we put them behind our Support/Legal button. But we got sued anyway, and we lost.
Now we have to have the "delete my data" and "request my data" as part of our main settings list. Result: flooded with requests. People are clicking the buttons just because they are there. For me it's not a big deal, I automate all the requests. But, I still feel like this went too far.
Its our human right to have realtime machine readable data copies of everything we do, its no companies business to question or interfere. Unless it crashes your servers because trolls are trying to DOS, it is really hard to not be angry at a statement as "this is going too far".
> People are clicking the buttons just because they are there.
The reasons why they click the buttons are utterly irrelevant to anyone except them.
Let them click the buttons. It's their right.
> But, I still feel like this went too far.
Not far enough. I think data should be a massive liability. It should actively cost you lots of money to know any fact at all about any person anywhere on the planet.
In other words, in an ideal world you would be scrambling to press that button on their behalf the second your business with them was concluded. "Can we please forget everything we know about you please?" and only their explicit affirmative consent would allow you to not delete their data.
At the moment, holding data about someone is not a significant recurrent cost, but it is a liability in the form of a risk that could get you in serious trouble if you get something wrong. However, that particular business risk doesn't tend to be recognised by many many organisations. It should be.
If they can afford to be ignorant of the risks, it's because the liability is not high enough. Gotta raise the liability until they start doing what we want them to do by default. Private information should be an existential risk for them. They should be deleting every last bit without even asking, not sucking up endless amounts of it without consent.
> Users have basic bare bones functionality that all applications should support is "too far"?
They were objecting to the idea that putting it behind the "support" button is a violation. If true, that's excessive in terms of mandating accessibility.
I would never file a support ticket to open an account. If you did that, your business would be under by the end of the week.
No, requiring actual application functionality isn't too far. For God's sake, just make normal software like a normal person. This should all be very intuitive.
Stop trying to game things, stop trying to maximize conversions and other bullshit metrics, stop trying to implement every dark pattern under the sun and just... Be normal. I promise you will comply without even trying.
And, bonus points, your software will be less shit. I know it doesn't feel that way right now, because most software is shit. You shouldn't aspire to be another turd floating around in the cesspool that is the modern web.
Can we get the full story? I don't believe that's what happened because GDPR does not prescribe any specific avenue of requesting data. You're not required to have a button on your website at all, it's completely valid to accept and respond to requests by mail, but it's obviously much cheaper to offer automated data export.
I wouldn't. The current theories on sleep and "brain needs sleep" always struck me as a stopgap theory. Even spent some time with GPT arguing about it and never felt fully convinced, like the real reason was still missing.
The crystal emits no magnetism as a whole, despite the different internal states it can take, because adjacent atoms cancel each other out.
Because each half of the net-zero magnet is arranged differently inside the crystal there's still a good way to measure what state it's in. Or something like that, I can see the pretty graph but I don't know what measurement you'd do.
