105 karma · joined May 7, 2020
- more ways to do things -> more effort required to keep somewhat uniform style
- linus and friends just get to decide. (they can be as subjective as they want. The "their house their rules" kind of thing).
- there is no "c/c++" language. there is c and there is c++. they have different std libraries, different idioms, and expert overlap is not that high.
- linux kernel even in c is a huge success - so c is good enough for linux (enough kernel developers are comfortible and productive with it).
- linux might have succeeded with cpp if it were used from the start, but now it's too late. Migration to cpp is a no-go: benefits do not outweigh costs (old code will not be rewritten in cpp, so people maintaining code will now have to be profficient in c AND cpp).
Kotlin makes gradle bearable.
https://quickbirdstudios.com/blog/gradle-kotlin-buildsrc-plu...
Though there is a problem of ambiguity if word is reused (adjusted) for different meaning, while books (and people) from 1940 still continue using the old meaning.
(just pointing out that meaning of words of dead people also matter)
How I see it. Let's say, russia dared to enter a real multi-battle direct war with usa, to take alaska, and is winning a bit more each day. When would usa say "we give up, please take the alaska, we will not use our nukes?". - Immediately after the start while there are no casualties? - after 1k casualties on both sides? - after going to total war mode, when each side bombs industry complex'es and later cities on the other side?
Backing down would say "nukes are not deterant anymore. Same thing can be done to us again."
btw. Nukes can be used, not only on cities, but also on fleets and divisionsand camps.
So the only way nukes would be not used if victory would be very instantaneous and total, which does not seem probable.
.. and since i'm venting, diet experts use formula "1 cal = 1 kilo cal". why oh why?
(2) profit = selling price - production\development cost - expected downsides of accidents(penalties, tarnished image). "Expected downsides of accidents" can be reduced by reducing risk, but also in some other creative ways (blackmailing, lobying, promoting the right candidate, marketing, rebranding, migrating to different markets, insurance, coverups. And lets not forget deals with friends: If I can win 5billion, I can allow my self to split it 100 ways and still end up with a nice big yacht).
There are two groups of people. Latent antibody bombs (on slitghest signal antibodies go from zero to hero) and antibody deserts (where even at late stages of desease only low antibody counts are produced). Those which easily make antibodies, kill off the virus quick enough to get significantly less side effects compared to the other group.
IF such model would hold, then it would be natural that antibody deserts dont produce much antibodies when reacting to vaccine, so there would be corellation between succeptible to covid mortality and vaccine innefectiveness.
Do they test for vaccine innefectiveness corelation with virus lethality and/or complications?
(1). Tractor analogy seems too extreme - it's about skiping automation in farming. But if one skips saas, one still automates in house (the amplifier is the automation). Also, frequently "saas" feels less like "tech" and more like "outsourcing".
(2) Total cost of ownership applies to saas as well. Lawyer's time for contract. Developer\architect time to figure out documentation, so company would know what configuration to ask for. Communication being external also costs time.
(3) Solutions for data ownership exist, but it's one additional thing to worry about.