Testing thread about nothing (I'm trying to diagnose an LQ-related Firefox issue)
GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The one with the guy talking about using Knoppix at his university isn't complete, but I'll post the rest of it:
Quote:
Originally Posted by Computer Stupidities
My instructor saw me and said, "What are you doing? That's not Windows! That's a VIRUS, isn't it? I'm going to report you for malicious use of school computers!" My advisor, who is a Linux proponent and also the sysadmin at the time, apparently laughed him out of his office when he went to complain.
Yeah, I find that code with alot of comments between lines of code (and most code I find is commented that way) is almost unreadable for me, because it's hard to tell apart comments and code for me that way.
I like it when every block of code is preceeded by a block of comments, and/or for every few lines to have a comment on the same line after the code.
I remember when coding 1-2 solid code lines per day was the norm. That would be debugging and testing to insure the code was valid.
As for commenting code: I like to comment enough to refresh whenever I re-look at a piece days or even years later then I don't have to familiarize conditions or status within a code block. Even with good commenting I would sometimes need to work/look the code over again therefore good hinting does save time.
Old school coders still document and cannot understand why someone else doesn't. As for myself, I will document but only within the block not always by line unless the line has merit.
We used to have too write code tight. Today most coders don't, memory is cheap and the process is a lot faster. Most high level languages have made a lot of lazy programmers who don't care that much about tight efficient code. Some waste a lot of resource to details that could be addressed via a good coders toolbox. Which a lot of the coders today don't really maintain like older coders do or did.
Yeah, I find that code with alot of comments between lines of code (and most code I find is commented that way) is almost unreadable for me
Man, I hate that! It's done all too often with "example" code in tutorials (and/or example code with programs/APIs), probably so as to "explain each line as it's written".
Just give me the raw, uncommented code (or at least with very concise comments, no longer than about 4-5 words) and let me get the rest of the info from the tutorial text itself.
If that happens to me, either a) I'll delete the comments (assuming that's not where most of the tutorial text resides, ugh), or b) I'll just tune them out as best I can. I have blue italics for comments in gedit's syntax highlighting, which is easily tune-outable on a black background.
In fact, usually I'll re-type the code myself, manually, without the comments (if necessary).
Man, I hate that! It's done all too often with "example" code in tutorials (and/or example code with programs/APIs), probably so as to "explain each line as it's written".
I agree 100%. Whenever I come across code like that in a tutorial and can't find a better tutorial, I copy the code into an editor and manually delete every single comment. Suddenly the code is very easy to understand! A great example of this is the GTK+ tutorial.
I really wonder what the hell people are thinking when they write those.
I also hate it when every second line of code is a comment explaining what the next line does. I see this in some "real" programs, not just tutorials.
Code:
Good:
/*
This is what
the following
block of code does.
*/
foo(); // explain what foo and bar do
bar();
Bad:
// foo does this
foo();
// bar does this
bar();
The reason I tend to re-type the code is that sometimes I find I get a better understanding of what the code does if I simply type it out by hand; kind of like how when you write out your ideas, you tend to remember them better.
Plus which, I also get a slight feeling of guilt from just doing Ctrl-C Ctrl-V, so I also kind of change the variable/class/function names sometimes (while keeping the code consistent, of course). It helps me to learn the concepts behind the code, rather than just the code itself.
The reason I tend to re-type the code is that sometimes I find I get a better understanding of what the code does if I simply type it out by hand; kind of like how when you write out your ideas, you tend to remember them better.
Plus which, I also get a slight feeling of guilt from just doing Ctrl-C Ctrl-V, so I also kind of change the variable/class/function names sometimes (while keeping the code consistent, of course). It helps me to learn the concepts behind the code, rather than just the code itself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.