I'm running hoary, not warty, so I'm not sure if it makes a huge difference... Especially since Hoary is slated to be released April 6th or thereabouts.
However, I can go to system->keyboard layout and select any damned keyboard layout I want from the list.
There's some valid bitches about Ubuntu, but that isn't one. Try upgrading your system, you might be amazed at what is out there. Hoary is quite a bit more polished than warty. It's also relatively trivial to upgrade from warty to hoary.
Oh, and as for working KDE as well? Again, update your system and try the kubuntu-desktop meta package.
Not sure what you're talking about, but I haven't posted anything as an AC. Nice jump to conclusions *again*.
And last time I checked, I haven't been writing code for you to review, so you're really reaching when you say "inability to write legible code". You're definitely qualified to make such an assumption, having seen zero lines of my code.
But... thanks for playing (and yes, I'm nearly 40, and have been doing this for 20 years, so again you are quite wrong).
Nice try. However, I assure you I am definitely old enough. Sometimes I wish I weren't. My back frequently thinks I'm quite a bit *older* than that as well.
Oh, and us codgers use the word "fuck" too. Your generation didn't invent sex, swearing or any other sins either. Get over yourself already... or at least get a better set of Tarot cards because your "jumping to conclusions" skills definitely need a leg up.
No, you're adopting a black or white approach. You are, in essence, saying that you don't need to comment at all. The original poster was saying that comments needed to be everywhere, on everything. I believe in a middle ground approach.
I comment things that are non intuitive. I comment things that I *think* may be non intuitive. I comment things that I think someone else might have some difficulty understanding, because I happened to be deep into a code burn and consequently wrote something pretty tight, pretty sweet, but also pretty obfuscated. Finally, I comment things that I think *I* may not understand when I go back and look at the code again 3 months from now.
I don't comment every single line... I don't comment simple data structures, loops "/* this is a for loop using the integer variable I */" etc which would be stupid. I do however disassemble the complex portions of my code, describe how I'm dispatching events and best of all *why* I decided to do things a certain way instead of a different way.
I have, however, been handed 30k lines of code with zero documentation and not a single comment anywhere in it, with absolutely no clue at all how it worked and no access to the original programmer and been told "We need such and such fixed|updated|added by friday" and had to spend the entire week basically tracing every single line of code to figure out that the original programmer must have been smoking crack with NO indication of why he wrote things how he did and NO help when he decided to be exceedingly "clever" in his code. That time was wasted.
Would it have killed him to simply put a comment block explaining his event dispatch model? Or to tell me what his functions and methods did and best of all why they did it?
Lol I left school long long ago, nice to pull that assumption out of your butt though and further that ego.
Those of us that actually get *paid* to program every day (and have been programming for 20 years or so) don't have time to waste picking apart your 200k lines of spaghetti code because you were too important and too macho to be bothered to put a few comments in. Some day you'll grow up and kick that nasty "I'm so important" habit. Here's a clue... the phrase "it was hard to write, it should be hard to read" is *sarcasm*, not a truism.
Oh, and I wouldn't work for you anyway. I carefully assess jobs and potential employers, and when they say "oh, we don't have to comment our code" I either take a contracting assignment so I can make the big $$$ fixing all their "perfect" code so that it actually works _or_ I happily go on to an employer who has actually been through puberty and understands that people actually need to *maintain* code and plan accordingly.
But hey, thanks for worrying about my employment status. If you're ever looking for a job, I'd give you a fair assessment, but I guarantee you if you bragged to me about not having to comment your code you'd be getting a complimentary cheez doodle, a bent business card and a "we'll be in touch".
Bullshit. He's spot on in many cases (although admittedly a tad overzealous).
Comments should be used LIBERALLY, albeit intelligently as well. If you do something that isn't intuitively obvious to even the most casual observer, just take 30 seconds to write a fucking COMMENT explaining why you did what you did.
Believe it or not, eschewing comments because "oh, well, if you want to understand it just read the code" just pisses those of us off who have to come along and clean up your miserable excuse for a codebase... and it sure as hell doesn't prove how studly a programmer you are.
That doesn't mean half your codebase should be comments, but it does mean that you should at least make a passing nod to demystifying your own attempts at cleverness. I have lots of better things to do than to spend all fucking day picking apart your rabbit's nest of code before I can make a change, add a feature or fix a bug.
People that honestly believe that "if it's well written it doesn't NEED comments" should be strangled with their mousecord and hung in their cubicles as a warning to the rest.
Some guy forks an *entire* codebase... presumably several KLOC. That's fine, it happens a lot and is to be expected. Nothing wrong with that at all.
Now, this guy gets all pissy because you integrate small sections of the new code into your *own* codebase? He has the audacity to bitch when you reuse small chunks after he's "liberated" an ENTIRE codebase? Hell, I'm *delighted* when someone reuses part of my code, and I've liberated code from other people on plenty of occasions as well. When someone else does something well, the best way I can say "thank you" and "wow that kicks ass" is to liberate it (with proper attribution of course) and propagate it in my own code.
(ok, maybe the BEST way is to FTP them a sixpack of beer but I'm still working on the matter transmission libraries so that's not an option atm).
Tell the guy to go piss up a rope. The thing that kills good Open Source projects the quickest is prima donna pain in the ass people with egos the size of montana who think the rules don't apply to them. Someone should lock him in a room with a copy of the GPL and not let him out until he fully groks it.
I got laid off back in 2001 from Sun Microsystems. I spent the last 3 years bouncing around doing the occasional contract work, fixing people's computers for cash, and doing whatever other work I could find (including working in a coffee shop and painting houses). I took the last year off and went back to school, and left the bay area because the job market was so bad.
I returned in July, and immediately noticed the job market was picking up. There were a lot more positive responses to the resumes I sent out, as well as a lot more places to *send* a resume in general. I started reconnecting with my personal network (people, not machines) and fairly quickly landed a new job at Ebay. I got this via my personal network, although I was getting several positive bites on my resume from all different sources as well.
The job market in the bay area is *definitely* starting to pick up. It behooves you, however, to not rely totally on just online job searches. Get your butt out of your chair, put the cheetohs down and beat the bushes the good old fashioned way.
It's not my problem to come up with a solution for *everyone*. Contrary to what you may think, this is not an entitlement society.
If you can afford a PC and are worried about playback on it, surely you can afford a $70 standalone DVD player. If not, don't watch the damned things or rip them to AVI (uh wow, there's a solution to your hard drive space too).
In that case, I just simply rip the damned thing to my hard drive and play it from there... or (gasp) play it in a standalone DVD player hooked to my 42" wide screen LCD projection TV./shrug
Maybe not, but you can indeed gauge effectiveness using another metric.
Has ANYONE that received a C&D been using SafePeer or any of it's kin? Let's hear from the letter receivers... any of you want to confess to computing without a condom?
If, in fact, you see a pretty equal percentage of AP2P users and non AP2P users getting letters, then I would indeed say it's not effective. If, however, you see a marked difference then you can say otherwise.
Without numbers or anecdotal evidence it's all just opinions... and we all know what opinions are like.
That addresses the first part of the issue, but it still leaves the second part hanging. I really don't believe simply having your IP in the list is enough, I believe they have to then connect to your system and verify that you are indeed sharing the content. I know this was definitely the case with the more traditional P2P networks, they would first cruise the search lists, then they'd have to physically connect to your machine and verify that you were sharing it out. Of course, they didn't verify the *content* in some cases, they only went on the file name and hash, but they most definitely *did* have to connect and verify first.
If that weren't the case, they'd be sending out a hell of a lot more than 200 letters the first day. They'd get 200 from just grabbing the IP list for a crappy movie like Gigi.
Only if they compromise the tracker... and simply knowing you are in the swarm isn't enough to back up a C&D afaik. I think they have to actually connect to you and verify. Of course, IANAL. YMMV. Yada yada, badda bing badda boom.
Why oh why would you not P2P without a condom? BT Plugins like SafePeer (for Azureus) or applications like Protowall use blacklists from places like Bluetack to filter out known *AA addresses, among others. I don't really know how effective they are, but I'd be curious to hear from people that use them and still get C&D's. I have heard of plenty of people getting C&D's but those people weren't using condoms.
YMMV of course. I'm not advocating digital theft, nor am I criticizing it. I'm just curious as to why people aren't protecting themselves. Maybe I'm just fooling myself that they work at all, but I'd like to think they do.
I've had a karma for about a year. I love it. I have had ZERO lockups, even when I take it out rollerblading with me (which admittedly is probably a lot less pounding than jogging, except when I'm skating stairs I guess). Of course, the very first thing I did was upgrade the firmware, and I keep it current. I've *never* had to whack my player.
I like the iPod. It's a slick unit, and Apple does a good job of interface design. I also like the karma. It's made by the same dev team that made the Empeg (which I also have) and they *still* support the empeg with updates even though it's been EOL'd a long time ago.
The Karma is not big and bulky, nor is it "chunky" and only a moron would think so. it's more square than the iPod, a bit thicker but not as tall. It fits just fine in my pocket, fits perfectly in my hand and has a good button layout and interface design. Both the iPod and the Karma are easy to use, just in different ways.
It finally came down to one factor for me... Ogg capabilities. I already have about 30 gig of music encoded in Ogg format (which my empeg also plays just fine). I'm not about to transcode everything, or worse yet go through the hell of reripping everything.
Feature for feature, the iPod and the karma are fairly close. I think they are both good products. I prefer both of them over the iRiver and other players, based purely on aestethics and form factor. It comes down to just these 2 players for me, and since only one of them plays Ogg, the Karma is the only possible solution for me. If the iPod played Ogg format, it would be a much tougher choice but Apple seems to be stubbornly refusing to acknowledge the desire or need for this format in their product.
I recommend using the latest releaes of JEmplode with it. There's an updated Emplode in the alpha firmware package, but it's rather flakey and JEmplode seems to be quite a bit stabler (and runs on Linux).
Not really. 30 gig Mk2 units are going in the 500 to 600 dollar range. That's hardly "the price of their college education" unless of course you're sending them to clown college.
The neuros uses a backpack hard drive though, which radically increases it's form factor.
Rio just released the Karma with Ogg support. Done by the same team that did the empeg, from what I understand. I haven't tested out a karma yet but I definitely love my empeg and if it's half as good it's much better than anything else.
Slashdot Mirror
I'm running hoary, not warty, so I'm not sure if it makes a huge difference... Especially since Hoary is slated to be released April 6th or thereabouts.
However, I can go to system->keyboard layout and select any damned keyboard layout I want from the list.
There's some valid bitches about Ubuntu, but that isn't one. Try upgrading your system, you might be amazed at what is out there. Hoary is quite a bit more polished than warty. It's also relatively trivial to upgrade from warty to hoary.
Oh, and as for working KDE as well? Again, update your system and try the kubuntu-desktop meta package.
-- Gary F.
Not sure what you're talking about, but I haven't posted anything as an AC. Nice jump to conclusions *again*.
And last time I checked, I haven't been writing code for you to review, so you're really reaching when you say "inability to write legible code". You're definitely qualified to make such an assumption, having seen zero lines of my code.
But... thanks for playing (and yes, I'm nearly 40, and have been doing this for 20 years, so again you are quite wrong).
-- Gary F.
Nice try. However, I assure you I am definitely old enough. Sometimes I wish I weren't. My back frequently thinks I'm quite a bit *older* than that as well.
Oh, and us codgers use the word "fuck" too. Your generation didn't invent sex, swearing or any other sins either. Get over yourself already... or at least get a better set of Tarot cards because your "jumping to conclusions" skills definitely need a leg up.
-- Gary F.
No, you're adopting a black or white approach. You are, in essence, saying that you don't need to comment at all. The original poster was saying that comments needed to be everywhere, on everything. I believe in a middle ground approach.
I comment things that are non intuitive. I comment things that I *think* may be non intuitive. I comment things that I think someone else might have some difficulty understanding, because I happened to be deep into a code burn and consequently wrote something pretty tight, pretty sweet, but also pretty obfuscated. Finally, I comment things that I think *I* may not understand when I go back and look at the code again 3 months from now.
I don't comment every single line... I don't comment simple data structures, loops "/* this is a for loop using the integer variable I */" etc which would be stupid. I do however disassemble the complex portions of my code, describe how I'm dispatching events and best of all *why* I decided to do things a certain way instead of a different way.
I have, however, been handed 30k lines of code with zero documentation and not a single comment anywhere in it, with absolutely no clue at all how it worked and no access to the original programmer and been told "We need such and such fixed|updated|added by friday" and had to spend the entire week basically tracing every single line of code to figure out that the original programmer must have been smoking crack with NO indication of why he wrote things how he did and NO help when he decided to be exceedingly "clever"
in his code. That time was wasted.
Would it have killed him to simply put a comment block explaining his event dispatch model? Or to tell me what his functions and methods did and best of all why they did it?
There *is* a middle ground, believe it or not.
-- Gary F.
Lol I left school long long ago, nice to pull that assumption out of your butt though and further that ego.
Those of us that actually get *paid* to program every day (and have been programming for 20 years or so) don't have time to waste picking apart your 200k lines of spaghetti code because you were too important and too macho to be bothered to put a few comments in. Some day you'll grow up and kick that nasty "I'm so important" habit. Here's a clue... the phrase "it was hard to write, it should be hard to read" is *sarcasm*, not a truism.
Oh, and I wouldn't work for you anyway. I carefully assess jobs and potential employers, and when they say "oh, we don't have to comment our code" I either take a contracting assignment so I can make the big $$$ fixing all their "perfect" code so that it actually works _or_ I happily go on to an employer who has actually been through puberty and understands that people actually need to *maintain* code and plan accordingly.
But hey, thanks for worrying about my employment status. If you're ever looking for a job, I'd give you a fair assessment, but I guarantee you if you bragged to me about not having to comment your code you'd be getting a complimentary cheez doodle, a bent business card and a "we'll be in touch".
-- Gary F.
Bullshit. He's spot on in many cases (although admittedly a tad overzealous).
Comments should be used LIBERALLY, albeit intelligently as well. If you do something that isn't intuitively obvious to even the most casual observer, just take 30 seconds to write a fucking COMMENT explaining why you did what you did.
Believe it or not, eschewing comments because "oh, well, if you want to understand it just read the code" just pisses those of us off who have to come along and clean up your miserable excuse for a codebase... and it sure as hell doesn't prove how studly a programmer you are.
That doesn't mean half your codebase should be comments, but it does mean that you should at least make a passing nod to demystifying your own attempts at cleverness. I have lots of better things to do than to spend all fucking day picking apart your rabbit's nest of code before I can make a change, add a feature or fix a bug.
People that honestly believe that "if it's well written it doesn't NEED comments" should be strangled with their mousecord and hung in their cubicles as a warning to the rest.
-- Gary F.
Holy shit, I know RMS is influential, the father of the FSF and the GPL and all that, but now he's a TV producer?
psst... it's J M S. Leave your nerd card at the door on your way out.
-- Gary F.
Ok, let me see if I understand this correctly...
Some guy forks an *entire* codebase... presumably several KLOC. That's fine, it happens a lot and is to be expected. Nothing wrong with that at all.
Now, this guy gets all pissy because you integrate small sections of the new code into your *own* codebase? He has the audacity to bitch when you reuse small chunks after he's "liberated" an ENTIRE codebase? Hell, I'm *delighted* when someone reuses part of my code, and I've liberated code from other people on plenty of occasions as well. When someone else does something well, the best way I can say "thank you" and "wow that kicks ass" is to liberate it (with proper attribution of course) and propagate it in my own code.
(ok, maybe the BEST way is to FTP them a sixpack of beer but I'm still working on the matter transmission libraries so that's not an option atm).
Tell the guy to go piss up a rope. The thing that kills good Open Source projects the quickest is prima donna pain in the ass people with egos the size of montana who think the rules don't apply to them. Someone should lock him in a room with a copy of the GPL and not let him out until he fully groks it.
-- Gary F.
I got laid off back in 2001 from Sun Microsystems. I spent the last 3 years bouncing around doing the occasional contract work, fixing people's computers for cash, and doing whatever other work I could find (including working in a coffee shop and painting houses). I took the last year off and went back to school, and left the bay area because the job market was so bad.
I returned in July, and immediately noticed the job market was picking up. There were a lot more positive responses to the resumes I sent out, as well as a lot more places to *send* a resume in general. I started reconnecting with my personal network (people, not machines) and fairly quickly landed a new job at Ebay. I got this via my personal network, although I was getting several positive bites on my resume from all different sources as well.
The job market in the bay area is *definitely* starting to pick up. It behooves you, however, to not rely totally on just online job searches. Get your butt out of your chair, put the cheetohs down and beat the bushes the good old fashioned way.
-- Foz
It's not my problem to come up with a solution for *everyone*. Contrary to what you may think, this is not an entitlement society.
If you can afford a PC and are worried about playback on it, surely you can afford a $70 standalone DVD player. If not, don't watch the damned things or rip them to AVI (uh wow, there's a solution to your hard drive space too).
-- Foz
In that case, I just simply rip the damned thing to my hard drive and play it from there... or (gasp) play it in a standalone DVD player hooked to my 42" wide screen LCD projection TV. /shrug
-- Foz
Sorry, but that's just an ignorant statement. Have you even LOOKED at bluetack?
/. Of course not. It's easier just to throw rocks.
Oh wait, I forget, this is
-- Palis
Maybe not, but you can indeed gauge effectiveness using another metric.
Has ANYONE that received a C&D been using SafePeer or any of it's kin? Let's hear from the letter receivers... any of you want to confess to computing without a condom?
If, in fact, you see a pretty equal percentage of AP2P users and non AP2P users getting letters, then I would indeed say it's not effective. If, however, you see a marked difference then you can say otherwise.
Without numbers or anecdotal evidence it's all just opinions... and we all know what opinions are like.
-- Foz
That addresses the first part of the issue, but it still leaves the second part hanging. I really don't believe simply having your IP in the list is enough, I believe they have to then connect to your system and verify that you are indeed sharing the content. I know this was definitely the case with the more traditional P2P networks, they would first cruise the search lists, then they'd have to physically connect to your machine and verify that you were sharing it out. Of course, they didn't verify the *content* in some cases, they only went on the file name and hash, but they most definitely *did* have to connect and verify first.
If that weren't the case, they'd be sending out a hell of a lot more than 200 letters the first day. They'd get 200 from just grabbing the IP list for a crappy movie like Gigi.
-- Foz
Only if they compromise the tracker... and simply knowing you are in the swarm isn't enough to back up a C&D afaik. I think they have to actually connect to you and verify. Of course, IANAL. YMMV. Yada yada, badda bing badda boom.
-- Foz
Why oh why would you not P2P without a condom? BT Plugins like SafePeer (for Azureus) or applications like Protowall use blacklists from places like Bluetack to filter out known *AA addresses, among others. I don't really know how effective they are, but I'd be curious to hear from people that use them and still get C&D's. I have heard of plenty of people getting C&D's but those people weren't using condoms.
YMMV of course. I'm not advocating digital theft, nor am I criticizing it. I'm just curious as to why people aren't protecting themselves. Maybe I'm just fooling myself that they work at all, but I'd like to think they do.
-- Foz
The Azureus BT client has the SafePeer plugin that does this. I have no idea how effective it is. I use it, I hope it's working :)
-- Foz
Ok, maybe I'm being a bit naive, but are you people who are getting C&D letters using SafePeer or an equivalent? And if not, why not?
Or is SafePeer just proving to be ineffective?
-- Gary F.
I've had a karma for about a year. I love it. I have had ZERO lockups, even when I take it out rollerblading with me (which admittedly is probably a lot less pounding than jogging, except when I'm skating stairs I guess). Of course, the very first thing I did was upgrade the firmware, and I keep it current. I've *never* had to whack my player.
I like the iPod. It's a slick unit, and Apple does a good job of interface design. I also like the karma. It's made by the same dev team that made the Empeg (which I also have) and they *still* support the empeg with updates even though it's been EOL'd a long time ago.
The Karma is not big and bulky, nor is it "chunky" and only a moron would think so. it's more square than the iPod, a bit thicker but not as tall. It fits just fine in my pocket, fits perfectly in my hand and has a good button layout and interface design. Both the iPod and the Karma are easy to use, just in different ways.
It finally came down to one factor for me... Ogg capabilities. I already have about 30 gig of music encoded in Ogg format (which my empeg also plays just fine). I'm not about to transcode everything, or worse yet go through the hell of reripping everything.
Feature for feature, the iPod and the karma are fairly close. I think they are both good products. I prefer both of them over the iRiver and other players, based purely on aestethics and form factor. It comes down to just these 2 players for me, and since only one of them plays Ogg, the Karma is the only possible solution for me. If the iPod played Ogg format, it would be a much tougher choice but Apple seems to be stubbornly refusing to acknowledge the desire or need for this format in their product.
-- Gary F.
Pyroman is correct. The Rio music manager software is in java and is platform neutral.
-- Gary F.
It's available from the Empeg BBS
You can skip directly to the Software
I recommend using the latest releaes of JEmplode with it. There's an updated Emplode in the alpha firmware package, but it's rather flakey and JEmplode seems to be quite a bit stabler (and runs on Linux).
-- Gary F.
Not really. 30 gig Mk2 units are going in the 500 to 600 dollar range. That's hardly "the price of their college education" unless of course you're sending them to clown college.
-- Gary F.
The neuros uses a backpack hard drive though, which radically increases it's form factor.
Rio just released the Karma with Ogg support. Done by the same team that did the empeg, from what I understand. I haven't tested out a karma yet but I definitely love my empeg and if it's half as good it's much better than anything else.
-- Gary F.
The empeg does, using the latest alpha release of the version 3 player software.
It's no longer in production, although it's still well supported and you can find them for sale quite often on the empeg forum.
-- Gary F.