GoFuckYourself.com - Adult Webmaster Forum - View Single Post - make a perl script stay resident (compiled)?

XXXManager · 09-18-2002, 07:15 PM

HQ: I would suggest you get 1G. It can run on 512 as well but 1G is definately a requirement (unwritten I guess). MOD_PERL is HEAVY on mem. Get more while you can - its cheap these days. More mem will help you anyway even for non-mod_perl stuff

TheFLY: Hey

I truely read all what you wrote. Damn - I dont have time to live now

so...
OOP unlike windows does not come preinstalled with every machine like windows. People would not program it if it was a bad idea. OOP is not good for everything but its a damn good idea for complex object. If you have'nt been a part of such a project you would not understand the need. Hell - I dont use if for everything but when its needed its a bless.

OOP is quite the oposite from what you said:
"More lines of code to do the same thing" - wrong. I would not program a file compression utility in OOP but a banking system or an ERP or any other multi-"essence" system - i will indeed do.

Proceduraly programming sux. Procedures is the nicest way to do things "un"nicely. OOP takes that ugliness and covers it.
OOP is not a syntax - its a way of thinking. Encapsulating (hiding the shit

) is only one aspect of it.

Same thing with Inheritance.

Save redundant work? Writing dumb procedures will get you as far as possible from doing efficient non-redundant work. OOP helps as much as anything today is able to - in saving redundant work. It takes some time to clean your room - but once you did that - its damn much easier to find your lucky socks

"Getting a car to run 500Mph dont require some extra-weight removel - it requires a Jet engine

"
This was an analogy for people (you included I think) saying that HQ needs to just tidy his code a little. BS - tidy you code from now till forever - keeping a code in native perl will never be fast if you don't use DB connection pooling and compiled code.

HQ: listen man - if you do DB stuff - mod_perl is better for you than C or ASM - Forget about cleaning your code - you GOT to use DB-connection pooling and use compiled code. doing C DB connection pooling is possible - but you will have to figure out how OR find an already written library for that. MOD_PERL has all of that inside and needs very little porting IF you wrote your perl code right. Get the MOD_PERL running and ONLY THEN think about other smarter moves like really porting your code (atleast the mission critical parts) to C.

09-18-2002, 07:15 PM
XXXManager So Fucking Banned Join Date: Mar 2002 Location: Far out in the uncharted backwaters of the unfashionable end of the Western Spiral arm of the Galaxy Posts: 893	HQ: I would suggest you get 1G. It can run on 512 as well but 1G is definately a requirement (unwritten I guess). MOD_PERL is HEAVY on mem. Get more while you can - its cheap these days. More mem will help you anyway even for non-mod_perl stuff TheFLY: Hey I truely read all what you wrote. Damn - I dont have time to live now so... OOP unlike windows does not come preinstalled with every machine like windows. People would not program it if it was a bad idea. OOP is not good for everything but its a damn good idea for complex object. If you have'nt been a part of such a project you would not understand the need. Hell - I dont use if for everything but when its needed its a bless. OOP is quite the oposite from what you said: "More lines of code to do the same thing" - wrong. I would not program a file compression utility in OOP but a banking system or an ERP or any other multi-"essence" system - i will indeed do. Proceduraly programming sux. Procedures is the nicest way to do things "un"nicely. OOP takes that ugliness and covers it. OOP is not a syntax - its a way of thinking. Encapsulating (hiding the shit ) is only one aspect of it. Same thing with Inheritance. Save redundant work? Writing dumb procedures will get you as far as possible from doing efficient non-redundant work. OOP helps as much as anything today is able to - in saving redundant work. It takes some time to clean your room - but once you did that - its damn much easier to find your lucky socks "Getting a car to run 500Mph dont require some extra-weight removel - it requires a Jet engine" This was an analogy for people (you included I think) saying that HQ needs to just tidy his code a little. BS - tidy you code from now till forever - keeping a code in native perl will never be fast if you don't use DB connection pooling and compiled code. HQ: listen man - if you do DB stuff - mod_perl is better for you than C or ASM - Forget about cleaning your code - you GOT to use DB-connection pooling and use compiled code. doing C DB connection pooling is possible - but you will have to figure out how OR find an already written library for that. MOD_PERL has all of that inside and needs very little porting IF you wrote your perl code right. Get the MOD_PERL running and ONLY THEN think about other smarter moves like really porting your code (atleast the mission critical parts) to C.