Magical Factoring of Primes: SNAKE OIL ALERT
on
SSH v. SRP
·
· Score: 1
Firstly, I doubt completely your claim to be able to factor primes fast enough to be useful in hacking the recommended encryption in SSH.
Secondly, if you followed security lists at all, you'd know that encryption attacks are the least succesful way to hack a security tool.
Name one major hack based on an SSH weakness
on
SSH v. SRP
·
· Score: 1
Give me a break, these rips on SSH are almost completely groundless and in typical/. fashion, none of you really has a clue what you are talking about.
Yes, SSH has weaknesses and the occasional buffer overflow, but the patches are made fairly quickly, and because of the high number of people using it, there is a high probability that other people will find a bug before it affects you.
come on folks, the fact that this even needs to be discussed really amazes me.
of course,/. folks like to play "clever contrarian", so it doesn't shock me that some many of you have rallied around an utterly dead concept like the daily newspaper.
If this were 1910, you'd all be lobbying for horse-drawn carriages.
Its not a technology issue - its a marketing issue. Eiffel is not only poorly marketed, but there aren't any major open source Eiffel-based projects that would spur developers to learn more about it. For at least another three years, C is king, as much as it chaps me to admit it.
there are other paradigms...one that has been convincingly applied is to use a robust high performance platform based on an open standard (like Apache), and use easy to understand extension languages to extend the platform through a known interface.
I tend not to put too much stock into the language choices of academia. Often, departments are involved in deals with tool and language vendors to push a particular language.
As for "a trend towards simplicity"...please tell me what is simple about Java. I understnad the base language syntax is fairly clean, but in terms of tools and implementations, Java is a mess. There are serious discrepencies between the JITs, JVMs, JDKs, browser compatibility etc. that are not trivial for a new developer to deal with. Contrast this with Perl and Python - there is one developer kit, and it runs in a similar fashion on all platforms. Added to which, Java programmers must deal with compatability and support issues (since "write once, run anywhere" is not and will not be a reality), that Perl and Python users typically don't have to deal with.
Firstly, OO, in the sense of programming languages, makes no sense in relation to hardware.
Secondly, OO has been hashed around for twenty years now...with limited success. No one really believes that it is a panacea paradigm that should be translated up and down the system hierarchy.
After twenty some years, its obvious that object-oriented programming is not a panacea. What are your thoughts on the future of the OO paradigm? What other paradigms do you see challenging it?
During its heyday, in the late 80's, every female character inthe X universe had gigantic breasts, such that in real life they would have precluded any physical activity at all.
Sorry guys, but women with 36F breasts cannot move abruptly in any way without experiencing signficant discomfort.
Given the fact thatmost comic book readers are teenage guys, its easy to see where the artists were aiming.
Linux is an OS for people who already know how to use computers. Trashing X just to go after the home market (which linux will never capture anyway), would be insane - it wouldn't sell linux to any new users, and it would alienate the technical set.
Bravo! No unix will or should be "easy to use"
on
New Desktop for Linux
·
· Score: 1
I agree with your point emphatically. Its incredible how many lemmings think that this Midnight Commander rip-off is somehow going to catapult linux into the same realm as the Mac and Windows.
Folks, it ain't going to happen. You still can't run any unix without knowing all about/etc and shell interfaces.
Linux is a success in the serving business and as a low-cost technical OS. This is where it shines and its best hope for growth. Why people think they can somehow turn it into the MacOS is beyond me.
As an examine, I use Java to generate XML, SAX parse evens, or a DOM tree. I then feed this dataset into an XSL or CSS stylesheet that "transforms" it into HTML, WML, PDF, Chinese, Spanish, or any number of output formats.
As a veteren of the SGML industry, I'm glad to see that someone has finally been suckered into beleiving the entire hook-line-and-sinker model for transforming documents to arbitrary output formats.
Unfortunately, this model was designed to sell consulting time, not get work done.
CSS is respectable, but XML is getting fat (hence the fifth columnists in the SML world) and XSL is simply a joke. I'm suprised someone who seems so stuck on language features would advocate a language that features no modularity features whatsoever.
The Perl implementation uses a two-dimensional hashtable which requires an O(1) lookup to locate a prefix.
All hashtables have unit time lookups. Crack open your undergrad text.
Yeah, anyone who wants type safety is a idiot
Then stay away from Java - the only way you're going to get useful polymorphism outside of templates (which Java doesn't support) is to excessively cast from base classes, perhaps as far up the tree as Object. Bye-Bye type safety.
P.S. You're still wrong
Blah Blah Blah...you STILL haven't provided me with one concrete unbiased performance suite that shows Java beating perl.
So you've never written anything in perl other than some web scripts
What else is there?
Most top software folks at big software houses will tell you that.exe's are dead...if you aren't programming for the web, what are you doing?
People programming at top web sites are being compensated better than any other programmers in the industry (think seven digits). Chew on that before you knock it.
I await you posting a significant Perl module that you have developed using these tricks.
Sorry, all my perl is owned by the one of the world's busiest (as in top five) web sites. I have at least 50k lines of perl checked into this company's source repository.
Rambone, you are either a troll, or 12 years old, or both. Either way, I'm done arguing with you
Funny, each time you threaten us with your impending departure, you rattle off a post that would do Tolsty proud.
Perform a random sampling of Java VM's, and run a numerically intensive benchmark. Next, pick a random sampling of Perl implementations and run a similar benchmark
You make two separate references to claims for perl vs. java benchmarks. I already gave you one in my previous post - Kernighan and Pike.
Object churn? Perl excels at this. Before Perl5
Perl 5 is over five years old. Thats older than any production quality JDK. If you honestly expect me to take seriously a comparison of Java vs. Perl 4 (which is six years old), you're off your rocker. Of course, these are the only types of serious comparisons Java can handle. I'm sure Java is also quite favorable when comapred to PL/1.
Java syntax for objects is virtually lifted straight out of C/C++
Except they made Java both idiot proof and poorly performing by removing the virtual keyphrase. With Java you pay for a vtable whether you want it or not.
But lets face it, that is what Java is all about - making OO idiot-proof for the masses. Unfortunately, you get pissed on in the performance due to Sun's over-reaching assumptions.
I'm not going to run the benchmark for you
Thanks for playing, you've barked about benchmarks numerous times in your post but are unwilling to provide your own (even when I've given you a clear reference to a good unbiased comparison of perl and Java).
Slashdot Mirror
Secondly, if you followed security lists at all, you'd know that encryption attacks are the least succesful way to hack a security tool.
Yes, SSH has weaknesses and the occasional buffer overflow, but the patches are made fairly quickly, and because of the high number of people using it, there is a high probability that other people will find a bug before it affects you.
of course, /. folks like to play "clever contrarian", so it doesn't shock me that some many of you have rallied around an utterly dead concept like the daily newspaper.
If this were 1910, you'd all be lobbying for horse-drawn carriages.
well, at the very least there is functional programming.
Its not a technology issue - its a marketing issue. Eiffel is not only poorly marketed, but there aren't any major open source Eiffel-based projects that would spur developers to learn more about it. For at least another three years, C is king, as much as it chaps me to admit it.
there are other paradigms...one that has been convincingly applied is to use a robust high performance platform based on an open standard (like Apache), and use easy to understand extension languages to extend the platform through a known interface.
I'd love to check them out if just for interest.
In my opinion, if it ain't working after twenty years, it ain't going to work.
Not nearly enough is written about the negative issues regarding OO.
Compiler support isn't the issue with these features - its code bloat. Templates I can deal with (sometimes), but RTTI is going overboard.
As for "a trend towards simplicity"...please tell me what is simple about Java. I understnad the base language syntax is fairly clean, but in terms of tools and implementations, Java is a mess. There are serious discrepencies between the JITs, JVMs, JDKs, browser compatibility etc. that are not trivial for a new developer to deal with. Contrast this with Perl and Python - there is one developer kit, and it runs in a similar fashion on all platforms. Added to which, Java programmers must deal with compatability and support issues (since "write once, run anywhere" is not and will not be a reality), that Perl and Python users typically don't have to deal with.
Its an amusing OO tool for illustrating concepts, but Smalltalk's hardware-agnostic design simply couldn't perform as well as C.
Secondly, OO has been hashed around for twenty years now...with limited success. No one really believes that it is a panacea paradigm that should be translated up and down the system hierarchy.
After twenty some years, its obvious that object-oriented programming is not a panacea. What are your thoughts on the future of the OO paradigm? What other paradigms do you see challenging it?
Now that the Java hype has cooled off, what is your assessment of its future?
Sorry guys, but women with 36F breasts cannot move abruptly in any way without experiencing signficant discomfort.
Given the fact thatmost comic book readers are teenage guys, its easy to see where the artists were aiming.
Linux is an OS for people who already know how to use computers. Trashing X just to go after the home market (which linux will never capture anyway), would be insane - it wouldn't sell linux to any new users, and it would alienate the technical set.
Folks, it ain't going to happen. You still can't run any unix without knowing all about /etc and shell interfaces.
Linux is a success in the serving business and as a low-cost technical OS. This is where it shines and its best hope for growth. Why people think they can somehow turn it into the MacOS is beyond me.
Its a glorified Midnight Commander.
If I wouldn't pay for RedHat, I sure as hell wouldn't pay for some idiotic shell program.
As a veteren of the SGML industry, I'm glad to see that someone has finally been suckered into beleiving the entire hook-line-and-sinker model for transforming documents to arbitrary output formats.
Unfortunately, this model was designed to sell consulting time, not get work done.
CSS is respectable, but XML is getting fat (hence the fifth columnists in the SML world) and XSL is simply a joke. I'm suprised someone who seems so stuck on language features would advocate a language that features no modularity features whatsoever.
Don't - thats how Valley people are getting their primary compensation these days. Salary is just for buying groceries.
Even admitting stocks and options, there are far more millionaires at Microsoft and Cisco than there are at Yahoo and E-Bay
Not per capita, not by a longshot.
Overall, most web startups are losers, not winners
No risk, no reward.
Web jockeys are starting to become a dime a dozen
Who cares? The good ones have already made their millions.
How are those sour grapes tasting?
All hashtables have unit time lookups. Crack open your undergrad text.
Yeah, anyone who wants type safety is a idiot
Then stay away from Java - the only way you're going to get useful polymorphism outside of templates (which Java doesn't support) is to excessively cast from base classes, perhaps as far up the tree as Object. Bye-Bye type safety.
P.S. You're still wrong
Blah Blah Blah...you STILL haven't provided me with one concrete unbiased performance suite that shows Java beating perl.
What else is there?
Most top software folks at big software houses will tell you that .exe's are dead...if you aren't programming for the web, what are you doing?
People programming at top web sites are being compensated better than any other programmers in the industry (think seven digits). Chew on that before you knock it.
Sorry, all my perl is owned by the one of the world's busiest (as in top five) web sites. I have at least 50k lines of perl checked into this company's source repository.
Rambone, you are either a troll, or 12 years old, or both. Either way, I'm done arguing with you
Funny, each time you threaten us with your impending departure, you rattle off a post that would do Tolsty proud.
You make two separate references to claims for perl vs. java benchmarks. I already gave you one in my previous post - Kernighan and Pike.
Object churn? Perl excels at this. Before Perl5
Perl 5 is over five years old. Thats older than any production quality JDK. If you honestly expect me to take seriously a comparison of Java vs. Perl 4 (which is six years old), you're off your rocker. Of course, these are the only types of serious comparisons Java can handle. I'm sure Java is also quite favorable when comapred to PL/1.
Java syntax for objects is virtually lifted straight out of C/C++
Except they made Java both idiot proof and poorly performing by removing the virtual keyphrase. With Java you pay for a vtable whether you want it or not.
But lets face it, that is what Java is all about - making OO idiot-proof for the masses. Unfortunately, you get pissed on in the performance due to Sun's over-reaching assumptions.
I'm not going to run the benchmark for you
Thanks for playing, you've barked about benchmarks numerous times in your post but are unwilling to provide your own (even when I've given you a clear reference to a good unbiased comparison of perl and Java).