osmala
Joined 13 years ago
Joined 13 years ago
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.
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.
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.
There are real differences there between sexes, and those preferences affect what career is the best for you. You don't pick whats average for you, you pick your best career with all things considered, and small differences in preferences can skew the outcomes heavily. Also I like to point out there is bunch of careers where there is heavy shortage of MEN choosing it for same reasons.
Write everything down about your idea in a paper. Then store it somewhere safe. Let it go for a while, and concentrate on law school first year. Check if you can bring second year courses, to your first year. Check if you can study in the next summer also. Then if you can graduate in 17-22 months do it. If you can't do that, but can move workload from later years to first year then do that and be able to work on your idea in later years of your school more freely. Design your law school experience to get back to your idea in either 17-22 months from now as graduated lawyer, or 10-22 months from now part time because you have more free time in your school scheduler. This way your idea is motivator for you to work harder in your law school, instead of distraction. Your goal is to get as soon as possible able to work on your idea full time or with serious amount of time instead of splitting your attention between two.
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.