butteroverflow
You know how motorists sarcastically refer to cyclists over here? "Crunchies", or something like that.
About a half also smokes, and then they "don't have enough air".
By the way, the office faces an arterial road, as they are called, with heavy traffic right outside. When you open a window, it fills very quickly with traffic fumes. This gives me persistent headaches almost every day.
Is it really better than CO2?
https://en.wikipedia.org/wiki/Khrushchyovka
These buildings were developed in massive numbers back in post-WW2 years, across the whole Soviet Union. with the task to move people out of barracks in some sort of relatively comfortable housing. Back then there wasn't much money to spare (still isn't). They typically have pretty bad insulation and are built out of, as we say, "cardboard" walls.
When it's cold enough outside (-35°C and lower), you can see the energy losses with a naked eye, as hot air escapes through every crack in the building (and there are a lot of them). No need for thermal cameras.
People over here just don't give a fuck about nature. Now it's the middle of summer, it's +33°C outside. I am sitting in the office with two ACs running at full capacity and with all windows open, because "there isn't enough air". I tried arguing with this, but it's pretty difficult to go against all my coworkers at once. It's a cultural problem, and I have no idea how to fight this.
Thanks for the sanity check, though, at least I know it's not me going crazy.
https://github.com/google/sanitizers/
Sure, Google is primarily a C++ shop, you could say that C++ is to blame and it has nothing to do with C.
But why the need for KASAN then? Which has a big track record at this point, by the way.
By prayer. It happened a couple times, although not yet on the city scale.
I don't personally know anyone who was affected. What they did, according to the local press, was stuffing every crack and cranny with old rags and sleeping fully clothed (as in fur coats and the like) and under as many blankets as they could get their hands on.
It's cheap low-quality coal with high sulfur content. The level of air pollution it produces is insane. In winter time you can feel the taste of coal on your tongue. The level of visibility is like 150-200 meters, after that it's a solid grey wall. Nobody here cares though, and if you do, you pick up your things and move elsewhere. That's what I am currently preparing to do.
I mean, how much coal do you have to burn to warm the air outside by 10-15°C?
I am from an ex-Soviet city too, by the way.
Of course, instead of opening the windows, you could always install a gate valve (or whatever it is called in English) and close it to make the water go through your apartment's heating elements without actually (mostly) heating them, and that's what they recommend, but why bother? The level of self-entitlement of many people here, you wouldn't believe. I could tell stories all day long.
Like a caricature of a stereotypical American tourist.
Would love to get all the complainers here to spend one month in winter where I live. We frequently have -35 to -45°C outside, and +30-35°C inside. How about a 70°C temperature difference?
Shouldn't that be banned by fire hazard regulations?
Edit: oh wait, it's actually 12 lines, the same as on your system. The reason it reported 11 on the first run is because KPTI has been disabled manually here.
I remapped my prefix to C-q. It's a relatively useless key (who needs flow control these days?) and it's close to the number row — you can press it and then quickly get to a number key.
Oh no, don't even put them in the same sentence. I am no fan of Go, but its error handling approach is beautiful compared to PHP. Every time I call an internal function I have to go through the docs — does it return a NULL, an int, a boolean, or something else? Does 0 signal an error condition, or is it a valid value? Do I have to perform a strict check for NULL/false then? Or is it -1 (see link below)? The situation is generally better with third-party libraries though — they tend to just throw exceptions (if that matches your definition of "better").
I was not aware you should not post here anything less literal than x86 assembly, now I know.
You can also revert multiple transactions at once, e.g. restore the package versions to what they were three months ago.
There's nothing remotely like this in apt -- if you install a lot of packages on your system, and then want to remove them, the common solution is something like "parse the (text) apt logs, learn manually what's changed, and revert it yourself".
Some other niceties:
* package groups: `dnf install @'c development'` instead of `apt install binutils gcc make bison yacc whatever-else`. Somewhat mitigated by metapackages, but they rarely cover the whole groups of functionality, i.e. they are often more low-level.
* package streams: `dnf install node-8`, or `node-9`, or one of the other supported versions;
* dnf downloads many packages in parallel, and the level of parallelism is configurable. This greatly helps with upgrades from slow mirrors. I believe it can also utilize multiple mirrors at once, though I haven't tried it.
* dnf supports plugins and you can install them with a simple command. For example, there's a plugin to automatically create btrfs snapshots on every package upgrade.
* COPR saved my skin a couple of times, though it's basically the same thing as Ubuntu's PPAs. This is more of a problem for Debian.
>It is amazing how well things work – the modern assembler, linker, and debugger handles the code generated by GCC 1.27 without any problems.
https://kristerw.blogspot.com/2019/01/building-gcc-127.html
And the write-up he based his experiments upon:
https://miyuki.github.io/2017/10/04/gcc-archaeology-1.html
I'd say this kind of source-based backwards compatibility is superior to what's happening in Windows world -- not only it encourages you to keep the source code open, but you also don't have to keep as many hacks in the kernel/system libraries.
https://www.gsmarena.com/results.php3?nYearMin=2018&nThickne...
My greatest dream is to be able to completely shut down the signal from the ears to the brain, with the ability to restore it at will, of course.
In my experience GPU rendering does provide buttery smooth scrolling and output for tons and tons of text. Now you can `cat` that 1 GiB log file that much faster!
I still prefer libvte-based terminals though.