RIAA Lawyer: The plaintiff moves to have the defendants computer examined for evidence of hacking, and of file sharing.
So, they take it, find that is has a number of mp3s in the kazaa shared folder, show that there are no backdoors or trojans installed, and demonstrate that the default audio player has playlists including files those in the shared folder.
Andromeda could have been good. Never quite got there though.
Re:Cross Platform Editors
on
JOE Hits 3.0
·
· Score: 1
Sure, but the amount of times I need to do any editting without a GUI, all I need is any cursor addressable editor. Even pico will be adequate, and it doesn't take any time to learn.
Re:Cross Platform Editors
on
JOE Hits 3.0
·
· Score: 1
it's mostly the IDE addicts that risk being locked into a platform-specific editor.
I disagree. It's a long time since I've used a windowing system that doesn't have a GUI editor with syntax highlighting for several languages, and the same key mappings for cut, copy, paste, find, replace. The differences between say, KEdit and Visual Studio are really quite trivial. Swithcing between them doesn't cause anyone any trouble.
Re:Required Slashdot reading list
on
JOE Hits 3.0
·
· Score: 1
I must remember to add context when replying to a stupid troll who is about to be modded down.
And to take control of slashgrot to remove this post limit threshold. I mean, what is it with this site? They come up with an idea to prevent abuse, and whether it works, or not, they stick with it.
Re:Required Slashdot reading list
on
JOE Hits 3.0
·
· Score: 1
I tried it. It's useless.
No indent assist, no syntax highlighting, and no interface to the C compiler.
It's not to be taken seriously. It was something a friend of mine used to write after proofs to annoy a lecturer.
This is the perfect market open source
on
Open Voting at OSCON
·
· Score: 5, Insightful
Traditional software companies hate open-source software because no one owns it or collects royalties for it.
sigh... They really don't get it. Unlike Windows XP, or Adobe Photoshop, voting software requires very limited runs, and typically needs to recover its cost on its first sale. There's no need to make revenue on a per copy basis. There is probably only going to be a single customer who will have precise demands. If it was closed source, the amount of work would be the same, and the amount and so that you could charge would be the same.
Companies really need to get over the idea that because code costs money to produce, it must have value. Sometimes it is the case. Often it isn't.
It's all down to the recent pro-rocketpack legislation.
You see, thanks to Red Ken's conjestion charge, a whole industry has been created to find a way around it. One of the many classes of exempt vehicles is the rocket pack (because it causes no conjestion, and a lot of the waste is water). It's now a common sight to see businessmen commuting to work with a rocket pack, umberella, and reinforced crash-bowler. Anyway, because of the popularity of these, the government has made sure the requirements for using on are quite low, thus making it the idal city to try this in.
MP3 perhaps. But do they know what a 3D file format is? I'd suspect anyone who knows anything about 3D graphics is sufficiently up to speed to know more than 2 file formats.
One restriction I wouldn't mind, however, is the same sort of compatibility requirement that JAVA has: If something follows the format, it MUST follow it exactly and have no proprietary extentions.
This could cause problems. While 3D graphics is a fairly mature field, there are still additions being made to it. Will the format have support for textures? How about mipmaps? Ripmaps? Procedural textures? Some new concept that's about to be introduced?
The idea has promise. However, not in the manner you suggest.
Linux, for all its advantages is just the wrong OS for this sort of thing. It's far too complex for something that will only be used for playing games. It takes up a lot of space, and takes a long time to load.
The other issue that people have mentioned, is hardware compatibility. Actually, this is probably only an issue when it comes to graphics cards. Most other hardware has some sort of fallback compatibility mode.
While we can assume that all gamers will have one of a small selection of cards, this will not always be the case. A new player could enter the market. This is an area that would need work.
I'd suggest that having part of the OS on a small partition may work, but setting that sort of thing up is more effort than most people really care for.
So instead of choosing a name that makes it clear that he thinks this is the successor to C, then he should select one that require no additional words to be entered in Google when searching for it?
Yes. Why does it matter whether it's a successor to C or not? And does Dennis Richie agree?
First hit with "D Programming" gave the language homepage... what is the difference between typing "D Programming" versus "DProgramming"?
Because, if the language becomes popular, the homepage is the last place I'll be looking.
If I just want general information about the language, I'll not search. I'll just go to the website. I'll be more likely to search for "how to do X using D". Will you ever be able to find information on 3D programming in D?
The definition of Hacker has changed. It means someone who breaks into computers to absolutely everyone, except for a few self proclaimed "hackers" who think that everyone else in the world gets the term wrong.
I agree with you, but I think the article largely misses the point. The built in support for soundcards, and most other types of hardware is actually pretty good. He was just unlucky to have hardware that wasn't. These things happen, but it's quite rare these days.
Linux really needs a much simpler and more flexible way of installing drivers. Ideally, what people want is to do nothing at all. If this isn't possible, the next best thing is to copy some files to a "drivers" directory. Having all drivers bundled with the kernel strikes me as a bad solution. Okay, I know little about kernel development. Maybe there are good reasons. However, from a user point of view, keeping them separate would be nice.
Okay, but that's a workaround rather than a solution. I'm always grateful when people come up with slightly more abstract names to amke searching easier though. Even just 2 words bolted together makes it easier to get relevent hits.
Are you by any chance just generalizing based on YOUR behavior here?
Nope. I use return codes where needed. Generally speaking, all I want to do is retry, quit, or carry on anyway.
With error codes one ends up having to use gotos; being unable to pass exception straight (ie. having to properly propagate error codes up the stack), maybe have to use specific error handler pointers (to emulate exception handling), and so on.
I've never had to use goto. Nor do I need to handle pointers. Nor do I want this degree of error checking compiled into my code. The debugger should deal with this. The end user has no use for it.
it's also very easy to make high-level catch-all handling of nasty problems like null pointer/array index out of bounds, so that program does not have to terminate.
Surely the program should check that the input isn't going to produce an array out of bounds error. I use ASSERT on this sort of bug, and catch them before they find their way into released code.
Slashdot Mirror
Talk about an ice breaker.
Pah. If you want an icebreaker, put one of these in your living room.
RIAA Lawyer: The plaintiff moves to have the defendants computer examined for evidence of hacking, and of file sharing. So, they take it, find that is has a number of mp3s in the kazaa shared folder, show that there are no backdoors or trojans installed, and demonstrate that the default audio player has playlists including files those in the shared folder.
Andromeda could have been good. Never quite got there though.
Sure, but the amount of times I need to do any editting without a GUI, all I need is any cursor addressable editor. Even pico will be adequate, and it doesn't take any time to learn.
Why not just use the USPTO's database?
it's mostly the IDE addicts that risk being locked into a platform-specific editor.
I disagree. It's a long time since I've used a windowing system that doesn't have a GUI editor with syntax highlighting for several languages, and the same key mappings for cut, copy, paste, find, replace. The differences between say, KEdit and Visual Studio are really quite trivial. Swithcing between them doesn't cause anyone any trouble.
I must remember to add context when replying to a stupid troll who is about to be modded down.
And to take control of slashgrot to remove this post limit threshold. I mean, what is it with this site? They come up with an idea to prevent abuse, and whether it works, or not, they stick with it.
I tried it. It's useless.
No indent assist, no syntax highlighting, and no interface to the C compiler.
Since when was the word "aspirin" copyright?
1899. At least that's when it was trademarked. There's a difference between trademark and copyright.
Last time I checked it was the name of a drug.
Yup. Its the tradename of acetylsalicylic acid. In many countries, it's now considered a generic name, and therefore not under trademark protection.
It's not to be taken seriously. It was something a friend of mine used to write after proofs to annoy a lecturer.
Traditional software companies hate open-source software because no one owns it or collects royalties for it.
sigh... They really don't get it. Unlike Windows XP, or Adobe Photoshop, voting software requires very limited runs, and typically needs to recover its cost on its first sale. There's no need to make revenue on a per copy basis. There is probably only going to be a single customer who will have precise demands. If it was closed source, the amount of work would be the same, and the amount and so that you could charge would be the same.
Companies really need to get over the idea that because code costs money to produce, it must have value. Sometimes it is the case. Often it isn't.
It's all down to the recent pro-rocketpack legislation.
You see, thanks to Red Ken's conjestion charge, a whole industry has been created to find a way around it. One of the many classes of exempt vehicles is the rocket pack (because it causes no conjestion, and a lot of the waste is water). It's now a common sight to see businessmen commuting to work with a rocket pack, umberella, and reinforced crash-bowler. Anyway, because of the popularity of these, the government has made sure the requirements for using on are quite low, thus making it the idal city to try this in.
Hmm.. Good point.
MP3 perhaps. But do they know what a 3D file format is? I'd suspect anyone who knows anything about 3D graphics is sufficiently up to speed to know more than 2 file formats.
One restriction I wouldn't mind, however, is the same sort of compatibility requirement that JAVA has: If something follows the format, it MUST follow it exactly and have no proprietary extentions.
This could cause problems. While 3D graphics is a fairly mature field, there are still additions being made to it. Will the format have support for textures? How about mipmaps? Ripmaps? Procedural textures? Some new concept that's about to be introduced?
True, but they could have gone for GIF and WAV.
The idea has promise. However, not in the manner you suggest.
Linux, for all its advantages is just the wrong OS for this sort of thing. It's far too complex for something that will only be used for playing games. It takes up a lot of space, and takes a long time to load.
The other issue that people have mentioned, is hardware compatibility. Actually, this is probably only an issue when it comes to graphics cards. Most other hardware has some sort of fallback compatibility mode.
While we can assume that all gamers will have one of a small selection of cards, this will not always be the case. A new player could enter the market. This is an area that would need work.
I'd suggest that having part of the OS on a small partition may work, but setting that sort of thing up is more effort than most people really care for.
We attached bungee ropes to his swivel chair, and arranged it so that when he sat down, he'd go whizzing across the floor.
It was really funny when he went through the window, landed, and went whizzing down the road.
So instead of choosing a name that makes it clear that he thinks this is the successor to C, then he should select one that require no additional words to be entered in Google when searching for it?
Yes. Why does it matter whether it's a successor to C or not? And does Dennis Richie agree?
First hit with "D Programming" gave the language homepage... what is the difference between typing "D Programming" versus "DProgramming"?
Because, if the language becomes popular, the homepage is the last place I'll be looking.
If I just want general information about the language, I'll not search. I'll just go to the website. I'll be more likely to search for "how to do X using D". Will you ever be able to find information on 3D programming in D?
Whatever. Perhaps I should refer to myself as "Gay" and then get angry whenever people assume that I'm homosexual rather than merely happy.
The definition of Hacker has changed. It means someone who breaks into computers to absolutely everyone, except for a few self proclaimed "hackers" who think that everyone else in the world gets the term wrong.
But how am i meant to know to search for Digital Mars without knowing a little about D? Couldn't they have simply called the language "Digital Mars"?
I agree with you, but I think the article largely misses the point. The built in support for soundcards, and most other types of hardware is actually pretty good. He was just unlucky to have hardware that wasn't. These things happen, but it's quite rare these days.
Linux really needs a much simpler and more flexible way of installing drivers. Ideally, what people want is to do nothing at all. If this isn't possible, the next best thing is to copy some files to a "drivers" directory. Having all drivers bundled with the kernel strikes me as a bad solution. Okay, I know little about kernel development. Maybe there are good reasons. However, from a user point of view, keeping them separate would be nice.
Okay, but that's a workaround rather than a solution. I'm always grateful when people come up with slightly more abstract names to amke searching easier though. Even just 2 words bolted together makes it easier to get relevent hits.
Are you by any chance just generalizing based on YOUR behavior here?
Nope. I use return codes where needed. Generally speaking, all I want to do is retry, quit, or carry on anyway.
With error codes one ends up having to use gotos; being unable to pass exception straight (ie. having to properly propagate error codes up the stack), maybe have to use specific error handler pointers (to emulate exception handling), and so on.
I've never had to use goto. Nor do I need to handle pointers. Nor do I want this degree of error checking compiled into my code. The debugger should deal with this. The end user has no use for it.
it's also very easy to make high-level catch-all handling of nasty problems like null pointer/array index out of bounds, so that program does not have to terminate.
Surely the program should check that the input isn't going to produce an array out of bounds error. I use ASSERT on this sort of bug, and catch them before they find their way into released code.