Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - GNU Hurd 0.6 Released->

Submitted by jrepin
jrepin (667425) writes "It has been roughly a year and a half since the last release of the GNU Hurd operating system, so it may be of interest to some readers that GNU Hurd 0.6 has been released along with GNU Mach 1.5 (the microkernel that Hurd runs on) and GNU MIG 1.5 (the Mach Interface Generator, which generates code to handle remote procedure calls). New features include procfs and random translators; cleanups and stylistic fixes, some of which came from static analysis; message dispatching improvements; integer hashing performance improvements; a split of the init server into a startup server and an init program based on System V init; and more."
Link to Original Source

+ - New Descent on Kickstarter, for Linux!->

Submitted by elfindreams
elfindreams (1824696) writes "Several of the Star Citizen team have separated out and are re-birthing Descent, the original 6doF space shooter. It will be being released as a PC/Mac/Linux game and will include a single player campaign and multiplayer with up to 64 combatants on a map!

They are working with a number of members of the current D1/D2 community to make sure the flight/gameplay feels "old school" and they are updating the technology and game to a new generation.

Head to the kickstarter to get your descent on or read more about it on the ars technica article (http://arstechnica.com/gaming/2015/03/classic-fps-descent-to-be-rebooted-by-star-citizen-alums/)."

Link to Original Source

+ - SimCity's Empire Has Fallen and Skylines Is Picking Up the Pieces->

Submitted by sarahnaomi
sarahnaomi (3948215) writes "Mariina Hallikainen, CEO of small Finnish game developer Colossal Order, is having a good day. When I call her, it's only been a few hours since she learned that Colossal Order's SimCity-like game, Cities: Skylines, has sold more than half a million copies in its first week. The first 250,000 of those were sold in the first 24 hours, making it the fastest-selling game its publisher Paradox Interactive has ever released.

The irony here doesn't escape Hallikainen. Only a week before Skylines was released, game publisher Electronic Arts announced that it was shutting down SimCity developer Maxis' studio in Emeryville, which it acquired in 1997.

"I feel so bad about Maxis closing down," Hallikainen said. "The older SimCitys were really the inspiration for us to even consider making a city builder."

At the same time, Hallikainen admits SimCity's mistakes were Colossal Order's opportunity. "If SimCity was a huge success, which is what we expected, I don't know if Skylines would have ever happened," she said, explaining that it would have been a harder pitch to sell to Paradox if the new SimCity dominated the market."

Link to Original Source

Comment: Re:Well, yeah (Score 1) 677

by rujasu (#49081279) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

Has nothing to do with "holy prophets" or anything like that. I've done programming with and without goto, and goto is (usually) bad. I knew this before I ever heard of Dijkstra.

The study says that goto has not been a problem BECAUSE it is not being used inappropriately. Inappropriate use is exactly what Dijkstra cautioned against. So the study isn't saying anything other than that people did exactly what Dijkstra suggested they should do.

Comment: Re:Well, yeah (Score 1) 677

by rujasu (#49046887) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

Stop teaching students to avoid goto so that it takes hold again, leading to bad code all over the place, so that we can empirically prove that it's a bad idea? How about we just don't do that and avoid the problem to begin with.

Unrestrained use of goto was demonstrated to be a bad idea decades ago, that's why Dijkstra recommended against it in 1968.

Comment: Re:Well, yeah (Score 1) 677

by rujasu (#49042381) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

The point is that people do not generally use goto in these harmful ways because they've been warned not to. That's what skews the study in the summary. You're going to have a hard time finding that empirical evidence of how goto can lead to bad code, because one of the first things coders are taught in today's programming courses is, "Do not use goto." Meaning that the inexperienced coders who would be having these problems are avoiding the problem by not using goto. Those who are using goto are those who know the risks and how to mitigate them.

So, in the absence of conclusive data either way, I can only argue from my experience. I'm a programmer who has used both goto and more tightly-controlled flow control, and in my experience goto is not a good option for the vast majority of cases (particularly for inexperienced coders).

Comment: Re:all languages can be abused (Score 1) 677

by rujasu (#49040441) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

Not sure what you're getting at with compilers. Once you translate a C program to assembler/machine code, most of your loops, switches, breaks, etc. all become effectively the same as goto. The problem with goto has nothing to do with the compiler, it has to do with the human being trying to read, write, and debug the code before it goes through the compiler, and with catching errors at compile-time with sane control flow, whereas with goto it will make it through the compiler and become a runtime error.

You complain about the giant if/for nests, but those huge nests will almost always become worse if you start throwing gotos in there.

Yes, goto is a tool like anything else. But it is not a tool for the common case or the common coder. Most of the time, if you're asking yourself, "should I use goto here or something else?" the answer is the something else.

Comment: Re:Well, yeah (Score 1) 677

by rujasu (#49040277) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

If you think modern code is horrible spaghetti (I disagree, for the record), bear in mind that it would be considerably worse with indiscriminate use of goto.

Sure, code has complex code flow. When code is designed to solve complex problems, it's going to be complex. Complexity is okay. The key is being able to make complex code clear, readable, and less error-prone. Goto is less clear and readable because it's not obvious what a goto statement is meant to do. When you see a while loop, or a break statement, or a function call, you can get an idea of what it's doing just by the nature of what statement is being used. Goto can be used to cover any of those cases, so it's more difficult to follow. Because of this, it's also easier to make a difficult-to-debug mistake!

99% of the time, when you could use a goto statement in code, there is another, better way of doing the same thing. An expert coder will be able to effectively use it in a way that limits the risk, but for a novice or intermediate coder, or even many experienced ones, it is much easier to muck everything up using goto vs. using other control flow tools.

+ - $10K Ethernet Cable Claims Audio Fidelity, If You're Stupid Enough To Buy It->

Submitted by MojoKid
MojoKid (1002251) writes "There are few markets that are quite as loaded-up with "snake oil" products as the audio/video arena. You may have immediately thought of "Monster" cables as one of the most infamous offenders. But believe it or not, there are some vendors that push the envelope so far that Monster's $100 HDMI cables sound like a bargain by comparison. Take AudioQuest's high-end Ethernet cable, for example. Called "Diamond," AudioQuest is promising the world with this $10,500 Ethernet cable. If you, for some reason, believe that an Ethernet cable is completely irrelevant for audio, guess again. According to their claim: "AudioQuest's Diamond RJ/E is a directional Ethernet cable made with the same hallmark materials, philosophy, care and attention that is applied to all their interconnects, whether it's an entry level introduction to Hi-Fi or a died-in-the-wool music connoisseur. Another upgrade with Diamond is a complete plug redesign, opting for an ultra-performance RJ45 connector made from silver with tabs that are virtually unbreakable. The plug comes with added strain relief and firmly lock into place ensuring no critical data is lost." It's too bad AudioQuest limits itself to just audio, because descriptions like that would prove a welcome sight in other markets. Just imagine how tempting it would be to own 100% solid paper clips made with uncompromising materials that take a no-nonsense approach to holding paper together. Unfortunately, in this case, there's the issue of digital data being, well, digital. But hey, a 1 or a 0 could arrive at its destination so much cleaner, right?"
Link to Original Source

Comment: Re:Nah, they're just thinking ahead... (Score 1) 191

by rujasu (#49020495) Attached to: Microsoft Trademarks "Windows 365"

Nah, I think it's clear that Microsoft is not counting in decimal like the rest of us. Sure, they start with 1, 2, 3 like you'd expect, but then after that it's 3.1, 3.11, 95, 98, 2000, XP, Vista, 7, 8, 10, 365. The next version will be something like 13.111.Xylophone. This is not Base 10. This is Base Bob.

fortune: cannot execute. Out of cookies.

Working...