foohbarbaz
Joined 14 years ago
Joined 14 years ago
Somewhat related: I am amazed now much gossiping goes on in an entirely male work group behind other people's backs. Males are definitely worse than females in that regard. I would not be surpised if allegations were true. A bunch if primadonna devs can be nasty to work with. Just stay away and separate work and life.
http://militera.lib.ru/research/suvorov12/07.html
is spot on! Been there.
So, you are doing 84mph (speed limit being 75) and go from relatively bright lit area into a dark and a curve. A second of blindness inevitably follows.
Still, I would probably rather just have a higher divider between lanes in different directions, so that high beams can be just used most of the time.
Over the mountain passes in spring where the lane markings get worn down sometimes you just can't see anything w/o high beams (and risking to blind the oncoming traffic).
What you get in return is both stability and security, since you don't wait for vendor to release a patch and actually understand what the vulnerability is.
With wholesale patching, in fact, you can never be sure whether your system is secure with respect to all published vulnerabilities.
Another interesting detail is, that with services running built from sources often you end up with vulnerabilities not applicable to your configuration.
Oftentimes, you can just tweak the config instead of changing code (and potentially breaking running things).
Software updates is just a cop out for people that are too lazy to pay attention to security.
You only patch what you need to patch. Most of the time for every production service you end up building a custom version anyway. Patching does no good to those.
So, by patching you only bring potential harm and overhead of going through change control processes.
I do not accept the risk of waiting for some vendor to release a patch. If there's a hole, read the report, determine whether your config/build is vulnerable, rebuild.
Why would want to patch something you are not running or use?
If I am running a service facing the internet, it's custom built and patches would do it no good. Why would I wait for vendor to release a patch? If a service is external, I will watch out for vulnerabilities and rebuild ASAP before any patches are out. Besides, 90% of the time my custom build is not even vulnerable to a particular problem.
If I am NOT running a service, why would I care about patches for it?
Why would I wholesale patch a server anyway? If somebody breaks in and gets a local shell, all is lost anyway. If they are not in, they are dealing with externally facing services only, see above. There are specific and counted number of daemons on every machine.
This whole patch-update thing is misguided and for people that want assurances and no responsibility.
Navajos, who don't make eye contact or smile either also take some getting used to now.
It's cultural, but Russia is a harsh place, so it goes deeper.
The part about people in the street not being helpful to each other is also true.
Just watch those dash cam videos where people witness a horrible crash, drive around and keep moving. You can die in the street and nobody might care. It's cultural and it's not a good thing.
The mob mentality is also a lot stronger. Westerners are a lot more tolerant to people being different or choosing their own way. It is in fact encouraged to be different and individual. Russians on the other hand, have whole layers of culture dedicated to making sure everybody is not sticking out of the crowd and not being an individual.
USB requires a lot more work and on Windows the API is atrocious. On Linux the API (libusb) quite a bit nicer, but still a bit of work.
The plug and play part, device naming and unique identifiers are a special "joy" of USB.
If serial port is sufficiently fast I'll take it any day over USB.