Earlier quoted context omitted.
the same applies to Stallman, if you consider that the FSF has been running for 34 years. But I believe grandparent didn't mean they lack charisma, but that they didn't have enough to swerve the general public.
I would posit that: impact = charisma * funding so .1 charisma score of some faceless tech exec * 1B in VC funding goes alot more than 2.0 charisma score * 50k of grasroots funding..
OpenBSD was right to disable hyperthreading [video]
161–170 of 284 posts
Re: OpenBSD was right to disable hyperthreading [video]
#162Earlier quoted context omitted.
I would posit that: impact = charisma * funding so .1 charisma score of some faceless tech exec * 1B in VC funding goes alot more than 2.0 charisma score * 50k of grasroots funding..
I wish i could favorite a comment.
Re: OpenBSD was right to disable hyperthreading [video]
#163Earlier quoted context omitted.
Lacking in charisma hardly describes a person like Theo de Raadt. I've never met the man, but I doubt that someone who lacks charisma could have lead a dedicated, opinionated team through more than 40 releases (counting OpenBSD releases alone!), over a period of almost 25 years now, a team which not only developed a sturdy (if equally opinionated) operating system but also a bunch of highly successful projects like,…
the same applies to Stallman, if you consider that the FSF has been running for 34 years. But I believe grandparent didn't mean they lack charisma, but that they didn't have enough to swerve the general public.
Re: OpenBSD was right to disable hyperthreading [video]
#164Earlier quoted context omitted.
You said the reason people don't use BSD was because the people who work on it are were too expensive. I know Google don't use BSD, but your idea that it's because they couldn't afford to pay BSD developers doesn't seem to add up, since Google happily pays Linux kernel developers maybe half a million dollars or more. Are the BSD developers really paid so much that Google can't afford them over the Linux developers? T…
when I said "Work on the systems" I meant support maintain care and feed. Linux has become mainstream so there are more people in the talent pool to pay to support it. Windows ... has more so it is cheaper BSD simply doesn't have enough people who know the system well enough to support it Paying 5 developers to build something cool doesn't mean you have the support system to run it.... You actually need people who un…
In some ways & depending on the situation, moreso, since linux distros are often trying to do things drastically different from each other in order to differentiate themselves, whereas BSD's are often sharing code because of the small developer base, sharing-compatible license, and lack of bottom-line oriented corporate sponsorship.
Re: OpenBSD was right to disable hyperthreading [video]
#165Re: OpenBSD was right to disable hyperthreading [video]
#166Earlier quoted context omitted.
HT doesn't actually make video encoding go any faster. It just allows the system to remain more stable while performing some other task at the same time. You really should not be running other tasks on your system while encoding video, your encoder will need all the resources it can get.
Uh, are you sure of that? My experience has been that x264, for instance, benefits greatly from hyperthreading. Hyperthreading allows you to queue up additional instructions (in a different thread) that the executor can switch to when it would otherwise be just waiting for the next instruction in the primary thread.
In making my previous claim, I was limiting the concept of 'encoding' to the more old-school definition: lossless compression of media bytestreams. This would include things like HuffYUV, ProRes, etc. But to be fair, these days it is quite likely that even a few of the newer intermediate/mezzanine codecs benefit from hyperthreading. I'd edit my post to clarify but the edit window has passed.
Re: OpenBSD was right to disable hyperthreading [video]
#167Two of the three (current) top-level replies compare BSDs to Linux in general, but that really has nothing to do with whether you disable HT. Using Linux should not have stopped anyone from listening to Theo and disabling HT months ago. Your security authorities don't have to be your kernel developers.
How many other decisions made by kernel developers are you supposed to second-guess because you know better?
On the image that you're pushing out to your fleet of production servers? Maybe a couple.
Re: OpenBSD was right to disable hyperthreading [video]
#168History will show that Theo was right in a manner similar to how Stalman was right: technically correct analysis and eerily accurate predictions, but lacking in sufficient charisma to create more than a small following. To some extent, you might say they are like Cassandra; speaking the truth but not believed or listened to.
Lacking in charisma hardly describes a person like Theo de Raadt. I've never met the man, but I doubt that someone who lacks charisma could have lead a dedicated, opinionated team through more than 40 releases (counting OpenBSD releases alone!), over a period of almost 25 years now, a team which not only developed a sturdy (if equally opinionated) operating system but also a bunch of highly successful projects like,…
Charisma means being able to persuade all kinds of individuals, regardless of their inclinations and initial positions.
Re: OpenBSD was right to disable hyperthreading [video]
#169Is anybody actually attacking AWS this way? It seems a promising attack vector; you get to run your own code on the same machines as others.
[1] https://aws.amazon.com/ec2/instance-types/#instance-details
Re: OpenBSD was right to disable hyperthreading [video]
#170Earlier quoted context omitted.
A new technique to pick locks is discovered. Does that mean all locks are defective?
When the Kaba Simplex (a commercial door lock) was discovered to be easily bypassed by holding a magnet near it, yes, it was in fact a design defect and the company had to correct it by giving repair kits out to purchasers.