Comerical ssh has one good feature which is not supported by openssh. It supports chroot for sftp subsystem. It is not essential feature but still it is nice to have it.
As I read the Halloween information at the site indicated above, I decided to re-read the "Linux Myths" page at Microsoft.com. I had read that one before in its entirety but I wanted to refresh my memory once more. As it turns out, the "Linux Myths" page is either missing or has been moved. So I searched using their search facility.
What about all of the cool API stuff and plugins, I suppose they all have to be rewritten? Mod_rewrite, mod_perl, etc, etc, yes?
AFAIK Apache's API have been changed and indeed all its modules should be rewritten for new Apache.
I don't know about all modules but here some info about mod_perl.
There is already exist rewrite of mod_perl for Apache 2.0 with threads support. It has many tasty features. Check yourself.
Last time (a year or maybe even two ago) I tried VNC to connect and run a Windows desktop it sucked a lot.
It was just slow. Very slow. Delays for screen updates were up to two seconds (on 100Mb LAN). I have no idea why but using VNC to run Linux desktop or using other programs (like PcAnywhere) to run Windows desktop is much faster.
If you want to talk about a rich ability to develop enterprise-ready applications, Linux doesn't stand a chance at this rate.
I don't know too much about PHP (I'm Perl developer for long time) and cannot compare it with ASP.NET but I usually don't trust people who use too much buzzwords without real facts. I know many people were able to build so called ' enterprise-ready applications' using Linux and Perl (just as example).
Anyway even if you want to talk using buzzwords. Ok. Linux can run Java which supposed to provide platform for 'enterprise-ready application'. It is supposed that Java can be used for 'enterprise-ready applications'. Moreover there is exist opinion that Microsoft actually catching up with their.Net platform.
So even if we don't use actual facts it is not very clear why Linux is not 'enterprise-ready applications'.
Sorry, I don't really understand what is the problem with temp tables but anyway I don't want to discuss it.
I would like to finalize discussion with following note. MySQL is very popular as SQL server used in web projects. Many people have been asked how database which lacks SP, triggers, etc can be so popular. The answer is simple: usually web applications doesn't have to deal with very complex data and all business logic can be easily implemented in middle tier without usage of SP, triggers, etc. In *seldom* cases when something like SP is required it can be easily simulated with temp tables.
But if you don't need SP, triggers, etc MySQL really rocks! It is very fast, it is very easy to setup, has excellent documentation.
P.S. Sorry about my spelling and grammar. Without spellchecker my spelling is... not very good:). And grammar.. sometimes it is not very bad:). But I hope my points were clear.
First of all I haven't said procedures are completely useless. My point is that they too often overused - instead of putting business logic into middle layer often it is put in to stored procedures.
Right now I have to deal with some legacy web application which has all its busness logic in PL/SQL scripts. It is very big PITA to support.
Concerning your example: task you have been described can be solved without any stored procedures. What is a stored procedure (usually)? It is several SQL queries. So why some code in middle layer can't execute them (storing intermidate data in temprorary table).
Can't say anything about Gemini but some words about BerkeleyDB and InnoDB.
InnoDB is just rocks!!! The only thing I don't like about it is that it is not very stable *yet* becoase it is very young. For example couple releases ago blobs were broken in it. But still it is already used in production by many peoples (for example my company switched on InnoDB several months ago).
BerkleyDB is not so cool as InnoDB because of several reasons. InnoDB was specially designed for SQL database while BerkleyDB table is just mapping on BerkleyDB. Guest which one is optimized for MySQL better. And finally BerkleyDB just doesn't scale for database which exceed size of RAM on server.
I am quite frightened when i see people still using MySQL...
Ok, it's a nice database but it lacks from major steps :
- fast and decent transactions
- procedures
- triggers
- views... (AFAIR there is no views)
First of all MySQL does has robust transactions. InnoDB's table type really rocks. Probably it is not very stable yet (there was found some problems with blobs some time ago) but it becomes better and better.
As for procedures and triggers and all other simular stuff. I wonder if it is really important to have it. I've seen some projects with heavy usage of procedures, triggers and other stuff. All busness logic of applications was implemented by them. It was very unmaintanable. IMHO more powerfull approach is three-tear architecture where middle layer (outside database) implements all busness logic itself.
IMHO procedures are often overused. Probably they are required sometimes but only sometimes.
If you think you need them than rethink you design. Maybe all logic you are going to implement with them should be implemented in middle layer?
I am quite frightened when i see people still using MySQL...
Ok, it's a nice database but it lacks from major steps :
- fast and decent transactions
- procedures
- triggers
- views... (AFAIR there is no views)
Re:Perl trying to outgrow its niche
on
Apocalypse 3
·
· Score: 1
Let's face it, perl is absolutely great for its original intention - fast, easy, write-and-forget scripting..... Wall and his fellow "designers" are struggling vainly to make Perl "grow up" -- something that it has absolutely no need to do.
Perl is already used by many people not just as fast, easy, write-and-forget scripting lanuguage. Java, Python are good languages but they don't have something that is missing in Perl. Perl have everything anyone needs to build complex web application for example(mod_perl, AxKit, HTML::Mason, etc).
AFAIK Linux 2.4.xx was major rewrite of 2.2.xx and 2.0.xx was major rewrite of 1.2.xx. Take for example SMP support. It have been imporved significantly in 2.4.xx comparing with previous stable kernel branches.
I'm not kernel hacker but I seriosly doubt that too much Linux kernel code that was written 10 year ago could survive these rewrites.
Write a killer game for the Itanium (imagine some REAL horsepower to do some stunning, jaw-dropping avatar AI and some absolutely awesome, fearsome, mind-boggling rendering.)
I'm hardly imaging any popular game targeted for Itanium. At least nowdays it is not a desktop platform. This technology is for servers.
And BTW as it was already mentioned Whistler will support Itanium.
Slashdot Mirror
If some trojan have been managed to steal your passphraise what prevents it from stealing your private key?
Comerical ssh has one good feature which is not supported by openssh. It supports chroot for sftp subsystem. It is not essential feature but still it is nice to have it.
I've tried to find this page with google.
I have that found page indeed doesn't work anymore but cached version still works.
AFAIK Apache's API have been changed and indeed all its modules should be rewritten for new Apache.
I don't know about all modules but here some info about mod_perl. There is already exist rewrite of mod_perl for Apache 2.0 with threads support. It has many tasty features. Check yourself.
AFAIK NVIDEA doesn't use DRI. They have their own techology. But you are right: it still requires kernel module which can crash system.
It was just slow. Very slow. Delays for screen updates were up to two seconds (on 100Mb LAN). I have no idea why but using VNC to run Linux desktop or using other programs (like PcAnywhere) to run Windows desktop is much faster.
I don't know too much about PHP (I'm Perl developer for long time) and cannot compare it with ASP.NET but I usually don't trust people who use too much buzzwords without real facts. I know many people were able to build so called ' enterprise-ready applications' using Linux and Perl (just as example).
Anyway even if you want to talk using buzzwords. Ok. Linux can run Java which supposed to provide platform for 'enterprise-ready application'. It is supposed that Java can be used for 'enterprise-ready applications'. Moreover there is exist opinion that Microsoft actually catching up with their .Net platform.
So even if we don't use actual facts it is not very clear why Linux is not 'enterprise-ready applications'.
I have seen in one book that there was created a ternary computer long time ago. I have tried to find anything with google and found this page.
I would like to finalize discussion with following note. MySQL is very popular as SQL server used in web projects. Many people have been asked how database which lacks SP, triggers, etc can be so popular. The answer is simple: usually web applications doesn't have to deal with very complex data and all business logic can be easily implemented in middle tier without usage of SP, triggers, etc. In *seldom* cases when something like SP is required it can be easily simulated with temp tables.
But if you don't need SP, triggers, etc MySQL really rocks! It is very fast, it is very easy to setup, has excellent documentation.
P.S. Sorry about my spelling and grammar. Without spellchecker my spelling is ... not very good :). And grammar .. sometimes it is not very bad :). But I hope my points were clear.
Right now I have to deal with some legacy web application which has all its busness logic in PL/SQL scripts. It is very big PITA to support.
Concerning your example: task you have been described can be solved without any stored procedures. What is a stored procedure (usually)? It is several SQL queries. So why some code in middle layer can't execute them (storing intermidate data in temprorary table).
InnoDB is just rocks!!! The only thing I don't like about it is that it is not very stable *yet* becoase it is very young. For example couple releases ago blobs were broken in it. But still it is already used in production by many peoples (for example my company switched on InnoDB several months ago).
BerkleyDB is not so cool as InnoDB because of several reasons. InnoDB was specially designed for SQL database while BerkleyDB table is just mapping on BerkleyDB. Guest which one is optimized for MySQL better. And finally BerkleyDB just doesn't scale for database which exceed size of RAM on server.
Ok, it's a nice database but it lacks from major steps :
- fast and decent transactions
- procedures
- triggers
- views
First of all MySQL does has robust transactions. InnoDB's table type really rocks. Probably it is not very stable yet (there was found some problems with blobs some time ago) but it becomes better and better.
As for procedures and triggers and all other simular stuff. I wonder if it is really important to have it. I've seen some projects with heavy usage of procedures, triggers and other stuff. All busness logic of applications was implemented by them. It was very unmaintanable. IMHO more powerfull approach is three-tear architecture where middle layer (outside database) implements all busness logic itself.
IMHO procedures are often overused. Probably they are required sometimes but only sometimes. If you think you need them than rethink you design. Maybe all logic you are going to implement with them should be implemented in middle layer?
Let's face it, perl is absolutely great for its original intention - fast, easy, write-and-forget scripting. .... Wall and his fellow "designers" are struggling vainly to make Perl "grow up" -- something that it has absolutely no need to do.
Perl is already used by many people not just as fast, easy, write-and-forget scripting lanuguage. Java, Python are good languages but they don't have something that is missing in Perl. Perl have everything anyone needs to build complex web application for example(mod_perl, AxKit, HTML::Mason, etc).
AFAIK Linux 2.4.xx was major rewrite of 2.2.xx and 2.0.xx was major rewrite of 1.2.xx. Take for example SMP support. It have been imporved significantly in 2.4.xx comparing with previous stable kernel branches.
I'm not kernel hacker but I seriosly doubt that too much Linux kernel code that was written 10 year ago could survive these rewrites.
Write a killer game for the Itanium (imagine some REAL horsepower to do some stunning, jaw-dropping avatar AI and some absolutely awesome, fearsome, mind-boggling rendering.)
I'm hardly imaging any popular game targeted for Itanium. At least nowdays it is not a desktop platform. This technology is for servers.
And BTW as it was already mentioned Whistler will support Itanium.
Check article "Full Disclosure is a necessary evil" on securityfocus.com
Check on your Debian system this RTFM /usr/share/doc/apt/offline.html/index.html