I thought about that, but that only solves the issue of asp's intrinsic objects(Request, Response, Session, Application, Server), not VBScript functions which still would have to be ported as Apache::ASP still requires you to use perl.
so I'm writing Perl functions to serve as drop-in replacements for people porting asp applications to perl. (I'm porting an application now, unfortunately Chilisoft asp couldn't handle the traffic this site gets).
So far I've gotten Trim, InStr, InStrRev, Left, Right, and a few others done. Having these functions really make translating the code a lot easier.
I wonder, is this too trivial to post on sourceforge? I'd love to share.
Although most people who bought a Zaurus love it, including fellow poster TechnoLust(read his journal), the ones that don't complain about the Linux OS - saying they prefer Windows or Palm. Hey, some people like a little handholding with their handheld.
The people who bought it because it runs Linux all seem to love it. Personally, the idea of a wireless handheld that runs bash and can ssh into my network is irresistible. I'm buying one, soon!
The world hates us because we have resources
on
Globalism Post 9/11
·
· Score: 2
We have resources, and thus are able to Do Things. No matter what we do, or don't do, there will be many people who hate Americans.
If we support a certain government(Israel, for instance), we are hated for that. If we withdrew all support from Israel, we would be condemned for abandoning the region and allowing the possibility for another anti-semitic massacre to occur.
If we give money to certain countries(like Saudi Arabia, for instance) we are demonized for supporting autocratic governments. If we do nothing we are lambasted for allowing the region to destabilize.
Look at Iraq for a good example. We are vilified for allowing millions of Iraqi children to receive inadequate medical and health care. Sadaam could comply with the UN, allow inspectors in his country, and greatly alleviate the suffering of the Iraqi people. Does the world blame Sadaam? No, they blame us.
In my opinion, our government generally does its best to promote peace and economic opportunity throughout the world. Mistakes get made, and consenquences happen, but overall our intentions are good. Since we have the ability to do things, the things we do aren't going to be liked by everyone. But don't confuse us with the real bad guys in the world - the terrorists, the dictators, the warlords. If Uncle Sam really had his way you'd all be living in democracies, have good paying jobs, and be free of worrying about when the next nutcase is going to blow the next building up.
We are not the cause of the world's problems. We may come up with the wrong solution from time to time but that doesn't make the problems our fault.
you might have a very high bar raised for those who would write core Windows components. For example, Netscape would have to be written in such a way as not to break the thousands of applications that have been written that make use of IE's low-level components. For example, I wrote an intranet application that uses the address bar, back & forward buttons, etc. You can't tell that IE is part of it, but it is.
This program WOULD NOT RUN if you stripped IE out of Windows. I think it would be neat if you could just drop in another browser and have everything work. But are the 3rd party players going to be willing to support all the functions, features, etc to create drop-in replacements? They just might be getting into more than they bargained for.
You might hear that AMD is unstable from a lot of intel zealots, but the real problem is people are buying extremely cheap motherboards, there are major problems and issues popping up on the forums from this.
Yes. The last several computers I have built, I passed on the savings I gained buying Athlon and bought Asus MB's(and I always pay a few extra bucks for ECC RAM). I've been very happy with these choices.
all the professors look at Microsoft with disdain. I can't imagine them switching from open source - i.e. Debian servers and gcc is what most CS classes are using, although I hear they may be moving from C++ to Java for the general curriculum.
Incidentally UNM has placed 100% of its CS and engineering graduates for years, which makes me scratch my head whenever I hear of someone from CMU or other top ten unis saying they can't find a job after graduation.
I wonder why geeky CS people have never applied algorithms to some of the vexing problems of everyday life.
For instance, figuring out that most people exercise with an exponential algorithm and devising an O(log n) way to get ripped abs in less than 5 minutes a day.
Or figuring out the shortest distance between meeting a beautiful woman and getting laid.
Devising a "quick sort" routing that got you out the door in the morning 5 minutes after waking up.
Perhaps an exponential growth algorithm for our bank accounts.
Why is it we only apply algorithms to move bits around?
I would really like to see a "if you buy petroleum products, you just might be supporting terrorism" commercial in response to the intelligence-insulting "if you buy drugs..." commercial we've been subjected to lately.
Well, I was being facetious, but since you asked...
1 - I am assumming duplicate lines have already been removed from file1 and file2. I don't know how you could remove them and find the same thing in both files, all in one command line.
2 - Knowledge of command line programs doesn't necessarily equate with knowledge of programming, but the two aren't necessarily exclusive, either. Unix command line programs are designed to be strung together at the command line with pipes and frequently have several command line options. What if I told you that sort file1 file2 | uniq -d used the quicksort algorithm and performed its task in O(n log n) time? Does the fact I solved a problem with the Unix command line make my solution any less relevant?
While im sure all of these participents are very good programmers and incredible mathmeticians, I'm fairly sure a lot of them wouldn't be able to tell you how to take two files on a Unix OS, and list only lines that appear in both in a single commandline.
I am one of those people who knows the bare minimum to move around in vi, type things in, and quit and nothing else. My total knowledge of vi is i to turn on insert mode, esc to go back to command mode, x to delete characters, dd to delete a line, the arrow keys to move around,:q! to quit without writing, and:wq to write the file and quit.
I learned vi because it is the one editor that is on every single system, and also because its small enough to fit on a boot disk. However, once I learned the bare minimum I needed I quit learning about it because its simply not productive to use such a rudimentary editor when there are so many better tools available.
:wq might be obsolete, but I picked it up from the O'Reilly book, Learning The Vi Editor. Where else was I supposed to learn about it?
I do the same things all the time. I use visual IDE's for programming just like every one else. But I don't see the need to make a graphical connection to remote machines when I'm trying to sync text files!(i.e. any code)
Have a Samba server everywhere you have a Windows machine, and do mount -t smbfs -o username=$user,password=$passwd//$windowsmachine/ C$//$unixmachine/$mountpoint for each Windows machine you want to connect to remotely. Install CVS and SSH clients on your remote machines. Use the same IDEs and other software on your laptop as you do on your remotes. Log in using SSH and use CVS or some other method to sync files.
This is easy and works everywhere. I've got setups at work, school and several friends houses that I can access from anywhere I'm at. If you need to control Windows machines remotely, learn its command line. You'll make up the time you spend learning it with the time you'll save dealing with slow buggy graphical clients.
I've never run into any shortcomings dealing with remote machines using text based clients. Perhaps there is someone out there who can enlighten me as to what I'm missing, but as far as I'm concerned text-based is faster and more productive.
are you documenting for users of the projects or are you documenting for present and future developers of the project? The two are completely different and have different requirements as such.
A web application by nature should almost always be self explanatory. A help link or button should be available prominently on every page. The better you do this part, the less it costs to support your app.
Developer documentation for a web app also works well with HTML. Not only can you use comments extensively, you can link variables and functions from where they are used to their actual definition. A common way to structure HTML documentation is to have a frame with the left frame containing a tree of links, an index, and a search. I would use something like ht://dig rather than a database to index your docs and allow searches.
At the moment I'm trying to find the best algorithm for finding the common elements between two arrays.
I could go the easy route and check every array index in the first array against every array index in all the other arrays. For all I know this is the most efficient way to do this.
But, instead I'm going to research some algorithm books and see if I can't find a more efficient way to retrieve the common elements.
I may very well end up with something that takes a lot longer to code and has less lines of code than the brute-force compare-every-element-against-every-other-element method. But if the payoff is faster, tighter code, then my research and extra coding time will have paid off. However, to the untrained eye, it may look like I'm spending more time to produce less code.
If you are a manager reading this, remeber, the best solution may take longer and contain less code than a suboptimal solution! You have to think hard if you are going to try to quantify this - because nobody knows off the top of his/her head what the best algorithm for everything is. If you have a programmer who regularly researches the efficiency of the algorithms they use you will probably end up with a lot happier customers than if you just have people who bang out code without thinking hard about what they are doing. Unfortunately, doing things the right way makes the programmers job harder to quantify.
Interestingly enough, relational database technology itself was created to overcome the limitations of hierarchal databases(aka tree-based data structures). The problem back then was - not everything can be organized into a nice little hierarchal tree of data, however if you could create relations between otherwise unrelated pieces of information you could tie together all sorts of disparate data.
Seems to me like we're coming full circle with OOP and XML - trying to create huge monolithic structures that can handle everything we need to do. Look at Java - everything ultimately is inherited from the almighty Object. XML is no better in this regard, although you can have lots of different XML files describing different pieces of data.
I wonder if the people pushing hierarchal(OOP and XML) data models over relational ones realize that the exact opposite was the case 30 years ago. Perhaps we should have stuck with hierarchal databases in the first place?
If you would rather them stay, then you would have helped Morpheus to quickly solve the problem rather than post on your website enticements for former Morpheus users to join Kazaa.
The real intention was to disrupt all the Morpheus users and try to lure them to Kazaa. Everyone knows it, its obvious, and what Kazaa just said is a really, really, really lame argument.
for proving that your "P2P" network really is centrally controlled. That was quite a stunt, kicking all those Morpheus users off, then trying to lure them back into the network to use Kazaa.
I really hope the majority of people see right through this, choose Morpheus(and therefore gnutella), and I hope this gets fast track shut down.
Its not true P2P if someone can flip a switch and cut everyone off. P2P is supposed to have no central control so when these programs become illegal(and there's no doubt they will shut them down if they can) they will live on because the network will still be there, and hopefully the project will also still be there living on in some enlightened country without industry sponsored politicians and the DMCA.
I thought about that, but that only solves the issue of asp's intrinsic objects(Request, Response, Session, Application, Server), not VBScript functions which still would have to be ported as Apache::ASP still requires you to use perl.
So far I've gotten Trim, InStr, InStrRev, Left, Right, and a few others done. Having these functions really make translating the code a lot easier.
I wonder, is this too trivial to post on sourceforge? I'd love to share.
Although most people who bought a Zaurus love it, including fellow poster TechnoLust(read his journal), the ones that don't complain about the Linux OS - saying they prefer Windows or Palm. Hey, some people like a little handholding with their handheld.
The people who bought it because it runs Linux all seem to love it. Personally, the idea of a wireless handheld that runs bash and can ssh into my network is irresistible. I'm buying one, soon!
We have resources, and thus are able to Do Things. No matter what we do, or don't do, there will be many people who hate Americans.
If we support a certain government(Israel, for instance), we are hated for that. If we withdrew all support from Israel, we would be condemned for abandoning the region and allowing the possibility for another anti-semitic massacre to occur.
If we give money to certain countries(like Saudi Arabia, for instance) we are demonized for supporting autocratic governments. If we do nothing we are lambasted for allowing the region to destabilize.
Look at Iraq for a good example. We are vilified for allowing millions of Iraqi children to receive inadequate medical and health care. Sadaam could comply with the UN, allow inspectors in his country, and greatly alleviate the suffering of the Iraqi people. Does the world blame Sadaam? No, they blame us.
In my opinion, our government generally does its best to promote peace and economic opportunity throughout the world. Mistakes get made, and consenquences happen, but overall our intentions are good. Since we have the ability to do things, the things we do aren't going to be liked by everyone. But don't confuse us with the real bad guys in the world - the terrorists, the dictators, the warlords. If Uncle Sam really had his way you'd all be living in democracies, have good paying jobs, and be free of worrying about when the next nutcase is going to blow the next building up.
We are not the cause of the world's problems. We may come up with the wrong solution from time to time but that doesn't make the problems our fault.
you might have a very high bar raised for those who would write core Windows components. For example, Netscape would have to be written in such a way as not to break the thousands of applications that have been written that make use of IE's low-level components. For example, I wrote an intranet application that uses the address bar, back & forward buttons, etc. You can't tell that IE is part of it, but it is.
This program WOULD NOT RUN if you stripped IE out of Windows. I think it would be neat if you could just drop in another browser and have everything work. But are the 3rd party players going to be willing to support all the functions, features, etc to create drop-in replacements? They just might be getting into more than they bargained for.
Yes. The last several computers I have built, I passed on the savings I gained buying Athlon and bought Asus MB's(and I always pay a few extra bucks for ECC RAM). I've been very happy with these choices.
Incidentally UNM has placed 100% of its CS and engineering graduates for years, which makes me scratch my head whenever I hear of someone from CMU or other top ten unis saying they can't find a job after graduation.
For instance, figuring out that most people exercise with an exponential algorithm and devising an O(log n) way to get ripped abs in less than 5 minutes a day.
Or figuring out the shortest distance between meeting a beautiful woman and getting laid.
Devising a "quick sort" routing that got you out the door in the morning 5 minutes after waking up.
Perhaps an exponential growth algorithm for our bank accounts.
Why is it we only apply algorithms to move bits around?
I would really like to see a "if you buy petroleum products, you just might be supporting terrorism" commercial in response to the intelligence-insulting "if you buy drugs..." commercial we've been subjected to lately.
Well, I don't know about salesmen, but I do recall Jon Katz telling 500,000 Slashdot readers about a guy named Junis connecting to the internet from Afganistan with a Commodore 64.
purely being facetious
Well, I was being facetious, but since you asked...
1 - I am assumming duplicate lines have already been removed from file1 and file2. I don't know how you could remove them and find the same thing in both files, all in one command line.
2 - Knowledge of command line programs doesn't necessarily equate with knowledge of programming, but the two aren't necessarily exclusive, either. Unix command line programs are designed to be strung together at the command line with pipes and frequently have several command line options. What if I told you that sort file1 file2 | uniq -d used the quicksort algorithm and performed its task in O(n log n) time? Does the fact I solved a problem with the Unix command line make my solution any less relevant?
sort file1 file2 | uniq -d
So, whats my prize
I am one of those people who knows the bare minimum to move around in vi, type things in, and quit and nothing else. My total knowledge of vi is i to turn on insert mode, esc to go back to command mode, x to delete characters, dd to delete a line, the arrow keys to move around, :q! to quit without writing, and :wq to write the file and quit.
I learned vi because it is the one editor that is on every single system, and also because its small enough to fit on a boot disk. However, once I learned the bare minimum I needed I quit learning about it because its simply not productive to use such a rudimentary editor when there are so many better tools available.
:wq might be obsolete, but I picked it up from the O'Reilly book, Learning The Vi Editor. Where else was I supposed to learn about it?
I do the same things all the time. I use visual IDE's for programming just like every one else. But I don't see the need to make a graphical connection to remote machines when I'm trying to sync text files!(i.e. any code)
//$windowsmachine/ C$ //$unixmachine/$mountpoint for each Windows machine you want to connect to remotely. Install CVS and SSH clients on your remote machines. Use the same IDEs and other software on your laptop as you do on your remotes. Log in using SSH and use CVS or some other method to sync files.
Have a Samba server everywhere you have a Windows machine, and do mount -t smbfs -o username=$user,password=$passwd
This is easy and works everywhere. I've got setups at work, school and several friends houses that I can access from anywhere I'm at. If you need to control Windows machines remotely, learn its command line. You'll make up the time you spend learning it with the time you'll save dealing with slow buggy graphical clients.
I've never run into any shortcomings dealing with remote machines using text based clients. Perhaps there is someone out there who can enlighten me as to what I'm missing, but as far as I'm concerned text-based is faster and more productive.
are you documenting for users of the projects or are you documenting for present and future developers of the project? The two are completely different and have different requirements as such.
A web application by nature should almost always be self explanatory. A help link or button should be available prominently on every page. The better you do this part, the less it costs to support your app.
Developer documentation for a web app also works well with HTML. Not only can you use comments extensively, you can link variables and functions from where they are used to their actual definition. A common way to structure HTML documentation is to have a frame with the left frame containing a tree of links, an index, and a search. I would use something like ht://dig rather than a database to index your docs and allow searches.
I could go the easy route and check every array index in the first array against every array index in all the other arrays. For all I know this is the most efficient way to do this.
But, instead I'm going to research some algorithm books and see if I can't find a more efficient way to retrieve the common elements.
I may very well end up with something that takes a lot longer to code and has less lines of code than the brute-force compare-every-element-against-every-other-element method. But if the payoff is faster, tighter code, then my research and extra coding time will have paid off. However, to the untrained eye, it may look like I'm spending more time to produce less code.
If you are a manager reading this, remeber, the best solution may take longer and contain less code than a suboptimal solution! You have to think hard if you are going to try to quantify this - because nobody knows off the top of his/her head what the best algorithm for everything is. If you have a programmer who regularly researches the efficiency of the algorithms they use you will probably end up with a lot happier customers than if you just have people who bang out code without thinking hard about what they are doing. Unfortunately, doing things the right way makes the programmers job harder to quantify.
music as a noun == "a piece of property"
music as a verb == "an experience"
Interestingly enough, relational database technology itself was created to overcome the limitations of hierarchal databases(aka tree-based data structures). The problem back then was - not everything can be organized into a nice little hierarchal tree of data, however if you could create relations between otherwise unrelated pieces of information you could tie together all sorts of disparate data.
Seems to me like we're coming full circle with OOP and XML - trying to create huge monolithic structures that can handle everything we need to do. Look at Java - everything ultimately is inherited from the almighty Object. XML is no better in this regard, although you can have lots of different XML files describing different pieces of data.
I wonder if the people pushing hierarchal(OOP and XML) data models over relational ones realize that the exact opposite was the case 30 years ago. Perhaps we should have stuck with hierarchal databases in the first place?
I also have a domain where the machines are named after jazz musicians. satchmo, coltrane, miles, parker...
next I may do characters from Grateful Dead songs(CowboyNeal, JackStraw, etc)
Stevie Ray Vaughn covered this song. Its on his Greatest Hits CD
I just got the exact same thing compiling for OpenBSD 2.7. Yes I installed the patch first. Any ideas?
Hey, if Michael can go and post to FortKnox's journal to tell him to get a life for posting to slashdot too much, its only fair that someone post this in one of his stories.
We'd rather them stay on FastTrack.
Sorry, but thats a lame argument that even the 13-14 year olds who use Morpheus as their primary source of music can see right through.
If you would rather them stay, then you would have helped Morpheus to quickly solve the problem rather than post on your website enticements for former Morpheus users to join Kazaa.
The real intention was to disrupt all the Morpheus users and try to lure them to Kazaa. Everyone knows it, its obvious, and what Kazaa just said is a really, really, really lame argument.
for proving that your "P2P" network really is centrally controlled. That was quite a stunt, kicking all those Morpheus users off, then trying to lure them back into the network to use Kazaa.
I really hope the majority of people see right through this, choose Morpheus(and therefore gnutella), and I hope this gets fast track shut down.
Its not true P2P if someone can flip a switch and cut everyone off. P2P is supposed to have no central control so when these programs become illegal(and there's no doubt they will shut them down if they can) they will live on because the network will still be there, and hopefully the project will also still be there living on in some enlightened country without industry sponsored politicians and the DMCA.