Square roots of two are very mathematically cool, but... "ISO A4 is 6 mm less wide but 18 mm higher than the U.S. "Letter" format." [1/4" less wide, 3/4" taller.]
I dunno, longer, less-wide paper means that the perimeter contains its writing area less efficiently. (A square would be most efficient for a rectangle.) So despite making my notepad almost 3/4" more unwieldy, moving to A4 actually reduces the area of the sheet by a small amount. (Do the math.)
Sure it's silly to quibble about a square centimeter of area; I'm just trying to quantify my aesthetic objection to skinnier paper...
bloxsom and pybloxsom (a port of the original Perl) offer an elegant plugin-based architecture with a gentle learning curve if you want to set up your own blog. And because so little is hardcoded into the app itself, you can leverage it to do all sorts of non-traditional sites; I wrote a plugin to enable a webcomic in a few hours.
By Lawrence Lessig, who is widely praised among/. readers for his work in IP law. I wonder if his thoughts on economic protectionism will be as well received.:)
just don't use it to justify theft... if the RIAA charges more than you want to pay, that doesn't mean you get to take it anyway. Check out emusic or other sources of indie music instead.
So the RIAA won't stop at bending the facts a little -- okay, a lot --
on their way to ripping fair use out of America. Nothing we didn't know.
What will be interesting will be to see how much play this gets in the
mainstream media. Probably no more than any of the other facts that
aren't convenient for the "hackers steal $billions on teh intarweb"
headlines they like to run.:-|
pretty extreme example of writing free software and charging for "services." I'm probably not the only one who didn't bother looking closer after seeing that.
You're not making sense. Remember, if you don't have exceptions, EVERYthing has to go into the return value, and that's what I'm talking about. It's not a pretty situation.
is that when you get an error that is properly handled 3 or 5 or 10 levels out from where the error happens, you DON'T want to have to check for that error in all the intervening calls. Your code would be messy as hell, and what happens more often, as you can see in a LOT of C code out there, is the coder pretends the error just won't happen.
Exceptions let you throw the error where it happens and catch it where it makes the most sense, however far down the stack that may be.
that's a pretty rediculous juxtaposition. perl is good language for one-offs and "duct tape;" Java is a systems language like. They really don't share the same problem domain; the one place they do intersect (web applications) is a place nobody uses C++, so they can't very well be supplanting it there.:)
... just a couple days ago. (Our previous high sale was $800 for someone not quite in the top 10.) I think that's probably a record for a game without fancy 3D graphics. I should spend less time coding and more time playing.:)
(And then there's the players who think any mixing of RL with the game world is grounds for lynching. Heh.)
None of these sites use the languages you specify for more than a small fraction of their pages. With the possible exception of TicketMaster, for which I'm not sure. (And in any case isn't in the same league as Yahoo and Amazon.)
TCL is far more maintainable than perl; you are obviously not very familiar with at least one of these languages.
Speed: they're all "fast enough." All of these scale well enough that for most sites you won't care, and none of them really scale well enough to support something like cnn.com. [Read through the archives to get a feel for the pain/. has to go through to serve its audience, for instance. And/. isn't even THAT big.] No flame; just that all these options are low/middle end.
Ease of use:
Classic ASP is pretty close to Perl. ASP.NET is a rather different paradigm, with a slightly steeper learning curve but more than enough added power to make it worthwhile. Unfortunately ASP.NET is a classic "leaky abstraction;" it tries to make things simple that sometimes aren't, and this will bite you.
Perl: it's nearly impossible to maintain a substantial site in perl with multiple developers working on the code. The language works against you here. Again,/. is a case in point. There's a reason/. doesn't upgrade to the latest & greatest very often.
JSP: takes a PHP-ish approach but Java is a statically typed language which makes using it for web apps _extremely_ verbose in comparison to the other languages here.
Javascript: poor fit for server-side use. Nobody does anything serious with it that way.
Verdict: They all suck to one degree or another. It's heresy on/. I know, but of these, ASP.NET is probably the best choice. If you want a toolkit/language that won't make site maintenance hell, OpenACS (tcl) or Zope (python) is probably a better bet. If you want something that will scale to absolutely huge levels (like the aforementioned CNN), J2EE is about the only game in town. (But a living hell to code for -- not recommended for smaller projects!)
- for all but the most trivial sites, separating code & presentation is a Good Thing - PHP supports this kind of separation. google for template libraries.
Slashdot Mirror
that's an attempt to create plausible deniability...
in other words the article blurb is either not funny or just stupid.
and the damn stock went up. :0
when your email starts with "php" :)
Slashdot: Read today's ArsTechnica tomorrow!
There would have to be many times more skycars than there are currently automobiles for congestion to be "just as bad."
you are correct; I subtracted 8 instead of 18mm.
:)
skinnier is still ugly though.
I dunno, longer, less-wide paper means that the perimeter contains its writing
area less efficiently. (A square would be most efficient for a
rectangle.) So despite making my notepad almost 3/4" more unwieldy,
moving to A4 actually reduces the area of the sheet by a small
amount. (Do the math.)
Sure it's silly to quibble about a square centimeter of area; I'm just
trying to quantify my aesthetic objection to skinnier paper...
bloxsom and pybloxsom (a port of the original Perl) offer an elegant plugin-based architecture with a gentle learning curve if you want to set up your own blog. And because so little is hardcoded into the app itself, you can leverage it to do all sorts of non-traditional sites; I wrote a plugin to enable a webcomic in a few hours.
not "first evidence"...
just like in judicial cases you can have circumstantial evidence, scientific hypotheses can be supported by indirect evidence.
By Lawrence Lessig, who is widely praised among /. readers for his work in IP law. I wonder if his thoughts on economic protectionism will be as well received. :)
just don't use it to justify theft... if the RIAA charges more than you want to pay, that doesn't mean you get to take it anyway. Check out emusic or other sources of indie music instead.
What will be interesting will be to see how much play this gets in the mainstream media. Probably no more than any of the other facts that aren't convenient for the "hackers steal $billions on teh intarweb" headlines they like to run. :-|
and yet email = hotmail?
:)
holy crap, gmail is going to clean up there.
for the former, use a labled outer loop
... ...
outer: for
for
break outer;
for the latter, "cleaning up properly afterwards" is a textbook case of where you want to use the finally clause of a try/catch block.
the former provides updated packages for EOL'd RH versions; the latter is the basis for new RH versions.
pretty extreme example of writing free software and charging for "services." I'm probably not the only one who didn't bother looking closer after seeing that.
Uh... no. In modern languages, that's a non-issue.
You're not making sense. Remember, if you don't have exceptions, EVERYthing has to go into the return value, and that's what I'm talking about. It's not a pretty situation.
is that when you get an error that is properly handled 3 or 5 or 10 levels out from where the error happens, you DON'T want to have to check for that error in all the intervening calls. Your code would be messy as hell, and what happens more often, as you can see in a LOT of C code out there, is the coder pretends the error just won't happen.
Exceptions let you throw the error where it happens and catch it where it makes the most sense, however far down the stack that may be.
that's a pretty rediculous juxtaposition. perl is good language for one-offs and "duct tape;" Java is a systems language like. They really don't share the same problem domain; the one place they do intersect (web applications) is a place nobody uses C++, so they can't very well be supplanting it there. :)
... just a couple days ago. (Our previous high sale was $800 for someone not quite in the top 10.) I think that's probably a record for a game without fancy 3D graphics. I should spend less time coding and more time playing. :)
(And then there's the players who think any mixing of RL with the game world is grounds for lynching. Heh.)
None of these sites use the languages you specify for more than a small fraction of their pages. With the possible exception of TicketMaster, for which I'm not sure. (And in any case isn't in the same league as Yahoo and Amazon.)
TCL is far more maintainable than perl; you are obviously not very familiar with at least one of these languages.
Speed: they're all "fast enough." All of these scale well enough that for most sites you won't care, and none of them really scale well enough to support something like cnn.com. [Read through the archives to get a feel for the pain /. has to go through to serve its audience, for instance. And /. isn't even THAT big.] No flame; just that all these options are low/middle end.
/. is a case in point. There's a reason /. doesn't upgrade to the latest & greatest very often.
/. I know, but of these, ASP.NET is probably the best choice. If you want a toolkit/language that won't make site maintenance hell, OpenACS (tcl) or Zope (python) is probably a better bet. If you want something that will scale to absolutely huge levels (like the aforementioned CNN), J2EE is about the only game in town. (But a living hell to code for -- not recommended for smaller projects!)
Ease of use:
Classic ASP is pretty close to Perl. ASP.NET is a rather different paradigm, with a slightly steeper learning curve but more than enough added power to make it worthwhile. Unfortunately ASP.NET is a classic "leaky abstraction;" it tries to make things simple that sometimes aren't, and this will bite you.
Perl: it's nearly impossible to maintain a substantial site in perl with multiple developers working on the code. The language works against you here. Again,
JSP: takes a PHP-ish approach but Java is a statically typed language which makes using it for web apps _extremely_ verbose in comparison to the other languages here.
Javascript: poor fit for server-side use. Nobody does anything serious with it that way.
Verdict: They all suck to one degree or another. It's heresy on
- for all but the most trivial sites, separating code & presentation is a Good Thing
- PHP supports this kind of separation. google for template libraries.
you need to change your google preference from 10 results displayed to something larger...
:)
if you have already done this and you're still wading through that many pages of results you suck at specifying what you want to search for