Actually, there are a few problems with your code.
gcc test.c
Will produce `a.out' not `test'. Now, at University's the network admins tend to be dumb and like to place '.' in the $PATH.
This is pretty evil. If I'm root and I change into one of your directories, and let's say this directory has a ton of files in it. If I executed a simple command like 'ls' and had '.' in my $PATH, you could have an 'ls' in your directory that would be executed as root.
This is why we use./test. It's not so much because of shadowing (you could always stick '.' in the beginning of $PATH if you were worried about that).
Even after getting a job, I find that this is a much more stable way of programming newish things -
"find a lot of similar things, pick the best strategies & adapt".
Btw, these days - that's called "Research"
Thank you. Now I know never to hire you. That's not called "Research" that's called stealing.
Taking someone else's copyrighted code and passing it off as your own is stealing. Not only can you lose your job over that, you can get your company sued for millions and millions of dollars.
Cheating in college should always result in immediate explusion otherwise you get people in the real world who think this sort of thing is ok.
The locate command was designed to get around the terribly slow transversal of directories when looking for a particular filename. It suffered the same basic design flaw in that it did not take user permission into account.
The slocate (s as in secure) was designed to get around this obvious flaw. I'm a tad surprised Google didn't see this one coming. Maybe they've been hiring a few too many PhDs and not enough folks with real experience:-)
I saw both seasons in the entirity at the Alamo Draft House. It's an interesting little story about a group of soldiers stationed out in the Halo world. It's mostly a comedy of errors staring a spanish-speaking robot, a couple ghosts, and some really stupid people. All in all it's a lot of fun:-)
The creators actually stayed for QA after each showing at the Drafthouse. Gus even gave out the shirt off his back to one of the audience members.. it was, er, strange:-)
They aren't required to make anything "freely" available. They just have to make their documentation available under licensing terms. A few companies have already joined the company (like NetApp).
NetApp gave a talk about it at the CIFS 2004 conference. Basically, the documentation they provided was incompletely, incorrect, and provided less info than they already knew. However, they did work with NetApp to improve the documentation.
I'm not sure what this article is referring to though. This progam is well over a year old...
At this point (even before Whidbey) the deciding factor (as always) for Enterprise work, when choosing a language platform, should be the support it has behind it, in terms of IDE, tools, api, and longevity of the vendor pushing it (forget the OpenSource crap argument, those guys are too in love with Perl, Python, and Ruby - Java could become the child nobody wants to talk about if Sun dies) - right now that's C# and the.NET Framework ---
I'm having trouble parsing this. Here's what I *think* you're trying to say. If I'm wrong please correct me.
The three factors deciding factors in whether a language should be used in an Enterprise environment are the IDE, toolset, and richness of API. The vendor that champions the language also plays a key role.
Now, as for IDE/toolset/API, I think Java and C# are pretty evenly matched. You can say one's better than the other but they're more or less close enough (especially when considering you're other options like C or C++).
When speaking about the vendor, please remember, that IBM invests just as much (if not more) into Java as Sun. IBM isn't going anywhere soon. Eclipse, in fact, was donated by IBM in the first place.
I think another argument you could make in terms of Enterprise adoption is availability of skilled workers. Java has a clear advantage here over C#. Very few college students are learning C# these days and an increasing number of Universities are moving away from C/C++ to Java (for better or worse).
Now, what did you want to discuss here, which language is technically superior or which language is more appropriate for Enterprise adoption? They are vastly different things...
And BTW, f you over the Open Source comment. Ruby... geeesh.
Slashdot Mirror
Actually, there are a few problems with your code.
./test. It's not so much because of shadowing (you could always stick '.' in the beginning of $PATH if you were worried about that).
gcc test.c
Will produce `a.out' not `test'. Now, at University's the network admins tend to be dumb and like to place '.' in the $PATH.
This is pretty evil. If I'm root and I change into one of your directories, and let's say this directory has a ton of files in it. If I executed a simple command like 'ls' and had '.' in my $PATH, you could have an 'ls' in your directory that would be executed as root.
This is why we use
Even after getting a job, I find that this is a much more stable way of programming newish things - "find a lot of similar things, pick the best strategies & adapt". Btw, these days - that's called "Research" Thank you. Now I know never to hire you. That's not called "Research" that's called stealing. Taking someone else's copyrighted code and passing it off as your own is stealing. Not only can you lose your job over that, you can get your company sued for millions and millions of dollars. Cheating in college should always result in immediate explusion otherwise you get people in the real world who think this sort of thing is ok.
The locate command was designed to get around the terribly slow transversal of directories when looking for a particular filename. It suffered the same basic design flaw in that it did not take user permission into account. The slocate (s as in secure) was designed to get around this obvious flaw. I'm a tad surprised Google didn't see this one coming. Maybe they've been hiring a few too many PhDs and not enough folks with real experience :-)
I saw both seasons in the entirity at the Alamo Draft House. It's an interesting little story about a group of soldiers stationed out in the Halo world. It's mostly a comedy of errors staring a spanish-speaking robot, a couple ghosts, and some really stupid people. All in all it's a lot of fun :-)
:-)
The creators actually stayed for QA after each showing at the Drafthouse. Gus even gave out the shirt off his back to one of the audience members.. it was, er, strange
They aren't required to make anything "freely" available. They just have to make their documentation available under licensing terms. A few companies have already joined the company (like NetApp). NetApp gave a talk about it at the CIFS 2004 conference. Basically, the documentation they provided was incompletely, incorrect, and provided less info than they already knew. However, they did work with NetApp to improve the documentation. I'm not sure what this article is referring to though. This progam is well over a year old...