693 karma · joined March 2, 2008
Propaganda, by nature does not show objective facts and depend on "useful idiots". There are countless examples, parent mention Nazi Germany which had its own propaganda ministerium. In recent history, during the first Gulf war, we could read how Iraqi soldiers pulled infants from incubators in Kuwait City, turned out to be false, but was part of legitimise the war. In the second Gulf war, do you remember secretary Powell's united nations WMD speech?
This is also the biggest problem I have with node.js which is inherently single-threaded (libuv's thread-pool aside) and only uses a fraction of the CPU power available on your computer.
[Edit]: A trivial, but practical example which demonstrate the power of using your machine's capabilities compared to just a fraction. If you use Make to build your project. Try 'make -j n' where n is 2 x cores on your machine. And observed the speed of building in parallel compared to serialised.
First, linking with the webkit framework is not the problem, using the framework is. I was playing around with preferences and also location. As you say, this is when the Webkit frameworks kicks in, which might explain the memory blowup to 118MB.
Second, I seem to recall that modern OS allocators are reluctant to release memory back to the OS (pool) unless required (when available memory is low) hence the process appears to use more memory than what it actual might be using. When I just restart Flux without fiddling with preferences, memory usage stays at around 45MB. I still think this is way too high if you think about what the program is doing, but given the above, even if Activity Manager reports that Flux is using 45MB, it might not really use 45MB now, only at some point.
I remember I used Xcode's instruments to investigate my program and could then see that the real active memory used by the process was usually much less than what Activity Manager, top, and ps w/friends were reporting. So a large part of the memory the process is currently holding (45MB) might be released back to the OS if needed, I think. If someone has more details on this, please elaborate.
Edit: Flux is also running with 4 threads(!) which of course also adds to the process memory usage. Isn't a thread stack around 4-8 MB?
Also, Flux appears to use 0.1% CPU continuously which is sloppy since CPU usage can be remedied by putting (nano)sleep in the poll cycle to make it use zero CPU.
Using otool -L /Applications/Flux.app/Contents/MacOS/Flux you can see an impressive number of frameworks included. I guess inclusion of the webkit framework is the biggest culprit. Why all this is needed to simply dim the light on my screen is beyond me.
That said, Flux is perfect functionality wise and very useful.
Icons are not hieroglyphs, in fact the idea behind icons is the opposite. Icons trancend language and present a concept across language barriers. If you need to go to the bathroom in russia you will know which door to take thanks to an icon.
I have mixed feelings about TextMate going open source. If QuickSilver is any indication, it will now definitely take forever for a new release. Dang! and I seriously don't like ST2.