Are you all guys seriously claiming that first a) finding right foo for your system, b) downloading foo, c) knowing where it went, d) knowing where to drag it, e) actually dragging it
is simpler than cryptic a) "install foo"?
Even if you automate all those steps and make a piece of software that has just a list of available applications and a place to drag it, you still need to know how start that, and it's not radically different or easier from how it's already done in most of cases (eg. checkbox in front of name and install button somewhere).
Alcohol, even in as low concentration as in beer, is much more effective in dehydrating you than coffee, it's probably not possible to drink enough beer to die from too much water - opposite might be conceivable, though. Well, assuming you don't die from alcohol poisoning first.
How big beers were those, and how much %, btw? Sounds like a quite magnificent amount of booze...
Very true. But, for every teenager who forgets to drink water while high on E, you have 20 drunks wrapped around a telephone pole. And drunk drivers have a nasty tendency to take out innocent people with them. So why on earth would E consumption be a bigger problem?
Bigger? Maybe not, but it's an additional problem, a new problem that be prevented before it's as well established, at that point it can't be dealt any more. Just because we have one bad thing (drunk drivers) happening, doesn't mean we should add more of them!
It's vastly easier to prevent "more bad things" from creeping in than trying to take out the existing ones, especially if they're as widespread and commonly accepted as alcohol and tobacco. Eliminating those is nigh impossible but that's not an excuse for letting new problems creep in ad become as bad over times.
Well, "s/foo/bar/" is a regex search/replace command in many things (the mentioned ed/sed/perl at least) but it's not really part of regular expressions per se.
The match part in it is. I guess the replacement value would also be somehow since it allows those backreferences and the like.
A week? Not a change in hell. New versions of major system component like Gnome will usually not make it into current "revision based" distributions as updates.
There's just too much testing to make that happen, it'll be in the next distro version, but no Gnome 2.6 until Fedora Core 2 (few months), or Mandrake 11 (no idea).
English is *the* foreign language learned by most Japanese students, through (at least) to the end of High School. As a result there are an astounding number of native Japanese who know enough English to pass a test marked by somebody else who is also not a native English speaker. (So for a mark of 90%, presumably they can get away with a 10% miss rate.)
The same (study English and are teached by another non-native), however, holds true for majority of people speaking European languages. For some reason we don't manage to mangle English anywhere near as good as Japanese.
In some cases it could easily be just because the native language is much closer relative to English than Japanese is, but even that doesn't really hold true to Finnish for example...
From the Jargon file, under "Hacker Writing Style":
There is also an accepted convention for 'writing under erasure'; the text
Be nice to this fool^H^H^H^Hgentleman, he's visiting from corporate HQ.
reads roughly as "Be nice to this fool, er, gentleman...", with irony emphasized. The digraph ^H is often used as a print representation for a backspace, and was actually very visible on old-style printing terminals. As the text was being composed the characters would be echoed and printed immediately, and when a correction was made the backspace keystrokes would be echoed with the string '^H'. Of course, the final composed text would have no trace of the backspace characters (or the original erroneous text).
Accidental writing under erasure occurs when using the Unix talk program to chat interactively to another user. On a PC-style keyboard most users instinctively press the backspace key to delete mistakes, but this may not achieve the desired effect, and merely displays a ^H symbol. The user typically presses backspace a few times before their brain realises the problem -- especially likely if the user is a touch-typist -- and since each character is transmitted as soon as it is typed, Freudian slips and other inadvertent admissions are (barring network delays) clearly visible for the other user to see.
Deliberate use of ^H for writing under erasure parallels (and may have been influenced by) the ironic use of 'slashouts' in science-fiction fanzines.
A related habit uses editor commands to signify corrections to previous text. This custom faded in email as more mailers got good editing capabilities, only to take on new life on IRCs and other line-based chat systems.
charlie: I've seen that term used on alt.foobar often. lisa: Send it to Erik for the File. lisa: Oops...s/Erik/Eric/.
The s/Erik/Eric/ says "change Erik to Eric in the preceding". This syntax is borrowed from the Unix editing tools ed and sed, but is widely recognized by non-Unix hackers as well.
Well, not needing registration has the bad side of not being able to get your preferences if you happen to use another machine. Or change browsers. Or need to reset your profile (and cookies) for some other reason.
I wouldn't mind ggroups type very small registration form if it allowed to get settings everywhere, especially now as something like this has something bit more tedious to repeat than the simple things they've have had before. Especially if it would be parallel to the current system instead of replacing it.
Yes, Boxx had an Opteron system, but there were no desktop PCs from IBM, Gateway, Fujitsu, Sony, HP, or Dell with Opterons. As far as I can tell, when Apple published their test results on June 30th 2003, no OEM was shipping a 3.2GHz P4 system for Apple to test.
Yeah, that's all nice and fine, except that Apple didn't claim that they have the fastest first tier computer, they claimed they have the fastest personal computer on the world
It just DOES NOT matter if the fastest happened to be "only" Boxx, or some even smaller garage shop, THEY WERE LYING. If you apple meant only first-tier OEM's, THEN THEY SHOULD SAY SO. It's that simple.
It seems to me that if you're going to believe we managed that with the probes it also seems just as likely one could argue for earth bacteria having made it there long ago on meteors.
That's probably quite a bit more likely than the probe case, there has been a shitload of meteors after all, and any hitchhikers they might've got had wayyyy more time to adapt.
But wouldn't it be funny if the life on Earth first came from Mars, was killed by environmental changes, and now has lifted aboard probes back to home...
By the way, have you considered that the poster may not have been fluent in English? How about having some consideration for foreign posters?
I don't know what's the case with other people but it certainly seems to me that non-fluent people might actually spot errors better, at least in some cases, since we must think when reading a foreign language, instead of everything being automatic.
Simple typo doesn't significantly raise annoyance meter here either, but when I consistently see people using teh instead of the or there instead of they're or their, or rouge instead of rogue I'll start seeing red. I know, it's absurd, non-fluent person getting angry because the "natives" don't know how to write their own goddamned language.
I think there may have been some slight precautionary measures on reindeer _meat_, but you're correct, no reindeer-herd-massacre has been done in Finland because of Chernobyl. Dunno about the Swedes.
Here is a nice chart of Cs-137 amounts in reindeer meat, courtesy of Radiation and Nuclear Safety Authority of Finland. Which tells quite nicely how slight the Chernobyl hit (86-) actually was up here. The enormously bigger 60-80 elevations are from atmospheric nuclear weapon tests. And today the amounts are actually smaller than before Chernobyl.
Basically, on the whole we need not fear natural radioactivity, as our bodies evolved to cope with it (cellular repair). What we need to fear/respect is man-made radioactivity and its waste products, because when human error/greed/fallibility get involved, that is when man-made radioactivity bites us in the ass...
Correction: We need not fear radioactivity, be it natural or man-made, as long as it's within sane limits.
Getting 1300 "extra" millirems by working in nuclear plant is in no way different than those you would get from smoking.
Getting 3000 "extra" millirems by scouring Chernobyl area in motorcycle will not bite you in the ass any more than living in Kerala, India.
Numbers are probably off, but you get the idea.
I guess you were trying to say tha man-made radiation can sometimes be much more intense than natural (unless you're in deep space or something), and THEN we need to fear it.
"Well, no offense but you're stupid" Offense taken!
Well, sorry if I was overly harsh, but I still think judging something so abruptly without trying or explaining is pretty stupid. Especially considering you claimed it's not even a programming language because of this small thing. Please give it a try. If you still think it's insane after thousand lines, well, then you've at least got a reason to dislike it of knee-jerking juts on princible.
{} for block sructure works very well in paractice. Sure, it's good "style" to tab in your code so to help visualise block structure, but to enforce it's use is harsh in the extreme. And at least I can see a { or } in printed code. Seeing white space is altogether more difficult!
Well, I'll grant you that using something like 1 space for block structure in printed code would be very hard to see, but bit more is pretty much instantly visible. It can even be much better than badly or non-intended {} blocked code in some cases. Consider totally flat c-code, that is long enough that it's not immediately visible - you have absolutely NO IDEA about what block is what if the starting {:s are outside of your view, whereas with whitespace blocks are still clearly separate.
I think it's more than just a case of what you're used to. It's like putting full stops at the end of sentances, and starting them with capital letters. It's a clear, visual sign to structure.
Well, it's kind of like that. But is the full stop really absolutely necessary? It ALWAYS comes just before capital letter and python (and these new derivatives and clones) DO have the capital letter equivalent : at the beginning of each block.
White space is unclear unless you turn on "display tabs" or something similar in your text editor.
Well, that depends on the amount of the whitespace.
Slashdot Mirror
"Linux" isn't copying OS X. Linux isn't a single entity. Linux developers aren't a hive mind. What's so very hard to understand about that?
What comes to ROX folks, they're quite openly stating they're copying RISC OS. Oh yeah, by the way, the ROX-desktop project has existed before OS X.
About 4 years to be exact, I guess you at least had the sense to get subject right, even if it was by accident.
Dragging and dropping WHAT from WHERE to WHERE?
Are you all guys seriously claiming that first
a) finding right foo for your system,
b) downloading foo,
c) knowing where it went,
d) knowing where to drag it,
e) actually dragging it
is simpler than cryptic
a) "install foo"?
Even if you automate all those steps and make a piece of software that has just a list of available applications and a place to drag it, you still need to know how start that, and it's not radically different or easier from how it's already done in most of cases (eg. checkbox in front of name and install button somewhere).
Alcohol, even in as low concentration as in beer, is much more effective in dehydrating you than coffee, it's probably not possible to drink enough beer to die from too much water - opposite might be conceivable, though. Well, assuming you don't die from alcohol poisoning first.
How big beers were those, and how much %, btw? Sounds like a quite magnificent amount of booze...
Very true. But, for every teenager who forgets to drink water while high on E, you have 20 drunks wrapped around a telephone pole. And drunk drivers have a nasty tendency to take out innocent people with them. So why on earth would E consumption be a bigger problem?
Bigger? Maybe not, but it's an additional problem, a new problem that be prevented before it's as well established, at that point it can't be dealt any more. Just because we have one bad thing (drunk drivers) happening, doesn't mean we should add more of them!
It's vastly easier to prevent "more bad things" from creeping in than trying to take out the existing ones, especially if they're as widespread and commonly accepted as alcohol and tobacco. Eliminating those is nigh impossible but that's not an excuse for letting new problems creep in ad become as bad over times.
Well, "s/foo/bar/" is a regex search/replace command in many things (the mentioned ed/sed/perl at least) but it's not really part of regular expressions per se.
The match part in it is. I guess the replacement value would also be somehow since it allows those backreferences and the like.
A week? Not a change in hell. New versions of major system component like Gnome will usually not make it into current "revision based" distributions as updates.
There's just too much testing to make that happen, it'll be in the next distro version, but no Gnome 2.6 until Fedora Core 2 (few months), or Mandrake 11 (no idea).
Even if someone makes a highly advanced and believable bot, isn't the idea of trying to create AI with current programming methods fundament flawed.
Only if you're trying or wanting to create a real, humanlike AI.
Evolution of chatbot like "limited-AI" thingies will make a perfectly good user interface that doesn't try to take over the world.
English is *the* foreign language learned by most Japanese students, through (at least) to the end of High School. As a result there are an astounding number of native Japanese who know enough English to pass a test marked by somebody else who is also not a native English speaker. (So for a mark of 90%, presumably they can get away with a 10% miss rate.)
The same (study English and are teached by another non-native), however, holds true for majority of people speaking European languages. For some reason we don't manage to mangle English anywhere near as good as Japanese.
In some cases it could easily be just because the native language is much closer relative to English than Japanese is, but even that doesn't really hold true to Finnish for example...
It probably predeces even the usenet.
From the Jargon file, under "Hacker Writing Style":
There is also an accepted convention for 'writing under erasure'; the text
Be nice to this fool^H^H^H^Hgentleman, he's visiting from corporate HQ.
reads roughly as "Be nice to this fool, er, gentleman...", with irony emphasized. The digraph ^H is often used as a print representation for a backspace, and was actually very visible on old-style printing terminals. As the text was being composed the characters would be echoed and printed immediately, and when a correction was made the backspace keystrokes would be echoed with the string '^H'. Of course, the final composed text would have no trace of the backspace characters (or the original erroneous text).
Accidental writing under erasure occurs when using the Unix talk program to chat interactively to another user. On a PC-style keyboard most users instinctively press the backspace key to delete mistakes, but this may not achieve the desired effect, and merely displays a ^H symbol. The user typically presses backspace a few times before their brain realises the problem -- especially likely if the user is a touch-typist -- and since each character is transmitted as soon as it is typed, Freudian slips and other inadvertent admissions are (barring network delays) clearly visible for the other user to see.
Deliberate use of ^H for writing under erasure parallels (and may have been influenced by) the ironic use of 'slashouts' in science-fiction fanzines.
A related habit uses editor commands to signify corrections to previous text. This custom faded in email as more mailers got good editing capabilities, only to take on new life on IRCs and other line-based chat systems.
charlie: I've seen that term used on alt.foobar often.
lisa: Send it to Erik for the File.
lisa: Oops...s/Erik/Eric/.
The s/Erik/Eric/ says "change Erik to Eric in the preceding". This syntax is borrowed from the Unix editing tools ed and sed, but is widely recognized by non-Unix hackers as well.
Well, not needing registration has the bad side of not being able to get your preferences if you happen to use another machine. Or change browsers. Or need to reset your profile (and cookies) for some other reason.
I wouldn't mind ggroups type very small registration form if it allowed to get settings everywhere, especially now as something like this has something bit more tedious to repeat than the simple things they've have had before. Especially if it would be parallel to the current system instead of replacing it.
Yeah, they realized they ca't make any money with a Desktop solution they give away for free. How strange.
They still have desktop solution, solution that costs money. Well, two actually. RedHat Professional Workstation and RHEL Workstation.
Well, if you think it sucks for GUIs, then don't use it for GUIs.
There are plenty of good GTK bindings for OO languages
Woah. Looks like Perl has finally met its match!
What happened to simplicity ?
It's called Python.
Yes, Boxx had an Opteron system, but there were no desktop PCs from IBM, Gateway, Fujitsu, Sony, HP, or Dell with Opterons. As far as I can tell, when Apple published their test results on June 30th 2003, no OEM was shipping a 3.2GHz P4 system for Apple to test.
Yeah, that's all nice and fine, except that Apple didn't claim that they have the fastest first tier computer, they claimed they have the fastest personal computer on the world
It just DOES NOT matter if the fastest happened to be "only" Boxx, or some even smaller garage shop, THEY WERE LYING. If you apple meant only first-tier OEM's, THEN THEY SHOULD SAY SO. It's that simple.
It seems to me that if you're going to believe we managed that with the probes it also seems just as likely one could argue for earth bacteria having made it there long ago on meteors.
That's probably quite a bit more likely than the probe case, there has been a shitload of meteors after all, and any hitchhikers they might've got had wayyyy more time to adapt.
But wouldn't it be funny if the life on Earth first came from Mars, was killed by environmental changes, and now has lifted aboard probes back to home...
You're probably confusing the Opteron with Athlon 64 branded chips. Those did indeed arrive (slightly) after G5.
By the way, have you considered that the poster may not have been fluent in English? How about having some consideration for foreign posters?
I don't know what's the case with other people but it certainly seems to me that non-fluent people might actually spot errors better, at least in some cases, since we must think when reading a foreign language, instead of everything being automatic.
Simple typo doesn't significantly raise annoyance meter here either, but when I consistently see people using teh instead of the or there instead of they're or their, or rouge instead of rogue I'll start seeing red. I know, it's absurd, non-fluent person getting angry because the "natives" don't know how to write their own goddamned language.
As if there aren't enough /. reading geeks in Europe to wine & dine her by two continents full of geeks.
Australia and South America could probably get into that list as well.
I think there may have been some slight precautionary measures on reindeer _meat_, but you're correct, no reindeer-herd-massacre has been done in Finland because of Chernobyl. Dunno about the Swedes.
Here is a nice chart of Cs-137 amounts in reindeer meat, courtesy of Radiation and Nuclear Safety Authority of Finland. Which tells quite nicely how slight the Chernobyl hit (86-) actually was up here. The enormously bigger 60-80 elevations are from atmospheric nuclear weapon tests. And today the amounts are actually smaller than before Chernobyl.
Yup. If the animals would be scared by loud noise, the damn car itself would be repellent enough!
Stupid things just don't understand to be afraid of "unnatural" noise.
Basically, on the whole we need not fear natural radioactivity, as our bodies evolved to cope with it (cellular repair). What we need to fear/respect is man-made radioactivity and its waste products, because when human error/greed/fallibility get involved, that is when man-made radioactivity bites us in the ass...
Correction: We need not fear radioactivity, be it natural or man-made, as long as it's within sane limits.
Getting 1300 "extra" millirems by working in nuclear plant is in no way different than those you would get from smoking.
Getting 3000 "extra" millirems by scouring Chernobyl area in motorcycle will not bite you in the ass any more than living in Kerala, India.
Numbers are probably off, but you get the idea.
I guess you were trying to say tha man-made radiation can sometimes be much more intense than natural (unless you're in deep space or something), and THEN we need to fear it.
Spying cyborg animals, huh?
Well, they are coming.
No need to burn karma with an opinion.
I still feel more like puking than drooling over one.
Happy now?
"Well, no offense but you're stupid" Offense taken!
Well, sorry if I was overly harsh, but I still think judging something so abruptly without trying or explaining is pretty stupid. Especially considering you claimed it's not even a programming language because of this small thing. Please give it a try. If you still think it's insane after thousand lines, well, then you've at least got a reason to dislike it of knee-jerking juts on princible.
{} for block sructure works very well in paractice. Sure, it's good "style" to tab in your code so to help visualise block structure, but to enforce it's use is harsh in the extreme. And at least I can see a { or } in printed code. Seeing white space is altogether more difficult!
Well, I'll grant you that using something like 1 space for block structure in printed code would be very hard to see, but bit more is pretty much instantly visible. It can even be much better than badly or non-intended {} blocked code in some cases. Consider totally flat c-code, that is long enough that it's not immediately visible - you have absolutely NO IDEA about what block is what if the starting {:s are outside of your view, whereas with whitespace blocks are still clearly separate.
I think it's more than just a case of what you're used to. It's like putting full stops at the end of sentances, and starting them with capital letters. It's a clear, visual sign to structure.
Well, it's kind of like that. But is the full stop really absolutely necessary? It ALWAYS comes just before capital letter and python (and these new derivatives and clones) DO have the capital letter equivalent : at the beginning of each block.
White space is unclear unless you turn on "display tabs" or something similar in your text editor.
Well, that depends on the amount of the whitespace.