Please create an account to participate in the Slashdot moderation system


Forgot your password?

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).


Comment: Re:But... (Score 1) 255

by Yunzil (#49128041) Attached to: The Case Against E-readers -- Why Digital Natives Prefer Reading On Paper

But if you're actually trying to understand what an author is saying, and there's this word popping up a dozen times that you don't know, simply guessing what it means is missing an opportunity to learn something.

Or, you know, you could actually think about what you're reading and deduce the definition of the word from the context.

Comment: Re:Mostly right. (Score 1) 673

by Yunzil (#49114179) Attached to: Bill Nye Disses "Regular" Software Writers' Science Knowledge

This is just a lot of stupid nitpicking. Oh sure, if you want to get into graduate-level details, then if you say the earth goes around the sun you're wrong. But you're not nearly as wrong as if you say it's the other way around.

Education is the process of telling smaller and smaller lies.

Comment: Re:It's GOTOs all the way down (Score 1) 677

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

You're kinda entirely missing the point of structured programming. In your other examples, the goto is constrained. The return statement is a goto back to the call of the function. The if statement is a goto to either the inside of the block or the end of the block.

What Dijkstra was complaining about was unrestricted gotos. If you can goto anywhere in the code willy-nilly then it becomes much harder for someone reading your code to follow your logic. And it becomes much harder for you to follow your own logic when you inevitably have to come back to the code a year later.

No problem is insoluble in all conceivable circumstances.