Launchy sits there with 30mb ram used and no cpu used when not in use.
This launcher sits there with 170mb ram used, and 1% of a core in constant use.
Launchy sits there with 30mb ram used and no cpu used when not in use.
This launcher sits there with 170mb ram used, and 1% of a core in constant use.
Even 30MB is ridiculous for this type of App... back in the DOS days there were similar TSRs using a few KB of RAM.
Of course, you could leave out the images, but you could also just keep using DOS if RAM is a concern :-)
And I still think 64x64 sounds kind of big for an icon, heh. I really need to get with the times, and get a lawn I guess.
WEB SCALE!
IO BOUND!
Forget assembly, they refuse to learn even the most basic and incredibly important consequences of the memory hierarchy. It's garbage collection and best practices all the way down.
I don't want to make fun of people. In fact, I can't make fun of people because the overwhelming majority doesn't appreciate the joke.
All I want is for people to give a shit.
n.b. Launchy 2.6 beta 2 on Windows - the most recent version since 2008 - pegs a CPU while it's running.
It is a bug, but it also means that Launch doesn't consume negligible CPU.
2.6b2's default behavior is to index too agressively. There are fixes out there, for those (like myself) who want to build their own binaries on Windows.
something to do with your system
Nope. https://www.google.com/search?q=launchy+cpu+usage
I'd give a better link but I'm on my phone.
That said, honestly I wish I knew the Node.js ecosystem:-/