Something we might not actually need but use anyway?
Something we might not actually need but use anyway?
Hmm, I’m not quite well read enough to understand this. I was thinking about running this in an LXC container, does the removal of non Docker setups mean that I would have to nest Docker in the LXC container? 😕
I bought the 8 pro in part for the promise of 7 years of updates. 😕
I understand not everything can come to old phones, maybe it depends on a battery management system feature that is missing in the 8 hw? Otherwise I’m disappointed for sure.
Edit: the missing hw was already in the comments… Read all comments before saying something 🤦♂️
And unfortunately wrong order for Jesus Titty Fucking Christ
There is hope. Haven’t looked into it, but there is the French German docs project that is based on open source and available on GitHub (under some license that I haven’t checked)
Me at a previous workplace.
-This is a piece of shit, who is the code owner of this module.
Ah, it’s me (“inheriting” code ownership when someone left was common)
Who did this change
Ah, it was me
Surely I just made a minor change to this line here, who wrote the function.
it was me, it was me all the way down
Fits the general theme of the thread as it was not giving any trouble for a year before being found.
Cold press would make it extra virgin baby oil?
We use slack for some things and teams for some things at work. Can’t say I really prefer one over the other. My dream is if we could just decide on one platform so I can find shit. Any of them!
Then I might be lying. Was all convinced I saw it at ICA, but can’t find anything online now 🤔
Unless they imported something under the radar maybe it was the “plant b+tter” I was thinking about.
My colleague was quite adamant that it was vegan butter he had used for the cookies he brought.
Recently I have been seeing “vegan butter” in the store. How this is not margarine eludes me. But my vegan friend assures me it’s completely different.
The crash early, crash often approach of Erlang has made for some amazingly resilient systems.
One time on a project I was working on, some horribly broken code was merged (nobody in the team had even heard of reviewing code). As soon as a specific call was made, it was executed once and then the thread crashed. The only way we noticed was that response times increased with load. All data and behavior was still correct. Whole nodes could go down and all you notice is a dip in performance until it comes back online.
Of course it requires special care in designing. Everything runs in stateless server threads with supervisors restarting them as needed. This in turn requires some language support, like lightweight threads. Our application would happily run tens of thousands of threads on an ancient sparkstation.