The thing that makes Everest dangerous is the air pressure combined with everything else, that's why it's such a long slow ascent, you have to acclimatize so your lungs don't implode.
In the summer the summit temperature is about the same as a bad Canadian prairie winter day
There is nothing this thing can do that a dedicated hobbyist couldn't replicate with parts bought off the shelf at a RadioShack, so where does the line get drawn
Chrome implements features that aren't standards track into their browser, and lazy/oblivious devs use these features to build their products - only to realize wayyy too late it won't work in Safari/Firefox because it uses APIs that are chrome only
It's markdown, if it detects "[number][period][space]" at the start of a line it converts it to an HTML ordered list, which always starts at one. You should be able to escape it with a \ before the period to bypass the markdown
At least for corn tortillas, placing them in a tortilla keeper (steaming basket) after you cook them makes a world of difference when it comes to having pliable tortillas - you can just use a pot/saucepan with a lid.
Baking powder in flour tortillas is common, helps them come out more like a light fluffy tortilla and less like a flat flour brick
All LTS releases get 5 years of updates. Ubuntu pro (which is free for non-commercial users FYI) extends the LTS support window to 10 years, which is 5 years more than any other Linux distribution I know of
However, the court decided that unauthorized access to data protected with a password violates Section 202c of the German Criminal Code, also known as the Hacker Paragraph.
The issue is the dev was authorized by the company he was working for to access their data, he had no way of knowing he would unwittingly be accessing everybody in the world's data
I mean I'm speaking from first hand experience in academia. Like I mentioned, this obviously isn't the case for people running prohibitively costly experiments, but is absolutely the case for teams where acquiring more data just means throwing a few more weeks of time at the lab, the grunt work is being done by the students usually anyways. There are a lot more labs in existence that consist of just a PI and 5-10 grad students/post-docs than there are mega labs working cern.
There were a handful of times I remember rerunning an experiment that was on the cusp, either to solidify a result or to rule out a significant finding that I correctly suspected was just luck - what is another 3 weeks of data collection when you are spending up to a year designing/planning/iterating/writing to get the publication?
the danger is that valuable data from studies straddling the arbitrary p=0.05 line is simply being discarded by researchers
Or maybe experimenters are opting to do further research themselves rather than publish ambiguous results. If you aren't doing MRI or costly field work, fine tuning your experimental design to get a conclusive result is a more attractive option than publishing a null result that could be significant, or a significant result that you fear might need retracting later.
To elaborate a bit more, there is the MySQL resource usage and the docker overhead. If you run two containers that are the same, the docker overhead will only ding you once, but the actual MySQL process will consume its own CPU and memory inside each container.
So by running two containers you are going to be using an extra couple hundred MB of RAM (whatever MySQL's minimum memory footprint is)
Every time there is a transaction the sender's funds are mixed together with a bunch of other senders, and the recipients receive their money from this random pool, so there is no direct association between sender/receiver
Because many apps will (or would prefer to) only be bundled as Flatpak.
This reads like speculation to me and is directly contrary to the file counts on flathub and snapcraft. What about CLI apps and server software? How are they supposed to distribute their software if not via snap? (Flatpak doesn't support this well)
could just as well be a rant why Canonical shouldn't have introduced Snaps in the first place
You are acting like Ubuntu core (and snaps) came after flatpak? Snaps were announced almost a decade ago
Like, I get you don't like snaps, but your argument is basically "every Linux distribution should ship the same default software, and it should be the software I choose"
The thing that makes Everest dangerous is the air pressure combined with everything else, that's why it's such a long slow ascent, you have to acclimatize so your lungs don't implode.
In the summer the summit temperature is about the same as a bad Canadian prairie winter day