So, I see this as rationalization.

The fact is, you took a leadership position, and later turned your coat for reasons that perhaps made sense to you. But they don't really make sense to anyone else. So, yes, everyone who supported you then is going to feel burned.

You also made yourself a paid voice that was often hostile to Free Software, all the way back to the SCO issue. Anyone could have told you that was bound to be a losing side and you would be forever tarred with their brush.

So nobody is going to believe you had any reason but cash, whatever rationalization you cook up after the fact. So, the bottom line is that you joined a list of people who we're never going to be able to trust or put the slightest amount of credibility in.

And ultimately it was for nothing. I've consistently tried to take the high road and it's led to a pretty good income, I would hazard a guess better than yours, not just being able to feel good about myself.

Meh, it's easy to find people with skill. With values, OTOH...

You have a point.

It's sort of a chicken-and-egg issue. Debian doesn't get the help because Debian doesn't make itself worthy of getting the help. There have previously been paid developers working on Debian, they simply weren't paid by Debian.

I am beginning to be wary of systemd, but no. I am talking about anal-retentive policy wonks who believe they only make the distribution for themselves and have (perhaps without intending to) systematically marginalized Debiian and made the project a whore to Ubuntu.

There is a certain contingent in Debian that is not good for the project, IMO. I would like to see which side of a fork they are on, and pick tthe other.

This is actually two bets, isn't it? One is that I live to be 93. Not terribly likely.

OK, you're on. Not that $10,000 is likely to be worth as much in 2050.

Let's make a bet then. You pay me $1 if there is no credible commercially utilized cold fusion by 2024. I'll pay you $10,000 if there is. And please don't bother me until then.

Um, no, x86 CPUs are nothing like ARM and I'm not aware of any commercial x86 CPU with an ARM backend. Yes, modern x86 cores use a RISC-ish microcode backend with an x86 decoder frontend, but that doesn't say anything in favor of ARM. All it means is that the industry has collectively agreed that CISC as a microarchitecture is a stupid idea - not necessarily as an instruction set.

I'm not a fan of x86 myself, and I think it's a stupid design with a vast amount of baggage causing a significant power/performance impact when designing an x86 CPU (that Intel can get away with because they're a generation or two ahead of everyone else in silicon tech), but then again ARM isn't the pinnacle of RISC either (though I do think it's better than x86).

Me, I'll take whatever microarch gets the best performance per watt at whatever TDP is relevant. If Intel can pull that off with x86-64, by all means. If ARM AArch64 ends up ahead, awesome. If both are about equal, I'll take whatever's more practical based on other factors.

Let me preface this with the fact that I'm an intellectual property specialist. I bill $450/hour, and still have lots of time to work on my startup without having to take venture capital.

I thought about some educational answers for your questions, but the insult at the start of your comment rubs me wrong and I decided I don't owe you anything. So, I'll save them.

The first symptom of a new but incomplete understanding of patents is gold fever. That is when you have an idea that what you are holding is extremely valuable and that you must protect it from others at all costs. People tend to get irrational about it.

So here is some reality: The fact that you have even published your video (which is "use in commerce" under patent law) invalidates future patents that you might file on that same art. Then there is the prior art (including art you are not aware of), and the recent court finding in Alice v. CLS Bank that invalidates most process and method patents which describe software. These all work against the potential that your thesis is going to make you rich through patent licensing.

You can get a patent awarded, perhaps, that you can use to hoodwink an investor, but forcing an automotive company to pay you? Much less likely and it will cost $10 Million in attorney fees to get there.

Probably your school wants 51% of the revenue and your grant funding sources (and those of your college department) may have their own policies on patents.

Yes, this is definitely a "WTF?" moment in the history of Slashdot. I suggest that you all just move on to the next story and refuse to feed the troll by asking him questions.

Slashdot, obviously, has to innovate in order to stay current. Thus, they are now taking the next step after "Anonymous Cowards". The new "Identified Troll" feature will include interviews of people who have prostituted their personal credibility to some company's calculated disinformation campaign.

There's nothing I find particularly alarming here and the behaviour is in fact pretty much what I would expect for computing sin(x). Sure, maybe the doc needs updating, but nobody would really expect fsin to do much better than what it does. And in fact, if you wanted to maintain good accuracy even for large values (up to the double-precision range), then you would need a 2048-bit subtraction just for the range reduction! As far as I can tell, the accuracy up to pi/2 is pretty good. If you want good accuracy beyond that, you better do the range reduction yourself. In general, I would also argue that if you have accuracy issues with fsin, then your code is probably broken to begin with.