I don't think you understand the problem, but first off this whole argument is moot though because you can release things as separate modules for the kernel. If your super-awesome idea doesn't get upstreamed it's probably for a good reason - and if you still think it should be then release a module and see it get popular and *proven*. This has happened many many times and it is exactly the way it should continue to happen - if you think your idea is awesome and your code is flawless then prove it and come back.

Poettering and his team are fucks who don't care if they release code that breaks shit and that absoultely CAN NOT happen. They pushed a bunch of patches that caused showstopper bugs which could have crippled tens of thousands of servers etc. had they been upstreamed. Then when Linus told them he wouldn't even consider upstreaming any of their code until they cleaned up their act and started being more clean and careful they get all pissy and say they won't work with Linus again.

Honestly I don't see why people are taking the sides of a self-proclaimed rock-star coder VS someone who called out said rock-stair coder for pushing code that epicly breaks shit and used "mean" words in the process. Poettering needs to realize if he released shit code he deserves to be called a fucking jackass; and the appropriate response to that is to fucking fix your code and stop assuming he's so awesome he doesn't need to test his code or hear out the people telling him there are problems.

That is a fantastically easy to understand analogy! Somebody needs to mod you up.

I'm hoestly hoping to get something like "+3, Flamebait" :P

Visual J++: http://en.wikipedia.org/wiki/V...

First paragraph starts with:
"While J++ conformed to the Java language specification, Microsoft did not implement certain features of the official Sun Java implementation in its Visual J++ product line. Remote Method Invocation (Java RMI) and Java Native Interface (JNI) are such examples.[2][3]

In addition, J++ implemented other extensions that were not part of Sun's Java implementation. The inclusion of callbacks and delegates for event handling further contributed to defining J++ as a completely different language merely based on an already existing design concept."

Not really worth reading past that... Also someone further down in the comments here covered it in detail.

You're talking about Visual J or whatever, and it was a big thing because they customized it and made it so it was no longer standard Java. Write code for Visual J and often it wouldn't work for regular Java. There were a bunch of windows-only extensions and stuff too.

Fuck you. You are everything wrong with the software industry.