I don't know much about this chip design, but many stack machines are integer-math only. It would make sense to dedicate lots of space for the stack on an integer-math only chip, which allows for arbitrary precision scalar math without a co-processor.
I've had a love-hate thing with Perl since I first saw it. I appreciate it's power, but scratch my head over some of the design choices. And the syntax! Inscrutable.
I do marvel at it's versatility, however. Perl. Is there anything it can't do? That being said, it's just too big for most of the work I do. If I need to hack a script together, I just reach for the Kornshell.
I've used Perl to prototype, and at that it excels, but the maintenance required for anything else hasn't given me the warm fuzzies. You have to be a bit of a wizard to showcase the elegance buried in Perl, and I just can't take the time. I'm sponsored by my company to increase my Java and C kung-fu, and <code>use Perl;</code> is just not part of our culture.
Anyway, to actually finish on topic, the db-powered app my company uses had ruled out mySQL, even on Linux, for lack of store procedures. The introduction of Perl is not going to change this significantly. Compared with Informix, mySQL rules, but it's not corporate-ready, at least for this corp.
Re:Hey!! I have a question!
on
Code Red III
·
· Score: 1
It is the question that burns your mind, like an itch you can't scratch. You want to know What. It. Is.
The Code Red is all around us. It is the air you breath, the food you eat. Code Red is there when you go to work and when you pay your taxes.
Apache infected by Code Red!
on
Code Red III
·
· Score: 1
I agree, though I've been racking my brain trying to come up with a creative way to use these incoming requests.
The most net-friendly thing I can come up with is to create a 0-byte/default.ida and just return the 30-byte 200 OK. This still clogs up the logs, but it doesn't add too much general noise, especially if you have custom error messages, like I do.
The most Evil thing I could come up with is using mod_rewrite to send the exact URI and query string back to the originating server:
<IfModule mod_rewrite.c>
# Turn on the rewriting engine
RewriteEngine on
# set to 5 for debugging, 0 otherwise
RewriteLogLevel 0
RewriteLog logs/rewrite_log
# If you find a URI that starts "/default.ida", change it to
# http://REMOTE_HOST/ and send the whole URL back wrapped in a
# "303 See Other"
RewriteCond %{REQUEST_URI} ^/default.ida*
RewriteRule ^/(.*)$ http://%{REMOTE_HOST}/?[redirect=seeother,last]
# If you are EVIL, construct a URL of the form
# http://REMOTE_HOST/REQUEST_URI?QUERY_STRING and do the same.
#RewriteRule ^/(.*)$ http://%{REMOTE_HOST}/$1 [redirect=seeother,last]
</IfModule>
Don't feel left out, just because you run Apache! You can be "infected", too. It's fun for the whole family!
The best solution would be an application-level way to just silently block or ignore these requests. It's just not easy to turn off logging on matching a URI. I suppose you could make a virtual host that serves on/default.ida, with logging turned off...?
The tools are there. Make them available and dirt-cheap, and the next generation of hackers, geeks and console jockeys will find them.
Like most folks, I learned on the BASIC that came with my little "home computer". Remember when there was more than one or two kinds of home computer? Sure those little boxes were not much more than programmable game boxes, but they _were_ programmable. As a result, I learned the thrill of staying up coding all night very early in my career. Not to mention the skills you learn coding your magnum opus on 32k and no fixed disk. You get clever with joystick ports and cassette recorders.
The problem may be that there are *too* many choices. It can be bewildering for a web-savvy kid when starting to explore the options for learning to code on their own. All those books, and languages, and docs.
Also, I have to mention some of the programmable toys that are coming out. The best example is good old LEGO. The Mindstorms is an excellent introduction into basic coding concepts. It's all there: variables, event handling, looping, subroutines. The interface is perfect for the raw beginner, but once you reach a certain sophistication, you can graduate to whatever style of coding you like. Want to use VB? LEGO provides the SDK. Want to code in C or Forth like a real robot coder? You got it.
Heck, if you want to create your own firmware and port your own language to it, those tools are there, too, and all free.
Still, I can't help but be a little afraid that most kids will grow up thinking the web is the internet, the internet is a kind of TV, operating systems are windows and mouses, real computers are PCs and coding is Visual Basic.
...until the economy makes a downturn, and it's decided you aren't needed any longer. We've already had a service-industry boom. It was called the "70's" and it lasted until the bottom fell out of the economy.
In the mid-to-late 70's, spending was at an all-time high, saving rates were lower than depression-era rates and people would quit jobs to go on vacations, certain another better one would be there after a few weeks.
Sound familiar?
BTW, you may want to do a search for the "Processed World" anthology for a different perspective on the temp worker situation in the '70's (and now). Big companies like HP *love* to paint the picture of the independent temp gunslinger, while making sure that over 60% of their workforce is temp. Gosh, no benefits or paid sick days, "work-at-will" contracts, and a workforce you can shrink at will (and still report "no layoffs"). Huzzah!
Slashdot Mirror
I don't know much about this chip design, but many stack machines are integer-math only. It would make sense to dedicate lots of space for the stack on an integer-math only chip, which allows for arbitrary precision scalar math without a co-processor.
Boy, are you going to get flamed.
I've had a love-hate thing with Perl since I first saw it. I appreciate it's power, but scratch my head over some of the design choices. And the syntax! Inscrutable.
I do marvel at it's versatility, however. Perl. Is there anything it can't do? That being said, it's just too big for most of the work I do. If I need to hack a script together, I just reach for the Kornshell.
I've used Perl to prototype, and at that it excels, but the maintenance required for anything else hasn't given me the warm fuzzies. You have to be a bit of a wizard to showcase the elegance buried in Perl, and I just can't take the time. I'm sponsored by my company to increase my Java and C kung-fu, and <code>use Perl;</code> is just not part of our culture.
Anyway, to actually finish on topic, the db-powered app my company uses had ruled out mySQL, even on Linux, for lack of store procedures. The introduction of Perl is not going to change this significantly. Compared with Informix, mySQL rules, but it's not corporate-ready, at least for this corp.
It is the question that burns your mind, like an itch you can't scratch. You want to know What. It. Is.
The Code Red is all around us. It is the air you breath, the food you eat. Code Red is there when you go to work and when you pay your taxes.
I agree, though I've been racking my brain trying to come up with a creative way to use these incoming requests.
The most net-friendly thing I can come up with is to create a 0-byte /default.ida and just return the 30-byte 200 OK. This still clogs up the logs, but it doesn't add too much general noise, especially if you have custom error messages, like I do.
The most Evil thing I could come up with is using mod_rewrite to send the exact URI and query string back to the originating server:
Don't feel left out, just because you run Apache! You can be "infected", too. It's fun for the whole family!
The best solution would be an application-level way to just silently block or ignore these requests. It's just not easy to turn off logging on matching a URI. I suppose you could make a virtual host that serves on /default.ida, with logging turned off...?
Why do we even need 7 digits for local calls? I certainly have less than 100 friends and family that I call. 10 digits are just a waste!
With digital switches, exchanges are basically area codea now, so that takes care of that problem.
All we need is a 3-digit number, and maybe a 3-digit exchange for less-dialed people or long distance calls.
I'm filled with solutions!
Like most folks, I learned on the BASIC that came with my little "home computer". Remember when there was more than one or two kinds of home computer? Sure those little boxes were not much more than programmable game boxes, but they _were_ programmable. As a result, I learned the thrill of staying up coding all night very early in my career. Not to mention the skills you learn coding your magnum opus on 32k and no fixed disk. You get clever with joystick ports and cassette recorders.
The problem may be that there are *too* many choices. It can be bewildering for a web-savvy kid when starting to explore the options for learning to code on their own. All those books, and languages, and docs.
Also, I have to mention some of the programmable toys that are coming out. The best example is good old LEGO. The Mindstorms is an excellent introduction into basic coding concepts. It's all there: variables, event handling, looping, subroutines. The interface is perfect for the raw beginner, but once you reach a certain sophistication, you can graduate to whatever style of coding you like. Want to use VB? LEGO provides the SDK. Want to code in C or Forth like a real robot coder? You got it.
Heck, if you want to create your own firmware and port your own language to it, those tools are there, too, and all free.
Still, I can't help but be a little afraid that most kids will grow up thinking the web is the internet, the internet is a kind of TV, operating systems are windows and mouses, real computers are PCs and coding is Visual Basic.
In the mid-to-late 70's, spending was at an all-time high, saving rates were lower than depression-era rates and people would quit jobs to go on vacations, certain another better one would be there after a few weeks.
Sound familiar?
BTW, you may want to do a search for the "Processed World" anthology for a different perspective on the temp worker situation in the '70's (and now). Big companies like HP *love* to paint the picture of the independent temp gunslinger, while making sure that over 60% of their workforce is temp. Gosh, no benefits or paid sick days, "work-at-will" contracts, and a workforce you can shrink at will (and still report "no layoffs"). Huzzah!
"Ha ha"