There is in France a kind of shared network of hot water used to heat up our homes (well, those that are connected and paying into the system at least). Part of the system works by burning trash and capturing the heat in the process. Supposedly they also work on using renewable energies to do the work.
Some people argue that the whole system is going against the objectives of recycling stuff but at least it's better than just burning it to get rid of it.
Because most maintainers love it compared to Sys V scripts.
In the end, users might complain about purity of things or something but the mainteners are the ones doing the work maintaining all that and end up deciding what gets used.
Honestly, I'm rather outside of all that stuff and I had my share of problems with systemd issues but that's mostly because I've been using pretty old systems anyway with thus older and buggier versions of the code. And I also remember the pain it was before unit files to get those sys V scripts working correctly. From my perspective, both systems had weird bugs I had to track but systemd clearly wins on the "creating a new service" part.
Or maybe we should stop the propaganda arm of the US fascists distorting the reality around here and inventing needs that our population doesn't actually need so that they are pushed towards far right parties?
Or how about making sure the corrupted US society do something about them messing up the world economy because rich people want to be richer and so they bought their governments through once again their propaganda arms of all the social media and news corporations they bought?
What about the parts where the US would bomb constantly the ME thus making the people living there want to move out. But of course they won't go to the place that bombed them, especially since there's a whole ocean between them so instead they come to us in the Europe. Oh and if it's not bombs, it's global warming anyway, another thing the current US government pushes hard for.
The reality is that it's probably mostly about incompetence and lazyness. And tight purses of course.
When some country parliament decides to mandate age verification, it's really easy and lazy for them to just say "verify ages and do it reliably!" and stop at that. As a result, the services affected don't really have a choice to go towards those horrible solutions of scaning our faces or IDs or both and all the issues around that.
What should happen rather is "we'll build a system for age verification that is privacy focused and all you sites that are adult only will have to use it or any other system we deem acceptable" But this requires effort on the part of the government doing the law. And money.
Yes, wellknown solutions have a strong grip on you. In this case it is unfortunate.
I know that the preparations for eIDAS 2.0 (the European thing) did contain many good parts. Taking inspiration from SSI. So at that point their specifications were rather good. I havent kept up with it for almost one year now, so that might have changed.
I thought the point (which the article misses) is that a token gives you an identity, and an identity can be tracked and rate limited.
So a crawlers that goes very ethically and does very little strain on the server should indeed be able to crawl for a whole week on a cheap compute, one that hammers the server hard will not.
In a similar vein, I remember people advocating for replacing new untrained hires with AI. After all, a competent senior engineer is needed to validate the contributions of the new hires anyway and they can do the same checking the AI code.
But then, how would you even train and replace those competent seniior engineers that do the filtering when they retire? The whole system was predicated on having a chain of new hires that gain experience in the process.
From what I could perceive, companies believe coding AIs will eventually learn to both code and teach better than seniors.
This is based on two assumptions:
- AI will get better. Developers using the system will transfer their knowledge to it.
- Seniors in a couple of years will be different. They should be those who can engage with the AI feedback loop.
Here's why I think it won't work:
- Senior developers learn more than they can produce. There is knowledge they never transfer to what they work on. Internalized knowledge that never materializes directly into code. _But it materializes indirectly_.
- Senior developer knowledge come from "schools", not just reading. These schools are not real physical locations. They're traditions, or ideas, that form a very long tail. These ideas, again, are not directly transferrable to code or prose.
- Juniors get embarrassed. You say "stop making this nonsense", and they'll stop and reflect, because they respect seniors. They might disagree, but a pea was then placed under their matress, and they'll think about "this nonsense" you told them to stop doing and why. That is how they get better. So far, AI has not demonstrated being able to do that.
The production of quality content is an aspect of one of those "schools of thought". You are supposed to bear the responsibility of passing the knowledge. Keeping lean codebases easy to understand is also a hallmark of many schools of thought. Working from fundamentals is another one of those ideas, etc.
Some people argue that the whole system is going against the objectives of recycling stuff but at least it's better than just burning it to get rid of it.
reply