> And what you are talking about is not exactly meta-programming.
I didn't describe metaprogramming, just how I usually see common metaprogramming "magic" implemented in javascript. The only reason you'd really need eval in js metaprogramming is if for some semantic reason it was nicer to accept a String of javascript somewhere. Afaik eval doesn't "get" you anything in javascript (it doesn't "unlock" private closures scope or anything, and context-injection is available using #call or #apply) and I almost never see it used, unless I am forgetting something (totally possible, I've been up all night)
> I mean what's your point. Yes, I realize that both are used profusely
My point is I don't see eval used profusely in javascript, which contradicts your assertion in a).
Edit: nvm, I stand corrected: (function(){var x = 1; eval('console.log(x)'); })() prints 1. Neat. But still, I do not see this often used, the callback + context passing approach is much more common.
That doesn't seem right. Can you give an example? I use lots of js metaprogramming, but it mostly involves wrapping and passing functions, mixing in methods and dynamic getters etc. I don't think I've ever actually had to use eval, or anything eval-like.
OTOH, grep for instance_eval and class_eval in rails source.
Yeah, don't use this. You lose key encryption (done at lock screen by osx) and DMA prevention, which were rather nice security features that the default OSX sleep mode provides.
That sounds right. OSX definitely encrypts your keys in memory while sleeping, to further prevent DMA attacks. So this would be tough to do without a kernel extension.
Another major caveat: locking your screen this way is a security risk if you are running FileVault. When OSX puts the computer to sleep and FileVault is enabled, DMA is automatically disabled until the screen is unlocked. If you use this app to lock your screen you will be removing the DMA prevention.
I would also be willing to bet there are other security concerns, as the iphone has taught us - lock screens can be hard :) be careful guys!
> No it doesn't, the DMG is automatically mounted and the app run if they do this
It really does, especially if you're one of the 99.999% of users who deletes their dmg's after installing. Then you just see an app icon with a big (?) in the middle of it.
No, don't use a .zip please. The point is to get the user to "install" the app, not open it once. A big aliased "Applications/" folder with a visual prompt to drag and drop the .app is all you need in the dmg. downloading & opening the dmg is a fairly seamless experience from Safari.
From a consumer (end user)'s perspective, you're pretty much wrong on all points except the last two. Those are valid, and i have accidentally done that before. Tis annoying.
One scenario: If you have a build server, say running jenkins, that consumes PRs from your private github repo and automatically runs them, someone from your team has to store an API key on it. Now imagine an attacker has gotten access to the network and is able to perform DNS cache poisoning.
I'll be brutally honest for you, since I would want the same: this is crap. You shouldn't have put this up yet. Here's a list of things wrong, I really hope you fix them because I like to see people make nice things :)
1. You're using minimalism as an excuse to not build a landing page. What is this!??!?!?! I sort of know what it is, but have no idea what the software looks like (is that a screenshot?)
2. I hate giving others design directives, but comic sans-ish fonts + spreadsheets makes very little sense. You can be "cute-sy" on other parts of the site, but when it comes to numbers you want things to be readable.
3. please preload any rollover images you have, seeing a button blink when i hover over it is so 90s.
4. The "Try now for free" should be right aligned, forreal.
otoh, the logo looks nice, except you should consider better aliasing on the font (or a css3 web font!) :)