Decentralisation. I don’t want to fall in the same trap picking a huge platform which can only be ran by a large entity. Federation in Forgejo is taking quite long.
We made a PoC on top of Solid which does work so it is clearly possible, but the code quality is too low to trust the solution.
To my knowledge, but I did not look this up, these constraints were known at design time. I don’t recall these changing. Hence the statement may be true, but pointing at the known constraint after the fact shifts the blame to nature conservation rather than infrastructure and climate change. This at a time where climate change focus is of utmost importance.
Hence, albeit factually correct, it is disingenuous to give it the focus.
If these constraints were added in the past 10 years then that could be considered different depending on the reasons for the change.
What has changed are the water levels and base temperatures. Our environment has changed and the infrastructure has not been adapted to it. Luckily we have other tools for generating electric power ready to be rolled out.
That twists it to “protecting nature raises your electricity bill” where it’s just that that the plant, when built, did not take into account water levels could drop this low. As if they assumed climate change wouldn’t be this influential or something.
Interesting read. I’ve glanced over sections and read others.
I’ve been involved in the use of some of these frameworks. They are good reference frameworks but they are most often overly heavy to get started and/or the implementation is most often not supporting what the marketing material suggests.
Good integration projects start from limited partners with limited datasets exchanging with each other knowing they want to exchange with more partners in the future. Limited can be two to seven and they can even be in the same organisation. Perhaps it works with more, I have not been involved in that. They contain only the necessary roles and know how they’ll expand. These frameworks are great to get the expansion options in place. However, to get something going we’ve seen that a cheap and structurally correct solution to data sharing gets the ball running more quickly and for longer, then an expensive and heavy project which needs all sorts of approvals (even if it would be superior).
Projects that start with the weight of all the roles filled in by different actors need substantial funding to get started and I don’t think they generally last after funding dried up. Projects faking their way through the extra roles and providing the most limited interpretation of some of these roles with the project having some (even vague) shared benefit seem to survive past the grant stage.
Get some basics right and get going is my advice. Identifiers, shared and extensible data models, and a clear way of sharing data.
I like these frameworks, they help set the stage, but my gosh do they see problems where there are none when a project is just getting started.
Not saying you should buy new, but compare prices with Starlabs and Slimbook etc too when you’re at it. System76 and certainly frame.work are more on the expensive side. Slimbook has had a good spare parts catalog for my model, no idea about others. Maybe wait for a Canada-EU trade deal XD
I don’t study the market but I’m not counting on price drops in the coming 2 years. Real cost will likely go down only with inflation.