i always liked the quicksort algorithm as well as concepts like structures, manipulating data in memory and of course loops! finally i can get those patents. try to collect them all!
portability is a great thing, but only if the app is meant to be distributed. if it's meant to be in-house save yourself the headache and do it all in PL/SQL. the app will be simpler and it'll perform better. the odds that your employer will switch platforms are, realistically, very low. besides, it's likely that speed of development and speed of execution are management's top priorities for the project. and even if they do, then you get to rewrite the app, which gives you a chance to clean it up down the road and provides you with plenty of work.
the only real answer would be to write a worm to wiggle its way onto exploitable machines, patch known holes, i.e. turning off most services, setting common application settings to common-sense ones and then delete itself.
unfortunately, this would be illegal. however, that won't stop anyone; what's stopping people from doing this is that to someone who could do it it's a waste of resources. if you have all those machines out there you can get your hands on, why not use them for your own nefarious purposes, since the people who own them neither have the common sense nor the ability to control their own machines.
You're forgetting the parent post authors theory on the world, Linux is the same thing as Unix, and Linux is the world, with out it, the earth would stop spinning and we'd all be thrown off into space.
i do sometimes forget that/. has warped me. i apologize.
Version 2.2 is in the works, which promises even more features
i was under the impression that the standard methodology in the unix-ish/open source-ish world was that odd sub-versions (.1,.3, etc.) were for adding features and even sub-versions (.2,.4, etc.) were for stabilizing the code, bug fixes, etc.
am i incorrect or does the postfix project simply not follow this model? just curious.
an attack like the one mentioned above would have the goal of smearing linux's reputation in the hopes that businesses would stay away from the software because of its high-profile legal trouble.
microsoft doesn't need to get rid of every copy, they just want to build up FUD surrounding it.
IRS's nearly failed $8 billion modernization attempt that includes missed deadlines, cost overruns of over $200 million
$200m is 1/40th of $8B. i wouldn't consider a 2.5% budget overrun headline worthy. of course, i guess it sounds like alot, so i'm supposed to be *shocked*
i just hope the IRS checked CPAN for an IRS module before they started
earlier versions had the showdown taking place during a dual bungie-jump session at Anakin's bar miztvah
i always liked the quicksort algorithm as well as concepts like structures, manipulating data in memory and of course loops! finally i can get those patents. try to collect them all!
everything is all cleared up thanks to the Edicar... Edictacar... Edicia... ah, forget it.
yeah.
portability is a great thing, but only if the app is meant to be distributed. if it's meant to be in-house save yourself the headache and do it all in PL/SQL. the app will be simpler and it'll perform better. the odds that your employer will switch platforms are, realistically, very low. besides, it's likely that speed of development and speed of execution are management's top priorities for the project. and even if they do, then you get to rewrite the app, which gives you a chance to clean it up down the road and provides you with plenty of work.
hey, you can't get everything you want.
unfortunately, this would be illegal. however, that won't stop anyone; what's stopping people from doing this is that to someone who could do it it's a waste of resources. if you have all those machines out there you can get your hands on, why not use them for your own nefarious purposes, since the people who own them neither have the common sense nor the ability to control their own machines.
it's so bleeding edge, there's no time to set things up! hurry!
- gentoo linux
- FreeBSD
- bash
- vim
- perl
- ruby
- MySQL
- PostgreSQL
- Apache
- PHP
- links www browser
- wget
- K Desktop Environment
- Mozilla Firefox
- xchat
- gimp
- Openoffice.org
slashcode has some weird funky rule that makes only lets this code post if i type in this line of fillerso *that* explains the lip sync problems in those old kung fu flicks.
i do sometimes forget that /. has warped me. i apologize.
i was under the impression that the standard methodology in the unix-ish/open source-ish world was that odd sub-versions (.1, .3, etc.) were for adding features and even sub-versions (.2, .4, etc.) were for stabilizing the code, bug fixes, etc.
am i incorrect or does the postfix project simply not follow this model? just curious.
how is that not less?
>$0
frmdrgtst --version
use lightning. i've seen it travel much further than you require.
i've had trouble testing my volume, and it's stressful.
this from the chief scientist. what an idiot.
neither is sex, but hey.
microsoft doesn't need to get rid of every copy, they just want to build up FUD surrounding it.
article. good. (brain chip implant required)
they're fucked.
geeks only run when being chased.
$200m is 1/40th of $8B. i wouldn't consider a 2.5% budget overrun headline worthy. of course, i guess it sounds like alot, so i'm supposed to be *shocked*
i just hope the IRS checked CPAN for an IRS module before they started
i wouldn't do that.