>we're stuck in a perpetual game of filling up spare CPU cycles with nothing in particular.
There are lots of CPU cycles, and plenty of cases where trading a few for increased flexibility makes a ton of sense.
There are lots of CPU cycles, and plenty of cases where trading a few for increased flexibility makes a ton of sense.
*In general and not supported by facts of any kind other than my own anecdotia.
You should not use virtual runtimes for everything your application does but using them in overnight cronjobs is ok.
Right now we are working on some middleware because the customers wants to use existing reporting tools(c#/windows only) with our product(perl/linux).
>Look how fast and simple this is! > >Yeah nice so how do I genearte my <wateva> reports? > >Well we can do the same with our <another> reporting service! > >No I want to keep my <goodOldstuff> based reports can you integrate those?