Comment "customers's" (Score 1) 134
I know, spelling/grammar police and all, but boy does that make me twitch.
I know, spelling/grammar police and all, but boy does that make me twitch.
In cases where a project is no longer actively being maintained, SourceForge has in some cases established a mirror of releases that are hosted elsewhere. This was done for GIMP-Win.
Editor's note: Gimp is actively being maintained and the definition of "mirror" is quite misleading here as a modified binary is no longer a verbatim copy. Download statistics for Gimp on Windows show SourceForge as offering over 1,000 downloads per day of the Gimp software. In an official response to this incident, the official Gimp project team reminds users to use official download methods. Slashdotters may remember the last time news like this surfaced (2013) when the Gimp team decided to move downloads from SourceForge to their own FTP service.
Therefore, we remind you again that GIMP only provides builds for Windows via its official Downloads page.
Note: SourceForge and Slashdot share a corporate parent.
My understanding was that DNT has mostly been a failure, though I don't know how much of that has to do with IE's default behavior. Am I wrong about that? Are there lots of sites out there honoring the DNT setting?
Glad I wasn't the only one thinking this.
Some states in the US allow you to choose your electricity provider - it's still coming down the utility company's power lines regardless, but you can buy from a different company.
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.
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.
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).
And why do you think this is bad practice?
(1) Never draw what you can copy. (2) Never copy what you can trace. (3) Never trace what you can cut out and paste down.