Reinforced planetary care: localism on its own cannot resist globalized pressure, nor solve planetary and global thermo-dynamic issues.

there’s an idea that dealing with climate change is an issue for our institutions. Whereas you can see by clear evidence that our institutions have a track record of completely failing to address climate change at all levels throughout the entire history of the climate discourse.

But surely, purely local commons, which have been under centuries of pressure in the capitalist order, are not enough to be such a counter-weight ? Indeed, they are not

when a open AI developed a gp4 and they wanted to test what this new AI can do they gave it the task of solving capture puzzles it's these puzzles you encounter online when you try to access a website and the website needs to decide whether you're a human or a robot now uh gp4 could not solve the capture but it accessed a website task rabbit where you can hire people online to do things for you and it wanted to hire a human worker to solve the capture puzzle

So, not only is it on our generation's watch that  everything has occurred, it's on our generation's watch that we will determine the future. So,  so it's, in our hands. to now determine the future for humanity on earth. So yes, it's  an intergenerational justice, fundamentally.

We are in a time between worlds

work on stress so tell me about the work on happiness

we have individual capitalists who try 00:48:45 to make the most profit and this is linked to their capital and productivity so to achieve more in less time and 00:48:57 productivity is linked to energy [Music] the only source of energy to increase profit is carbon oil and gas and this has resulted in a change in our 00:49:15 atmosphere we have to put an entities if we wish to live in our planet can our capitalism do this based on the current data we won't be able to do so 00:49:28 therefore perhaps we should do the following reflection if capitalism is unable to do so either Humanity will die with it or 00:49:42 Humanity will overcome capitalism so that we can live in our planet

The problems that we solved are applicable to a lot of people. Most people are not even aware of these problems, so things can break in unexpected ways (Murphy's law). It's inefficient if everybody has to solve these problems over and over.

Ruby Object Mapper (rom-rb) is a fast ruby persistence library with the goal of providing powerful object mapping capabilities without limiting the full power of the underlying datastore.

Boilerplate is only boilerplate if it's the same everywhere, which it shouldn't be.

As a conclusion, I’d say that Flexbox in an email unfortunately causes more troubles than it helps solving.

I am wondering if it wasn't faster for maintainers/developers who know the glib code to just provide a fix instead of writing comments on this issue.

I'm kinda stuck at the moment, going around in circles. Everything is really heavily coupled. I would like to get to the point where no load is called from within processors, but i'm not sure if that's possible. Currently the API and the caching strategies are fighting me at every step of the way. I have a branch where i'm hacking through some refactoring, no light at the end of the tunnel yet though :(

it's super hard to test master because i have no idea which gems need to be updated. is there a guide on how to take a rails 4.2 project to master sprockets without everything mysteriously exploding? ill try to make a repro case but its hard to tell where to even start

Is there a PR to... something? sassc-rails? That would make the patch not necessary? (I don't know if there's any good way to monkey-patch that in, I think you have to fork? So some change seems required...) Should the defaults be different somehow? This is very difficult to figure out.

Not all cases can be covered and easily restored. And sometimes when we will reuse this function for different use-cases we will find out that it requires different restore logic.

But why do we return 0? Why not 1? Why not None? And while None in most cases is as bad (or even worse) than the exceptions, turns out we should heavily rely on business logic and use-cases of this function.

So, the sad conclusion is: all problems must be resolved individually depending on a specific usage context. There’s no silver bullet to resolve all ZeroDivisionErrors once and for all. And again, I am not even covering complex IO flows with retry policies and expotential timeouts.

systemd has such huge documentation. systemd.unit Did you try searching for explanation yourself? What did you find?

http://letmegooglethat.com/?q=How+to+change+the+default+search+engine+in+chromium&l=1

that's the only really accurate answer to the question: all the others propositions run an "almost same" container, but they forget the volumes, env, UIDs,