Well, good luck...But expect this to be a paying service. The days of the "it will be free" are over:
1. Build 3D Chat world
2. Charge users
3. Profit!!!
Except for a little details (and ameliorations, like voice-chat, better graphics), it was exactly what I thought about. I've used AW 5 years ago. Eventually everyone just stood still and read the text, not watching the graphics. Some techniques like the speech-bubbles are supposed to circumvent this.
Oh, well, back in the day AW was a non-paying service. I even payed some time for support, but now it's completely paying and I just don't care anymore. My friends there have left anyway.
What's wrong with that girl I've been chatting to for over three years! She's a real hottie, I've seen pics you know... She wants me! Just too bad I can't get in her pants over TCP/IP.
The Sega GameGear could play Master System games. You haven't lived if you didn't try to play Populous on the Gamegear using a MasterSystem cardridge.;-)
And that's why I've got a Psion. Way more powerfull than a Palm including touchscreen. Too bad Psion stopped making them. A truly good PDA seeing death because technology doesn't win over marketing.
If this is true, I will be screwed someday. I often make humorous comments in my code, and the occasion expletitive comes in it, especially if I have to work around another bug in the system.
Actually, up until now, I've never had any problems with it. Often coworks scream out "Hey, that must be your code...";-)
I once made a comment where some terrible hack was in it and I didn't want others to meddle with it. I marked it with "Don't touch: 100% WJO code" (WJO was my short for the versioning system). The maintainer of that code still talks about it at every company party when I meet her, because she was laughing out loud when she found it.
SMP support? Who cares? Not on the desktop at least. I'm deperately trying to get a dual system and no shop in my neighborhood is *willing* to deliver one!
I give you that one
Having both experience with Slackware and BSD (OpenBSD specifically), there is not much difference in configging the systems. Do some greps and you're on your way in no time. Don't forget that Slackware is the Linux that is closest to BSD (considering configuration).
Granted... as a Java developper I am disappointed. Yes, my Mac OS X (a BSD after all) doesn't seem to have Java problems.
Common problem with many companies... As if Windows support was great... Tsss... As you say "Whatever"
Look, I am far from a BSD fanatic. What I think is that the original parent poster was going for a +5, Funny. Unfortunately he was modded to Interesting. I think that BSD people are most of the time quiet in the back, while Linux people are yelling at about anyone they can (including the harmless BSD people in the back).
Sorry, my native language is not English and I meant "structure your thoughs". However I do think that forcing a strict (because Hierachical filesystems are strict and the proposed one is not) system upon the user causes him to think more logically. Creating structures for himself. Essentially there is no structure in the proposed system, just a few vague searches.
It's like having a big pile of paper on your desk and crawling through all of it if you need a certain paper.... While a nice set of drawers and filing cabinets make your life much much easier.
you're going back to file names again. forget the filename
No I wasn't I was stating an accurate description of a certain file which might as well be attributes. You see, actually you confirm my point: I used three attributes quoted (just as in a google search), yet you interpreted it as a name. And that is what it is, an accurate description of something *is* a name. Hence the supremacy of Hierarchical filesystems: it gives a name to a set of data (aka file).
it's not a matter of learning, it's a matter of laziness.
No worries, I understood that... Then stop being lazy!
The "problem" with Hierarchical filesystems is that you have to decide for a naming convention. Once you can make up your mind and *stick* to your own conventions there is no problem. From your post I can assume you are a coder, so you must be familiar with "coding conventions". Well, that's exactly the same thing. No I don't like coding conventions like prefixing the type in variables, but if that's the coding convention on my project I will damn well stick to it. It's exactly the same with filesystems.
What I find problematic is that there isn't anymore a "single handle" to a file. That is inherently wrong. You know, it is akin to people that don't know a certain word in a certain language (I speak 5 languages and often have that problem). When you don't find the exact word, you start describing it. People will understand you after a while, but it isn't fast and often you find not the exact word you were searching for....often it is just a bad compromise. To me this system looks like a bad compromise.
I do understand it is not a filename, that doesn't change the problem I describe. If he does not use the right keywords to make the query, he will not find the file.
Oh, and what if he wants to find the "Yearly Report 1976"? Guess that one won't be on top of the list. I guess this system is good for recently used files, but not for files that have been archived for years on your machine. (Yes, I do have files back from 1981, and yes, I know exactly where they are)
And that you are messy is your problem, not mine. Learn to organize, makes your life easier.
Yes, I do realise that. Essentially that is a "name" or some kind of "categorization". However, this is not much more different from giving consistent filenames and searching with the Windows search applet (or Sherlock, or the find command).
And as I said, people think strange sometimes. One day you think about "Personal Finances 2002" and the next day you think "My Money 2002". If you saved it with the keywords "Personal", "Finances" and "2002", you'll be very lucky if you find the same document by searching on "My Money 2002". Yes, the 2002 might match... But so will the 25000 other documents that you wrote in 2002 and classified under the keyword "2002".
Reread my comment: I know that users have problems with directories, and I specifically stated that. But the cause is not the filesystem itself, the cause is the *user*. If you cannot correctly align your thoughts, you cannot organize your stuff, and that's about it.
Oh yes, I did do tech support. And I can only tell you that a keyword based filesystem will be a complete nightmare for tech support. Why? Simple: now at least you have the vague idea where a specific file is. Once you use keywords, good luck finding a specific file back that you didn't create yourself.
The comparision of user/directories, C programmers/segfaults is absurd. The user is using a structure and can essentially do nothing wrong if he organizes his thoughts. The programmer however is creating something, eventually making his own datastructures. Yes, he makes a pointer error and he gets a segfault, well then he goes hunting for the bug. That's what a C programmer is supposed to do.
He took care of that? He did? Now that isn't clear to me when I read the article. In case everything goes wrong, he simply falls back to the Hierarchical File System. Great help, especially this is supposed to help people that cannot use HFS efficiently.
Essentially a user needs to associated keywords, but we all know users. Anything that causes extra work will not be used. I personally have seen users that save their Word documents as "Document 1". Too lazy (or just doesn't care) to give the doc a good name. You cannot help these kind of people, even with the best system.
Do you know why "My Documents" or/home/username exists? Because that way programs have a directory where they can default to, in order to write files. I remember back in the DOS days (and Windows 3.xx), there was no such thing and documents were cluttered all over the place. You know, like Lotus files in C:\123 or Word Perfect files in C:\WP51. Users couldn't fathom switching to a different directoy.
Of course I'm really biased, because I *like* HFS. I have used it for over 10 years, and it just feels like the right thing to organize stuff.
I doubt it. I know users have problems with directories, yes, but that is because they were not trained to know what they are.
If you explain them it's just a "box with a label on it", most of them do get it. They know boxes, they know labels and they do realise you can put a box in a box in a box (Russian puppets - forgot the name).
It all comes down to how organized someone is. If you are organized, you will grasp the concept of a directory tree (my mom does, she is over 50 and didn't touch a computer until last year). If you are unoriganized, you will lose your files anyway. Consider this: you save your spreadsheet today as "Yearly Report 2002", and two days later you want to call it back your mind just doesn't say "Yearly Report 2002", but more like "Financial Data last year". Then your nice database-filesystem won't find it either. Unless there is some serious AI backing it.
Yes, French do invent some of the stupidest words around. Especially for technology-related stuff. While doing a google search on "cliquetez", I found another one that hit me: "webmestre". Sure! Whatever they want!
The difference between Québec French and normal French is usually just the pronunciation and some awkward words. I can understand it, but it's really hard due to the very different pronunciation. Luckily, Québec people in Europe usually adapt quite fast to nomal French when they are around here.
While I have no dictionary around here now, I just did a quick test. I opened Microsoft Word (French version) and typed both words: "cliquez" and "cliquetez". They both are accepted by the spell checker, so I suspect they both are valid.
I do prefer "cliquez", but that's a personal opinion.
Well I did... Perhaps the guy just was playing silly. I don't know, but there are a lot of differences between the french spoken in Québec and the one in France. I really have trouble understanding the Québec french.
... I have heard people from Quebec use that word (I used to work for a Canadian company). However, in Europe one usually says "cliquez"... Well if you're in a french speaking country, of course.
Slashdot Mirror
At least someone who got the joke... :-(
1. Build 3D Chat world
2. Charge users
3. Profit!!!
Note: there is no "2. ???".
Oh, well, back in the day AW was a non-paying service. I even payed some time for support, but now it's completely paying and I just don't care anymore. My friends there have left anyway.
Wow, now we can track down the spammers that sign with their real name and kill them! Preferably gutting their entrails with a spoon!
What's wrong with that girl I've been chatting to for over three years! She's a real hottie, I've seen pics you know... She wants me! Just too bad I can't get in her pants over TCP/IP.
Yes, I still own my GameGear. It rocked!
And that's why I've got a Psion. Way more powerfull than a Palm including touchscreen. Too bad Psion stopped making them. A truly good PDA seeing death because technology doesn't win over marketing.
I don't think so... Besides she tried to hit on one of my co-workers (while his girlfriend was there!) ;-) Besides, I have a girlfriend.
It like seeing your mother in law drive of a cliff in your brand new Ferrari.
Did a funny comment bite you when you were young?
Actually, up until now, I've never had any problems with it. Often coworks scream out "Hey, that must be your code..."
I once made a comment where some terrible hack was in it and I didn't want others to meddle with it. I marked it with "Don't touch: 100% WJO code" (WJO was my short for the versioning system). The maintainer of that code still talks about it at every company party when I meet her, because she was laughing out loud when she found it.
- SMP support? Who cares? Not on the desktop at least. I'm deperately trying to get a dual system and no shop in my neighborhood is *willing* to deliver one!
- I give you that one
- Having both experience with Slackware and BSD (OpenBSD specifically), there is not much difference in configging the systems. Do some greps and you're on your way in no time. Don't forget that Slackware is the Linux that is closest to BSD (considering configuration).
- Granted... as a Java developper I am disappointed. Yes, my Mac OS X (a BSD after all) doesn't seem to have Java problems.
- Common problem with many companies... As if Windows support was great... Tsss... As you say "Whatever"
Look, I am far from a BSD fanatic. What I think is that the original parent poster was going for a +5, Funny. Unfortunately he was modded to Interesting. I think that BSD people are most of the time quiet in the back, while Linux people are yelling at about anyone they can (including the harmless BSD people in the back).It's like having a big pile of paper on your desk and crawling through all of it if you need a certain paper.... While a nice set of drawers and filing cabinets make your life much much easier.
No I wasn't I was stating an accurate description of a certain file which might as well be attributes. You see, actually you confirm my point: I used three attributes quoted (just as in a google search), yet you interpreted it as a name. And that is what it is, an accurate description of something *is* a name. Hence the supremacy of Hierarchical filesystems: it gives a name to a set of data (aka file).
it's not a matter of learning, it's a matter of laziness.
No worries, I understood that... Then stop being lazy!
The "problem" with Hierarchical filesystems is that you have to decide for a naming convention. Once you can make up your mind and *stick* to your own conventions there is no problem. From your post I can assume you are a coder, so you must be familiar with "coding conventions". Well, that's exactly the same thing. No I don't like coding conventions like prefixing the type in variables, but if that's the coding convention on my project I will damn well stick to it. It's exactly the same with filesystems.
What I find problematic is that there isn't anymore a "single handle" to a file. That is inherently wrong. You know, it is akin to people that don't know a certain word in a certain language (I speak 5 languages and often have that problem). When you don't find the exact word, you start describing it. People will understand you after a while, but it isn't fast and often you find not the exact word you were searching for....often it is just a bad compromise. To me this system looks like a bad compromise.
Oh, and what if he wants to find the "Yearly Report 1976"? Guess that one won't be on top of the list. I guess this system is good for recently used files, but not for files that have been archived for years on your machine. (Yes, I do have files back from 1981, and yes, I know exactly where they are)
And that you are messy is your problem, not mine. Learn to organize, makes your life easier.
Yes, I do realise that. Essentially that is a "name" or some kind of "categorization". However, this is not much more different from giving consistent filenames and searching with the Windows search applet (or Sherlock, or the find command).
And as I said, people think strange sometimes. One day you think about "Personal Finances 2002" and the next day you think "My Money 2002". If you saved it with the keywords "Personal", "Finances" and "2002", you'll be very lucky if you find the same document by searching on "My Money 2002". Yes, the 2002 might match... But so will the 25000 other documents that you wrote in 2002 and classified under the keyword "2002".
Oh yes, I did do tech support. And I can only tell you that a keyword based filesystem will be a complete nightmare for tech support. Why? Simple: now at least you have the vague idea where a specific file is. Once you use keywords, good luck finding a specific file back that you didn't create yourself.
The comparision of user/directories, C programmers/segfaults is absurd. The user is using a structure and can essentially do nothing wrong if he organizes his thoughts. The programmer however is creating something, eventually making his own datastructures. Yes, he makes a pointer error and he gets a segfault, well then he goes hunting for the bug. That's what a C programmer is supposed to do.
Essentially a user needs to associated keywords, but we all know users. Anything that causes extra work will not be used. I personally have seen users that save their Word documents as "Document 1". Too lazy (or just doesn't care) to give the doc a good name. You cannot help these kind of people, even with the best system. /home/username exists? Because that way programs have a directory where they can default to, in order to write files. I remember back in the DOS days (and Windows 3.xx), there was no such thing and documents were cluttered all over the place. You know, like Lotus files in C:\123 or Word Perfect files in C:\WP51. Users couldn't fathom switching to a different directoy.
Do you know why "My Documents" or
Of course I'm really biased, because I *like* HFS. I have used it for over 10 years, and it just feels like the right thing to organize stuff.
If you explain them it's just a "box with a label on it", most of them do get it. They know boxes, they know labels and they do realise you can put a box in a box in a box (Russian puppets - forgot the name).
It all comes down to how organized someone is. If you are organized, you will grasp the concept of a directory tree (my mom does, she is over 50 and didn't touch a computer until last year). If you are unoriganized, you will lose your files anyway. Consider this: you save your spreadsheet today as "Yearly Report 2002", and two days later you want to call it back your mind just doesn't say "Yearly Report 2002", but more like "Financial Data last year". Then your nice database-filesystem won't find it either. Unless there is some serious AI backing it.
The difference between Québec French and normal French is usually just the pronunciation and some awkward words. I can understand it, but it's really hard due to the very different pronunciation. Luckily, Québec people in Europe usually adapt quite fast to nomal French when they are around here.
I do prefer "cliquez", but that's a personal opinion.
Well I did... Perhaps the guy just was playing silly. I don't know, but there are a lot of differences between the french spoken in Québec and the one in France. I really have trouble understanding the Québec french.
... I have heard people from Quebec use that word (I used to work for a Canadian company).
However, in Europe one usually says "cliquez"... Well if you're in a french speaking country, of course.
Thanks dude... I ordered two at once!
Manga == Japanse Comics.
You really could have done a Google search, you know.