2 ms·
>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 f
by macspoofing 13y ago
>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.
- EpicEng 13y agoNot to the users who sit around watching swirlies and beachballs. They don't care what rad, flavor of the month framework you used to build your software. Websites and desktop apps were more responsive in 1998 than they are today* *In general and not supported by facts of any kind other than my own anecdotia.
- sitkack 13y agobeachballs are for IO. You should have an SSD and banish the beachball.
- noptic 13y agousers do care about the tools they know. Our perl based webapp must interact with java, windows services, ... you name it. 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?