Örebropartiet is not Al Qaeda nor a terrorist organisation. They can have a controversial position, but I'm not sure it is worse than the position of the republican party in the US which has many supporters amongst CEO of big tech companies.
But for desktop applications it is bloated, a big attack surface.
HTML/CSS is made for online documents, and using it for applications is a bit hack that happen to work, but hides a huge ton of complexity behind frameworks and frameworks of frameworks with leaky abstractions and each their own caveat.
Or do you need evidence that the bio labels are not optimizing for health or environment? Check the rules. Most of them are just there to restrict synthetic products, regardless of their impact.
They optimise for natural. So you can still have pesticides and herbicides. If you find your poison in some plant, it is fine. If you synthetize the same molecule in a factory, then it's not allowed.
As for the animal welfare, true, but there are also labels specifically for that that.
But it is controlled for the wrong criterias.
"Natural" doesn't mean healthy or good for the environment.
It is only greenwashing and "appeal to nature" fallacy
Because users and community contributors most likely already have an account, are familiar with the UI.
There is also the "gamification" aspect that GitHub have. Doesn't motivate me personally, but could have effect on some others.
Projects on GitHub gets a lot more visibility.
To the point that many projects that do not use GitHub as their main forge are still often mirroring their repository there, and have to deal with double source of bug reports or pr.
So far everything is going according to the plan. Humans are really close to make the AI that will replace them and enter into the next phase of the plan.
Or do you have a better idea of what the plan exactly is?
I might be missing something, but what I need is not "stacked PR" but a proper UI and interface to manage single commit:
- merge some commits independently when partial work is ready.
- mark some commit as reviewed.
- UI to do interactive rebase and and squash and edit individual commits. (I can do that well from the command line, but not when using the GitHub interface, and somehow not everyone from my team is familiar with that)
- ability to attach a comment to a specific commit, or to the commit message.
- better way to visualize what change over time in each forced push/revision (diff of diff)
Git itself already has the concept of commit. Why put this "stacked PR" abstraction on top of it?