Well, not quite all of them. One of the main benefits with tinkering with DD-WRT on Linksys b/g hardware is being able to boost the output from the rather puny(but effective for most) factory 28mW to well over 200mW. Makes for some pretty expansive WDS setups, and a HELL of a lot cheaper than the higher end commercial hardware.../i.
DD-WRT's power settings are great. For setting the power level lower...
Don't use them to set the power levels higher than the chipset's specs. The signal to noise ratio drops. You're just sending out the same data, louder, but with a correspondingly increased amount of background noise. You're not improving your connection, and damaging everybody elses'.
It's an abuse of language. But under the conditions on the planet, the phase transitions go from liquid to diamond, instead of liquid to graphite or fullerene.
... and because the indentation varies by the length of the type name.
And that's bad because...? I presume it's because it makes it easy to distinguish between types and values. Procedural programmers tend to obscure things for pay raises.
You're going out of your way to hide the code's tabular form. Every program you write is a state machine. Why hide it? You only complicate life for yourself.
I'm not going to fight with Slashdot's lame input field/text parsing, so here is an example with leading underscores:
Yes, that's very ugly. My version makes it extremely clear that we're defining a type. Yours looks like a block of random C code (maybe with extensions). Look at how the text crowds around the keywords and names.
The solution there would be to either a) change your tab indent to something less than 5 or b) do something about your horrendous code to reduce all of the nesting (since it is only nesting, not code length that has changed).
You missed the point, and so your solution is utterly broken. In particular, in this hypothetical example, I downloaded code that I now cannot read without text munging or changing my preferences.
Are you seriously suggesting that I should change my hypothetical preference for 5 space tabs because 2-space tab documents might not render correctly? That entirely undermines the idea that using tabs is preferable because it lets everybody pick their own indentation. It doesn't. That was my point.
An equally valid hypothesis is that there was no environmental change, but that in an otherwise genetically diverse population one small group gained a genetic competitive advantage over other proto-humans and began to multiply wildly, killing off or starving out the rest of the gene pool
World wide? That's not an equally valid hypothesis.
Low genetic diversity world wide, among three different species of great ape, when there had previously been great genetic diversity is indicative of catastrophe.
Why micromanage spaces and alignment when that's what computers are good for?
It would be nice if computers were good at finding a tabular normal form for code. But they're usually not. So you either end up with code in "stanza form", which is as hard to read as shitty poetry, or you find the normal form yourself by sticking spaces in appropriate places using "visual mode".
Unless you're being sensible and are actually tabulating your code. Why do you think I want to read your shitty poetry (stanza-form) when I could be checking off properties about a table (tabular form)?
data User = User { login_id:: LoginId
, login_password:: Password
, first_name:: Maybe FirstName
, last_name:: Maybe LastName
, email_address:: Maybe EmailAddre
, user_permissions:: [ Permission ]
} deriving (Data, Eq, Ord, Show, Typeable) is "awful". The only thing that is awful is how it looks when I paste it into the slashdot comment system, and the fact that it took me nearly a minute to get it to render the way it does on Slashdot.
User is a type. It's a function (a so-called data constructor) with a bunch of arguments of various types. I'll pass on your "one line" suggestion.
Unfortunately, it appears that TextMate has been using
The directional nature of the = sign is one place that mathematics and programming languages generally differ sharply.
Not in a programming language with "referential transparency". Languages with side-effects, where "=" doesn't mean "equality" but means "assigns", are not referentially transparent.
It's a shame that programmers don't even realize how much easier thinking about this stuff can be...
The bigger joke is SAS - as someone who has programmed in many, many languages it must have the absolute worst syntax/design of any computing language I know... in what other language does x=y actually mean y=x in some contexts????
Have you ever tabulated your code? Do you see that it offers readability and maintainability? Perhaps it is counter-intuitive, but using tabs to tabulate code is counter productive. The columns you will tabulate are typically not same-sized. So you will have to use spaces to bring columns into alignment. What happens when somebody comes and views your code with tiny or large tab stops?
I suppose I shouldn't care too much. It is 100% their problem at that point. But they are effectively undoing your work.
When did \n become a visible character? Just about every language I know of uses \n as a syntactically significant character... spaces are syntactically significant in most mainstream languages too. You always need at least one between tokens, right? That makes them syntactically significant.
I would be annoyed if I was a 5-space using user, and downloaded somebody's code, and found that it flowed off the screen because of 2-space nesting in the author's environment... I would rather see 2-space nesting than 5, in that case.
* The tab character itself has some semantic meaning - indent. The space is a word and symbol separator. Use an indentation character when you want to indicate indentation.
No, it doesn't mean "indent". It means "tabulate". You shouldn't be using tab to indicate indentation. You should use tab align table columns -- i.e., to indicate tabulation.
Well, not quite all of them. One of the main benefits with tinkering with DD-WRT on Linksys b/g hardware is being able to boost the output from the rather puny(but effective for most) factory 28mW to well over 200mW. Makes for some pretty expansive WDS setups, and a HELL of a lot cheaper than the higher end commercial hardware.../i.
DD-WRT's power settings are great. For setting the power level lower...
Don't use them to set the power levels higher than the chipset's specs. The signal to noise ratio drops. You're just sending out the same data, louder, but with a correspondingly increased amount of background noise. You're not improving your connection, and damaging everybody elses'.
Yeah, the first time.
Did you forget about all the colonial powers engaging in an economics and military race to control the Americas from about 1492 to 1900?
Value shouldn't always be measured in $$.
That only works between people who care about each other's needs.
Why was this modded informative? It's all absolutely wrong.
And the person who asked for more information said please! Imagine that. He was pleasant, and Blappo or whatever was rude in response.
It's an abuse of language. But under the conditions on the planet, the phase transitions go from liquid to diamond, instead of liquid to graphite or fullerene.
There's a fairly good reason for that. They're actively marketing to people who don't want blood diamonds.
Really? Four hundred thousand is a tenth of three hundred million?
... and because the indentation varies by the length of the type name.
And that's bad because...? I presume it's because it makes it easy to distinguish between types and values. Procedural programmers tend to obscure things for pay raises.
You're going out of your way to hide the code's tabular form. Every program you write is a state machine. Why hide it? You only complicate life for yourself.
I'm not going to fight with Slashdot's lame input field/text parsing, so here is an example with leading underscores:
Yes, that's very ugly. My version makes it extremely clear that we're defining a type. Yours looks like a block of random C code (maybe with extensions). Look at how the text crowds around the keywords and names.
The solution there would be to either a) change your tab indent to something less than 5 or b) do something about your horrendous code to reduce all of the nesting (since it is only nesting, not code length that has changed).
You missed the point, and so your solution is utterly broken. In particular, in this hypothetical example, I downloaded code that I now cannot read without text munging or changing my preferences.
Are you seriously suggesting that I should change my hypothetical preference for 5 space tabs because 2-space tab documents might not render correctly? That entirely undermines the idea that using tabs is preferable because it lets everybody pick their own indentation. It doesn't. That was my point.
I'm far more concerned with social crusaders who want to reward oversensitivity with new conventions, blah blah blah
Oh, the irony.
An equally valid hypothesis is that there was no environmental change, but that in an otherwise genetically diverse population one small group gained a genetic competitive advantage over other proto-humans and began to multiply wildly, killing off or starving out the rest of the gene pool
World wide? That's not an equally valid hypothesis.
...
Low genetic diversity world wide, among three different species of great ape, when there had previously been great genetic diversity is indicative of catastrophe.
Why micromanage spaces and alignment when that's what computers are good for?
It would be nice if computers were good at finding a tabular normal form for code. But they're usually not. So you either end up with code in "stanza form", which is as hard to read as shitty poetry, or you find the normal form yourself by sticking spaces in appropriate places using "visual mode".
Unless you're being sensible and are actually tabulating your code. Why do you think I want to read your shitty poetry (stanza-form) when I could be checking off properties about a table (tabular form)?
You're a fool if you think something like
data User = User { login_id :: LoginId :: Password :: Maybe FirstName :: Maybe LastName :: Maybe EmailAddre :: [ Permission ]
, login_password
, first_name
, last_name
, email_address
, user_permissions
} deriving (Data, Eq, Ord, Show, Typeable)
is "awful". The only thing that is awful is how it looks when I paste it into the slashdot comment system, and the fact that it took me nearly a minute to get it to render the way it does on Slashdot.
User is a type. It's a function (a so-called data constructor) with a bunch of arguments of various types. I'll pass on your "one line" suggestion.
Unfortunately, it appears that TextMate has been using
If \r and \n are "visible", then so is \t.
The directional nature of the = sign is one place that mathematics and programming languages generally differ sharply.
Not in a programming language with "referential transparency". Languages with side-effects, where "=" doesn't mean "equality" but means "assigns", are not referentially transparent.
It's a shame that programmers don't even realize how much easier thinking about this stuff can be...
The bigger joke is SAS - as someone who has programmed in many, many languages it must have the absolute worst syntax/design of any computing language I know... in what other language does x=y actually mean y=x in some contexts????
Uh... any logic with equality.
Have you ever tabulated your code? Do you see that it offers readability and maintainability? Perhaps it is counter-intuitive, but using tabs to tabulate code is counter productive. The columns you will tabulate are typically not same-sized. So you will have to use spaces to bring columns into alignment. What happens when somebody comes and views your code with tiny or large tab stops?
I suppose I shouldn't care too much. It is 100% their problem at that point. But they are effectively undoing your work.
When did \n become a visible character? Just about every language I know of uses \n as a syntactically significant character... spaces are syntactically significant in most mainstream languages too. You always need at least one between tokens, right? That makes them syntactically significant.
I would be annoyed if I was a 5-space using user, and downloaded somebody's code, and found that it flowed off the screen because of 2-space nesting in the author's environment... I would rather see 2-space nesting than 5, in that case.
* The tab character itself has some semantic meaning - indent. The space is a word and symbol separator. Use an indentation character when you want to indicate indentation.
No, it doesn't mean "indent". It means "tabulate". You shouldn't be using tab to indicate indentation. You should use tab align table columns -- i.e., to indicate tabulation.
What part of a "trade war" don't you understand?
Learn to read and you won't be called for making pedantic "corrections" that don't need to be made.