Well it is free so people have freedom to edit and have a repository of free software without jokes. But nobody has right to demand what goes to someone else's repository.
If glibc maintainers choose to make their own repository which Stallman has has no right demand anything they are free to do so. And then it becomes distributors freedom to choose who's repository they prefer.
What percentage of HIGH PAY ENGINEERING jobs in google have comp sci degrees, that's the true comparison. And then there is bigger issue here. It's really the obsession about percentages of women in X position. Here's another percentage what percentage of women and men didn't waste a thought on how they looked in their teenage years because they where so obsessed on how computers worked? I believe it is both very small and men are over represented there, and they are over represented in high paying computer jobs.
A nice project, but I didn't find the license for the source code. As without one no-one can really legally use parts of it for anything that can become serious.
Of course it might be that I have missed it or it is hidden somewhere. I hope it really exists somewhere in the repository, but I didn't find it. I might be too tired to find it and someone else has better luck.
No not really. The finger was about not giving enough details for opensource driver and pushing closed source blob instead. This issue is about closed source blob not supporting next gen linux desktop until the desktop has gotten enough market share to force them to.
i7 7820X is the CPU is probably the best system price/performance overall in the long run right now. Threadripper might be competing it depending on what you do but we don't know about it yet. For software developers having over 50% lead in compilation performance compared to ryzen 7 1800X (nightly build of chromium on visual studio) should make it a good choice.
A) In system price there are many components and that
makes ultra cheap CPU:s in other vice identical configurations not so good price-performance.
B) Performance is really the performance differential from what you upgrade. And even more importantly the performance differential years from now to systems of that time, if you upgrade to a system that lasts 5 years before you upgrade or to a system that lasts 7 years before you upgrade is significant in terms of price/performance because later means you get the high performance early and price last longer.
C) Significantly higher single threaded performance compared to Ryzen 7 the main contender. There are still many tasks that are single threaded, especially if you run legacy code.
D) AVX-512 I doubt the review benchmarks are in AVX-512 but some legacy code. AVX-512 increases both width of vector and fraction of code and algorithms that can be parallerized significantly. Once compilers are well tuned to use AVX-512 the code compiled with AVX-512 optimizations turned on should be significantly faster than what it was before hand. Simply being able to do 8-16 times work per cycle in large variety of tasks is significant advantage even if that is for a good fraction of time instead of all the time.
Personally I7-920 has given me far better price-performance compared to people who bought dual core at the time simply because it has lasted LONGER so it had superior price/(time between CPU upgrades) measurement. Right now in that same measurement I7-7820X is the king.
So in conclusion I7-7820X is faster in both real legacy code and the future code, and gives good enough performance longer simply because code that you run when you would start considering upgrades run much faster on it simply because of extensions.
Lots of keys combined with Meta(alt)+Control key, the optimum keybinding for window manager, those two keys are always unused in user programs. Its really perfect for emacs, no-one has imagined to use those two keys with some random key, on any of emacs packages or modes.
Poor me have binded my windowmanager commands with Super(windows) + (what ever command key I use for it.
Tim Ferris: Four Hour Workweek .
Eliminate, Automate, Delegate...
It can give you ideas on how to delegate more.
Secondly figure out how to retain developers. If it causes you stress and hiring is real expense then you should invest in fixing it.
Make developer work environment as good as possible and maybe pay slightly above market pay.Your job is to fix the environment to reduce turn over to compensate the boring product with other factors they value.
If glibc maintainers choose to make their own repository which Stallman has has no right demand anything they are free to do so. And then it becomes distributors freedom to choose who's repository they prefer.