Few things that was tame for him. You must have a set of balls and be the ultimate narcissist to send code to Linus that does not even build.If you are stupid enough to try and ship code that does not build you should be perma banned from touching anything thing. Sounds like these people did not do a single test or had some ultra weird setup requiring vague modules,api to build right.
Linus Torvalds lashes devs who 'screw all the rules and processes' and send him 'crap'
Linux 4.11's first release candidate has been released, but not without a little friction after Linus Torvalds railed at the quality of some code sent his way during the merge process for the new update to the platform. Torvalds has a few gripes, writing that “if you cannot follow the simple merge window rules (this whole two- …
COMMENTS
-
-
Monday 6th March 2017 05:28 GMT Anonymous Coward
@kain
Assuming it actually happened.
I'm in no position to judge on that part but I do consider it a bit odd to read that someone wouldn't even test their own stuff. Making you all the more curious to who Torvalds is shouting at yet today this detail wasn't being shared. Even though he was previously all the more eager to directly address RedHat representatives and call them out for their horrid update. Yet now he choses to keep up anonymity?
I have no reason not to believe him, but it would have made more impact on me if he called out the people who actually did it.
In my opinion: seems some are good enough to be scolded at in public and some are special enough to be kept safe. Takes away the impact and reeks of double standards.
Of course: calling 'm out in public also gives the other party a platform to actually talk back.
-
Monday 6th March 2017 08:22 GMT Anonymous Coward
"If you are stupid enough to try and ship code that does not build"
Probably it does build somehow. On their systems exclusively. It looks Linux is undergoing the same issue Windows underwent some time in the past too - the arrival of lame developers. It happens to any platform as soon as it becomes widespread enough.
-
-
-
-
Monday 6th March 2017 11:13 GMT Doctor Syntax
Re: "If you are stupid enough to try and ship code that does not build"
"usually paid employees of the hardware maker."
And these are donated to Windows.
And if you look who contributes code to Linux it's mostly paid employees of H/W manufacturers or distro makers such as Red Hat.
Either both cases are charity or neither is. Is that beyond your understanding?
-
-
-
-
-
-
-
Monday 6th March 2017 02:59 GMT jonfr
Not surprise reaction from Linus
This is not a surprise from Linus, bugs do happen and due to complex Linux is something A not working with something E, G and D is hard to avoid at all. Lack of quality of code happens due to pressure and rushing things along, even if its just in rc builds.
Disclaimer: I'm not yet a programmer, but I've been looking into it as a next step in learning more about computers.
-
-
Monday 6th March 2017 10:33 GMT WatAWorld
Re: Grasshopper ...
"... allow me to impart some of the wisdom of the Ancient Coders: Do not begin to write code without first understanding full extent of the problem."
That is ideally true in the vast majority of cases, especially those with recently written in-house software at companies who've always had high quality staffing and procedures.
Then there are:
- The poor bastards stuck in shops where they're afraid to ask questions because they'll either be called stupid or ostracized as newbies.
- The poor bastards told to fix the current problem because it is urgent and that ramifications can be taken care of laster, and
- The poor bastards stuck in shops where most documentation was destroyed by people worried about their personal 'job security'.
More applicably to operating systems and massive shrink wrapped applications: There now there are systems installed in such a vast variety of companies all around the world, each using it for different purposes, different alphabets, each customizing it in their own way, each with different unforeseen needs, running on a vast variety of imperfect hardware, and then you'll realize that a detailed total understanding of the full extent of the problem is not always possible.
Understanding the full extent of the problem with mega complex massive multi-user software will come with sitting in your ashram chamber and accepting that your knowledge is not detailed that there will never be bug fixes, future releases and future versions.
You try to insist on get a sufficient understanding of the problem that you won't introduce bugs, while accepting that in such complex situations nothing is 100%.
(I think maybe that is how 'security researchers' see the world -- as a bunch of small shops with simple specs and simple human interactions, something that a human being can totally understand with a couple of months effort. That would explain why they think project scheduling, analysis, coding, unit testing, system integration testing, regression testing, beta testing and production roll-out, done over 15 countries with 45 different cultures and delivered to 137 countries in 55 languages should never take more than 90 days.)
-
Monday 6th March 2017 12:30 GMT Anonymous Coward
Re: Grasshopper ...
@WatAWorld
If the extend of the problem is unknowable, they should be clear on what problem they think they have solved, and what the gaps/risks are i.e. what they have not tried to solve.
I agree it is not always possible to understand everything when approaching a solution, but it is normally possible to frame your effort in what you are, and are not capable of achieving and what the constraints are.
-
-
-
-
Monday 6th March 2017 10:42 GMT Doctor Syntax
Re: Not surprise reaction from Linus
"Lack of quality code comes from getting your code second hand, built by people paid to fulfill some paying companies own project"
The biggest single contributor is usually Intel. Their "project" is the Intel processor line. Of course, given some recent experiences you may have a point....
https://www.theregister.co.uk/2017/03/03/netgear_recalling_hardware_with_bad_intel_atoms/
-
-
-
-
Monday 6th March 2017 07:06 GMT 9Rune5
Arguably, the amateurs who assembled your computer should have made sure that all the components came from respectable vendors supplying drivers for all major operating systems.
And the amateur buying said computer should have verified that the vendor was in the business of selling proper computers and not mere toys.
Good device drivers is mainly the hardware oems' responsibility. Many Windows installations have gone the way of the dodo due to dodgy third-party drivers. (MS writes very few drivers themselves)
-
-
-
Monday 6th March 2017 10:39 GMT Anonymous Coward
Re: "supplying drivers for all major operating systems"
Is Chrome Linux? Can you install and run any Linux software on Chrome? Google will of course write drivers for the Chrome hardware, getting all the needed info from the OEM, signing all the required NDAs, and maybe won't publish them either. Android too is not Linux, is a Google proprietary OS built on top of the Linux kernel.... just like macOS is not FreeBSD. There's a reason why the macOS driver framework is not the FreeBSD one...
-
-
-
-
Monday 6th March 2017 10:53 GMT Doctor Syntax
If and only if you are normally paid for your work are you a professional.
If you work for free you're an amateur.
Could you explain a little further.
Are the devs working for Intel being paid or not? Assuming they are that makes them professionals. Intel donates their work to the Linux kernel for free. Does that make them amateurs?
-
Monday 6th March 2017 11:20 GMT WatAWorld
"Are the devs working for Intel being paid or not? Assuming they are that makes them professionals. Intel donates their work to the Linux kernel for free. Does that make them amateurs?"
As covered in one of my other posts in this topic: The amature contributions to Linux and then the professional contribution to Linux.
The amateurs work for free, for experience or as part of class work.
The Intel, AMD, nVidia, etc developers are professionals paid by their employers. So are the developers working for banks, governments, consulting firms, and other companies that donate code to Torvalds.
Those professionals are employed by those other companies, not Linux.
With some exceptions, the objectives of the projects they are working on are not to improve Linux, but rather to get THEIR product to work with Linux, or to change Linux so it will play nice with THEIR internal app, or to eliminate some bug in Linux that affects their company and their clients.
- Their jobs are to fulfill the needs of their employer and their employer's clients.
- Their loyalty is to their employer and their employer's clients.
- They surely don't want to hurt Linux. They probably all want to play nice, because of professionalism and so their companies aren't banned.
- But their loyalties and objectives are not to make sure that Linux runs fine and bug free on obscure stuff at other companies. When their boss assigns them to a new project, regression testing of the old project ends.
So this stuff is created so Linux will work with their equipment or their internal applications, and it is donated to Linux for free. It is written by them so their stuff will work. And they're donating it to Torvalds for free. Even if it has bugs, it is arguably worth the price Torvalds pays for it.
Is Torvalds not even giving them a registered charity donation receipt so they can claim their effort on their income taxes?
-
Monday 6th March 2017 11:34 GMT Doctor Syntax
"With some exceptions, the objectives of the projects they are working on are not to improve Linux, but rather to get THEIR product to work with Linux, or to change Linux so it will play nice with THEIR internal app, or to eliminate some bug in Linux that affects their company and their clients."
Upvoted because this is actually an interesting comment.
The point at which I think we diverge is this: you're seeing Linux as something separate from these contributors (and here I'm including the employers such as Intel as contributors), as some external product which they have to improve.
I think you're looking at it wrong. Linux is, collectively, their product. Torvalds could step away from it today and people (including those companies) would still go on contributing because they see it as worth their while to have that product there and continuing to evolve.
One other interesting aspect of all this discussion is the role of the companies who contribute vs those who don't. If some H/W manufacturers such as Intel find it essential to contribute to Linux by sharing IP what, really, does it say about the self-image of those who seem to think it essential not to? Do they really think they know something Intel doesn't? Or do they not know something Intel does? Or, as someone said in another comment, are they ashamed of the quality of their code?
-
-
-
This post has been deleted by its author
-
-
-