and jim gettys blog https://gettys.wordpress.com/ are good places to start
1,739 karma · joined August 21, 2009
and jim gettys blog https://gettys.wordpress.com/ are good places to start
And then there are the bufferbloat people who finally tracked down the fact that in various common situations, the normal Wi-Fi protocol has a nasty interaction where it self-degrades to ridiculously slow speeds, and will take 2-5 MINUTES to recover.
We just don't have enough people doing serious whole-stack hardware+software analysis on our wireless stuff. At least outside of cellular telephony - probably because the money is more concentrated there.
Never before in history have we attempted to store wealth at this scale for things like retirement.
In a world that was continually growing at a pretty solid pace (i.e. since WW2) that was sort-of conceivable because the bigger next generation effectively created more space for that.
But now people live, and retire, for muuuuuccchhhh longer.
And sovereign-wealth funds, retirement funds, insurance funds, etc, are much larger.
And population growth is slowing (and with, financial growth).
Some very hard things to square coming up.
Every single one of them has had various annoying bugs that would not have survived decent QA.
But your point is partially correct - at least the LTS releases had workarounds for the problems, whereas with Fedora I am SOL
or hack up a daemon-process thing where you can start it up outside the loop, then call it inside the loop
And once they get sufficiently interested, they can crack pretty much anything the market can come up with.
So if you're trying to hide stuff - old school is probably best, innocuous code-word language stuff, keep communication to a minimum, leave phone at home, etc, etc.
e.g. I don't have working VNC server at all on latest Fedora, with either X11 or Wayland, and no sign of it being fixed anytime soon.
And that is just one of many irritations with desktop linux, that simply don't occur on Windows, mostly because of MS superior QA
Obviously, YMMV, but I find absorbing any theory-heavy knowledge alongside my day job extremely hard, whereas I can very easily more practical skills as a I work.
Source: mailing list discussion with one of the Sun devs.
I love macOS, but their software generally has issues with flakey internet connectivity and long latencies - down here in South Africa, ~400ms RTT is not uncommon.
How about we give them some benefit of the doubt, that they are mostly trying to make things better, and instead ask them "what is the technically correct way, in the systemd world, of implementing this functionality?"
I suspect the answer, for screen, would probably require some degree of messing with the user manager daemon.
Coz I use it every day, and despite many little deficiencies, it still compares well to other cross-platform toolkits.
Like just chopping off a leg instead of spending a 12 hour operation and months of physiotherapy to save it.
Letting people die from chronic conditions instead of managing them.
Letting old people die, because the cost of medical treatment was too high.
Not performing operations for heart disease, so people got one heart attack and then died a year later.
Which we could totally go back to, it really is a lot cheaper.
Once you pull the aquifer down far enough, the surface starts to dry up, plants stop holding the soil together, the microclimate changes, which reduces the water capture, etc, etc.
It had great shared/cluster filesystems, that came standard, that have only been replicated in about the last 5 years in Linux (see Gluster/Ceph/etc), and the Linux equivalents are (still!) less well documented with much higher admin overhead.
The downside was, of course, that all those great features worked only with VMS software and hardware, and only with specific combinations of the above.