I already went and found the setting to turn it off before this story was posted. FYI it's under your Preferences->Homepage tab. Since the columns only have little pictures instead of headings (not even alt text), I can only tell you to click the 2nd radio button from the left.
Supporting imake and autotools in what is essentially the same codebase seems pretty impressive. Just one build system generally is cause for enough hair-pulling to make even RMS go bald. Shouldn't we be offering kudos to the x.org folks?
It's a clever idea and all, but wouldn't it be simpler to just throw out some tarps?
OK, they'd need a bit more than some blue plastic, but really, I'm sure enough lightweight, ultraviolet resistant, tough modern technical fibers material to cover a fair space could easily be taken up for the weight and size of this "lawnmower" idea.
Totally agree. The businesses signing on seem to be doing so to try to dump their pet marketecture into Eclipse. Look at the projects page: Business Intelligence and Reporting Tools (BIRT) Project? Let's be sure they are at worst plug-ins and never part of the core.
News flash: companies and the senior managers that run them are psychopathic. As long as you keep that in mind and manage your relationship with them the same was as you'd manage your interactions with Hannibal Lector, you'll avoid serious trauma.
As a consultant on a DHS project in Salem (I'm a resident of Portland and commute), I can also say that open source is definitely used where it makes sense. But it's never easy to get in the door, and the official line is that OSS is not permitted.
I have yet to see a penguin or a devil doing any of the work in anything associated with this work, though.
How quickly we forget, Oregon schools tried to go open source and got the smackdown by Microsoft's lobbyists. No, this state government is NOT in the lead on the use of open source.
That's basically my conclusion -- posturing by politicians so they can claim they have an energy policy, when really they're doing whatever the oil and automobile industry lobbyists pay them to do.
This change is intended to save the country energy (and presumably keep energy costs lower). It's a bit of a stretch to believe it will really have any effect. Gadgets being out of sync and operating systems failing to keep accurate time will be inconvenient at best. By the time we add up the cost of writing, shipping, and installing patches or just compensating for the incorrect times, does anyone really believe we'll end up with a net savings? Won't the programmers and hardware guys who have to work extra hours to develop fixes easily eat up the supposed difference?
Write intention-revealing code. Use meaningful identifiers. Write with the maintenance programmer in mind. Code is write-once, read-many. In the days of low-level programming languages and maximum identifier length, comments were at least necessary to explain WTF a PLGRNX1 means. With modern development tools, you don't even have to type out the whole identifier after the first time, you can use code completion.
Too many comments makes me wonder why the programmer couldn't write clearer code.
People with CS degrees seem to get jobs writing software for money without knowing a thing about security, testing, defect discovery and removal, team organization, refactoring, design, technical writing, communication, estimating, abstractions and complexity management, business practices, communicating with users... well, anything needed to actually deliver working software that delivers value to the business.
But, you know, in case that trucking company struggling with logistics needs to know about "turing complete", "Karnaugh map", "Rice's theorem", "Goedel's completeness theorem", "planar graph", "functional language", "church-turing thesis", they're golden.
The commentor and OP are confusing Java and Javascript. The two share a C-like syntax, that is all. The only reason they even have a confusing name is because Netscape renamed Livescript at the same time the Java-for-applets alliance with Sun was driving the browser. Brendan Eich probably wishes he could have a do-over on that one.
If you knew what you were talking about, you'd know it was javac that does that, not Ant. In fact, Ant has the task that helps address the shortcomings of javac.
My recommendation: Style: Toward Clarity and Grace, by Joseph M. Williams. The main lesson of his book is how to drag your writing out of the context of expert knowledge and assumptions in your head and into a form that communicates what you really meant to people who can't get inside your head.
Yes but. COBOL arrays, or as they are called, tables, are extremely simple. In fact they are barely above indexed addressing in assembly -- not surprising. They are nowhere near as powerful as the array type in modern languages, e.g. Ruby Arrays. In fact they don't really measure up to Java's array, which at least knows its own length.
That's the key I was getting at. In Windows, threads are the preferred tool, while in unix (or at least Linux specifically), processes can fufill a lot of the same needs. So it's really fair to ask, "why would you need threads?" for many applications.
Slashdot Mirror
I already went and found the setting to turn it off before this story was posted. FYI it's under your Preferences->Homepage tab. Since the columns only have little pictures instead of headings (not even alt text), I can only tell you to click the 2nd radio button from the left.
Supporting imake and autotools in what is essentially the same codebase seems pretty impressive. Just one build system generally is cause for enough hair-pulling to make even RMS go bald. Shouldn't we be offering kudos to the x.org folks?
Well at least now I'll finally be able to say to the young turks who love to produce bad code and come up the endless excuses to justify it: EAT ME!
Nicodemus says, "No comment."
On the other hand, you might want to Forget the debugger.
Please tell slashdotters the name of your startup so we can be sure our money does not get invested in that dead fish.
It's a clever idea and all, but wouldn't it be simpler to just throw out some tarps?
OK, they'd need a bit more than some blue plastic, but really, I'm sure enough lightweight, ultraviolet resistant, tough modern technical fibers material to cover a fair space could easily be taken up for the weight and size of this "lawnmower" idea.
Totally agree. The businesses signing on seem to be doing so to try to dump their pet marketecture into Eclipse. Look at the projects page: Business Intelligence and Reporting Tools (BIRT) Project? Let's be sure they are at worst plug-ins and never part of the core.
Dave Thomas' Code Kata.
Nevada won't be covered in sand and dust, it'll be covered with glass.
News flash: companies and the senior managers that run them are psychopathic. As long as you keep that in mind and manage your relationship with them the same was as you'd manage your interactions with Hannibal Lector, you'll avoid serious trauma.
As a consultant on a DHS project in Salem (I'm a resident of Portland and commute), I can also say that open source is definitely used where it makes sense. But it's never easy to get in the door, and the official line is that OSS is not permitted.
I have yet to see a penguin or a devil doing any of the work in anything associated with this work, though.
How quickly we forget, Oregon schools tried to go open source and got the smackdown by Microsoft's lobbyists. No, this state government is NOT in the lead on the use of open source.
That's basically my conclusion -- posturing by politicians so they can claim they have an energy policy, when really they're doing whatever the oil and automobile industry lobbyists pay them to do.
This change is intended to save the country energy (and presumably keep energy costs lower). It's a bit of a stretch to believe it will really have any effect. Gadgets being out of sync and operating systems failing to keep accurate time will be inconvenient at best. By the time we add up the cost of writing, shipping, and installing patches or just compensating for the incorrect times, does anyone really believe we'll end up with a net savings? Won't the programmers and hardware guys who have to work extra hours to develop fixes easily eat up the supposed difference?
"I'm grasping it, I'm pulling, it's coming out very easily," astronaut Stephen Robinson radioed.
Don't comment.
Write intention-revealing code. Use meaningful identifiers. Write with the maintenance programmer in mind. Code is write-once, read-many. In the days of low-level programming languages and maximum identifier length, comments were at least necessary to explain WTF a PLGRNX1 means. With modern development tools, you don't even have to type out the whole identifier after the first time, you can use code completion.
Too many comments makes me wonder why the programmer couldn't write clearer code.
Goedel fits in there because the incompleteness theory is not unlike Turing's incomputability problem.
People with CS degrees seem to get jobs writing software for money without knowing a thing about security, testing, defect discovery and removal, team organization, refactoring, design, technical writing, communication, estimating, abstractions and complexity management, business practices, communicating with users... well, anything needed to actually deliver working software that delivers value to the business.
But, you know, in case that trucking company struggling with logistics needs to know about "turing complete", "Karnaugh map", "Rice's theorem", "Goedel's completeness theorem", "planar graph", "functional language", "church-turing thesis", they're golden.
Congratulations to Erich, Richard, Ralph, and John. Great guys who made a contribution for the ages.
The commentor and OP are confusing Java and Javascript. The two share a C-like syntax, that is all. The only reason they even have a confusing name is because Netscape renamed Livescript at the same time the Java-for-applets alliance with Sun was driving the browser. Brendan Eich probably wishes he could have a do-over on that one.
If you knew what you were talking about, you'd know it was javac that does that, not Ant. In fact, Ant has the task that helps address the shortcomings of javac.
My recommendation: Style: Toward Clarity and Grace, by Joseph M. Williams. The main lesson of his book is how to drag your writing out of the context of expert knowledge and assumptions in your head and into a form that communicates what you really meant to people who can't get inside your head.
Yes but. COBOL arrays, or as they are called, tables, are extremely simple. In fact they are barely above indexed addressing in assembly -- not surprising. They are nowhere near as powerful as the array type in modern languages, e.g. Ruby Arrays. In fact they don't really measure up to Java's array, which at least knows its own length.
That's the key I was getting at. In Windows, threads are the preferred tool, while in unix (or at least Linux specifically), processes can fufill a lot of the same needs. So it's really fair to ask, "why would you need threads?" for many applications.