That they are not wrong that the standard of living for the average person in a lot of ex-soviet (which I assume they are talking about) countries did indeed decrease sharply after their "liberation".
Windows that are just invisible, as if they're located somewhere off-screen.
Windows that spawn in random places (such as the 3rd external monitor way outside my FOV), instead of following a logical rule like "on the same desktop as the cursor" or "on the desktop where this app is usually located".
Windows that get stuck in the middle of one of the fullscreen-related animations.
Oh, and that hilarious bug where the screen locker does not completely lock, so Outlook manages to show modal dialogs (that can be interacted with!) on the lock screen.
nVidia video driver crashing every time when a thunderbolt display is attached or detached since High Sierra.
Java windows flashing after screen has been locked.
Terminal windows using 100% CPU (some sort of render bug).
Bluetooth connections constantly dropping.
Windows of 0 by 0 pixels when restoring a desktop after reboot.
Video playback in every browser stopping after about 10 seconds.
Actually, there will be risk takers on top of existing ones.
Belarus is the source of great engineers that created Viber, Juno, MSQRD, WoT to name a few. PVT revenues will reach $1 bln. in 2017. This decree just added more perks to already existing tax privileges.
The system is stable and growing, why kill the cash-cow? IT enterprise is not and oil factory that you can nationalize. Engineers will take the laptop and fly away same day and your seized company will turn into empty building with zero profit. Even dictators understand it.
Not so familiar with vagrant on mac (though my time is coming), but having used loopback KVM's on rhel I can say that fiddling with mount options can drastically improve stability / performance (though still much slower)
e.g. tcp mounts, getting read/write blocks matched up btw/client server and sized to be digestable but big enough to move data, etc.
also, nfs is mainly only suited for 'NAS-like' operations - things like rdbms's do waay better on iscsi or eating the vdisk performance.
last I messed with macos nfsd (which has been a while), it a way happier with smaller blocksizes (e.g. 8-64k range) - modern linuces will attempt 1MB which is too much for the older 4.4BSD based code
another thing to look at is timeouts / backoffs - it's easy to kill performance by setting these things too agressively so that the system double-chokes when it gets bogged down..
clang doesn't document the full list of warning flags that it supports, but the clang source code has a list, including the hierarchy of meta flags that enable other flags:
http://fuckingclangwarnings.com/ has descriptions of many of the warnings, but more recent warnings aren't covered because the website hasn't been updated since 2014.
Thank you! I've never seen that page. It doesn't show up when searching for "clang warnings" in DuckDuckGo or Bing, but I see now that it is Google's result #2.
I just found a GitHub repo that lists which warning flags are supported by different versions of clang and gcc:
I found -Weverything seriously annoying. Declare a structure, and clang warns about padding bytes being added. Make it a packed structure, and clang warns about the lack of padding bytes. Useless! Okay, I can see the warning on packed structures, as that's usually a compiler extension, but a plain struct?
There is also -Wlogical-op-parentheses, which rather condescendingly implies that you don't know the precedence of || vs &&. (The main use of parentheses is specifically to indicate precedence different from the usual, since otherwise they just add noise to the code and reduce clarity.) I half-expect -Warithmetic-op-parentheses or even -Wop-parentheses to show up in some future version of clang...
Unfortunately there's no corresponding -Wuseless-parentheses, which if present would truly make -Weverything a "damned if you do, damned if you don't".
The point is there's a warning either way. Pack the structure, and you get warnings. Don't pack the structure, get warnings. To me, that's being needlessly pedantic.
I'm not convinced I want Scott Meyers yelling at me with -Weverything as part of -Weffc++. I think I side with the gcc devs here on not having a flag to enable every possible warning ever.
The results are terrible. I tried a simple search for a large Porsche dealership which is down the street from my house and it did not even come up in the top 5 results.
Would be a great search engine if it was the year 2001.
Well, for such use cases Google is a better tool indeed. I personally know my neighborhood and never google what is down the street. And if I need dealership I will try to find it on car maker website which is easy to look up even using search engines from 2001.
In communist countries millions of people were killed, so you probably should pick better examples.