Looks nice. Thanks for the effort.
It’s impossible for the reviewer to be knowledgeable of every open source project out there. The best thing to do is contact support.
Windows Phone is the worst, don’t buy the Lumia 920.
Spoken by someone who probably has never used it.
I’m a WP7 early adopter, and I’m sticking with the platform. The 920 is probably the phone I’ll buy. Nokia has the better set of vendor-provided apps, and the camera is better than anything Samsung or HTC is putting out. I also like the “wireless charging” capability. It’s not really wireless charging, but the peripherals are what’s going to really sell it for me.
Good to hear your opinion on this. I’ve always understood the idea of closures for protecting code from other unknown script, but have never used them for the purpose of performance before. I like the idea of using this technique because it’s sort of like creating a “private class” which feels a lot more organized.
Keep in mind that you can use the first version only after it’s call (since it’s a variable) while the the second example is available immediately within its scope
The first version uses an immediately-invoked function (IIF). So
It comes down to how often you’ll call
myFunction(). If you call it multiple times throughout your application, then Example 1 is more efficient.
Make sure “under the floor boards” is properly ventilated and kept clean.
Synology has some good NAS units. Buffalo NAS units are OK.