> Leaked documents 1
obtained by SOMO reveal how, under the pretext of the now-near-magical concept of ‘competitiveness’, these companies plotted to hijack democratically adopted EU laws and strip them of all meaningful provisions, including those on climate transition plans, civil liability, and the scope of supply chains. EU officials appear not to have known who they were up against.
I'm seeing the exact same narrative more and more right here on HN, in every thread in any way related to the EU - the idea that the likes of GDPR are destroying "competitiveness". That if only all of it would be axed, "competitiveness" would arise once more.
It's not a coincidence, especially with so much FAANG employees, either ex- or current, who spend even more on lobbying than the likes of Exxon highlighted in this article. Though it seems naive to blindly hope that even in the age of mass astroturfing, this place is somehow immune.
It's frightening just how similar the playbook and the players involved are, big oil and big tech being oh so alike.
It's happening on a different level as well. More and more developers are moving from the US to popular startup hubs in Europe, e.g. Amsterdam, Copenhagen. They were often higher up in the FAANG chain, so they are immediately quite high up where the arrive, and they are bringing the American culture with them. E.g. what do you mean you're taking a month of holiday, or what do you mean, you're staying at home with your wife to take care of your baby. And yes, you have a right to that, but it's different to take that time when you feel it's accepted or frowned upon.
I'm following this Jujutsu project, I'm genuinely curious to see what it can bring to the SVC scene.
That said, the first thing I do now in a repo is jj init --colocate. The fact alone that there is an operation log in jj, so you can easily revert your last command, or go back to any point you want, is mind blowing coming from git and having experienced frantically digging through the reflog.
But that aside, the way to work with branches ahem bookmarks, commits, conflicts, just makes so much sense in a world where simultaneous feature branches are a thing.