Most of those small and medium hydropower plants generate near insignificant amounts of electricity, even if you damn all the non major rivers you can (and destroy all the surrounding ecosystems) it would be hardly noticeable.
My napkin math disagrees. Small/medium hydro (<100 MW) appears to account for ~1.7% of annual US grid energy output. If we replace that with fossil fuel generation and account for the cost of dam decommissioning, account for estimated benefit of ecosystem restoration in terms of quantified dollars willing to pay by benefiting citizen, and net annual CO2 cost I come up with an annual cost to society of removal of small/medium hydro dams between $1.7B/year on the low and $41.7B/year on the high end. Happy to show detailed assumptions and calculations if desired. But tl;dr fossil fuel generation is very, very bad and replacing even comparatively small amounts of carbon-neutral generation with it results in a significant societal net negative.
Wow, Omarchy is hot right now. Great to see all these companies contributing to a future with Linux on desktop. Good on Digital Ocean for making such a substantial commitment.
It would be a shame if css-tricks went offline after all these years. I can understand it winding down now that we are in the age of agents but I hope to see it preserved in some way so it stays online for a very long time.
Omarchy is a highly opinionated distro. For example I remember DHH falling in love with alacritty a few minutes after switching from being a Mac hardcore user-evangelist (Mac users were furious in Twitter!). Now alacritty is in Omarchy as one of the four terminals available.
This is to say that Omarchy is not Linux. Is a very particular vision of Linux that lots of people won't like. Funding should go to projects near the foundation of Linux (say Gnome or Kde or alacritty itself), not to some random re-packager known for having strong and radical takes that might swing without previous notice. DHH is perfectly able to wake up tomorrow saying "fuck Linux, fuck Omarchy, the future is Windows".
> Great to see all these companies contributing to a future with Linux on desktop.
I'm thinking they're merely riding the free publicity wave. Who, in their right mind, would contribute to the super narrow definition of linux desktop preached by DHH?
Was "being agentic" and "being keyboard shortcut oriented" the big gaps preventing the adoption of linux on desktop?
I honestly fail to see why everybody is so convinced that the linux desktop will be "saved" by Omarchy, a set of scripts specifically designed to mostly satisfy a narrow slice of power users and developers.
Also, sponsoring a multi-millionaire's AI generated side project to the sum of many millions of dollars instead of contributing to the dozens or hundreds of thankless developers that have built and maintained most of the current linux ecosystem is pretty disgusting imho.
Yes, though its worth noting the goal of Cordova was to not exist. In the eyes of the project the web itself is the cross-platform solution but at the time Browser progress was stagnant and Cordova helped move things forward by offering device functionality using open web standards. Cordova was never intended to be a "cross-platform productivity multiplier". The north star of the Cordova project was for browsers to get the device functionality that native platforms offered, such as geo-location, accelerometer, contacts, camera, etc.
I just want to correct this, because I agree with you but the framing is a misinterpretation of the goals of the Cordova project - goals which were ultimately met.
Actually yes. The chart is put together by "The 2 Degrees Institute" which has a stated objective of influencing "behavioural and lifestyle changes". That isn't science.
You may not be aware that node created a situation where ESM maximizes compatibility when consuming libraries and CJS maximizes compatibility when producing libraries. Its a circular incentive paradigm. I suspect you are consuming libraries using "import" and everything "just works". Well, under the hood you are likely importing many libraries that use CJS "module.exports" because that is what libraries use to ensure their library can be used with both import/ESM AND require/CJS.
The only solution to this problem is to upgrade require work for importing ESM. Once that is implemented ESM will become the natural choice for those publishing libraries. Until that happens library authors are going to continue to use CJS so their libraries are available to everyone.
The last version of Node that only supported CJS libraries has already long faded out of LTS. In my opinion, more libraries should just rip the band-aid off and entirely stop publishing CJS. Sure that will upset some downstream dependencies, but semver major tag it, and many of the downstream dependencies need the kick in the pants to move to ESM anyway.
Also, Node 12 supported ESM somewhat fine, you just had to use the --experimental-modules flag for Node. If you still have to support Node 12 in 2023 for some odd reason, you probably shouldn't have a problem enabling an experimental flag to support more modern libraries.
Node 10 was truly the last LTS that had zero ESM support, and that support ended 2 and a half years ago.
There is a ton of information asymmetry in education. (The parents don’t sit through the classes, and the kids have no reference points), which means it will devolve into a “market for lemons” in the absent of regulation.
In this case I would say that the latency of finding out a method or microschool isn’t teaching in an effective way might be longer than I would like to see as a parent.
So that’s a small problem as this is all rapidly developing.
This hasn't been true in the U.S. for a century when the house reapportionment act was passed. Now the strongest voice the majority has is in the Senate. The body that was designed to give voice to the minority.
Restating the same fact per days instead of per year doesn't change the facts. And the fact is it all adds up. The list of things that Twitter isn't paying is huge.
