Tortoise git is the windows git gui of choice at our work and is the one I recommend to install for our clients who use windows. Haven't tried any others though.
Since I know the command line client best, I always install msysgit first, set up ssh keys in "git bash" using ssh-keygen and then install tortoise git. Warning, if you use msysgit, make sure to not use the "plink" ssh that is installed with tortoise but use the msysgit one. That setup has had the least issues for us.
Very cool. I had a flashback this fall after discovering an old book I made for some school project about programming the Apple 2. Code looked horrible (to my 2011 eyes) but with an emulator I was able to get it working. Those few old pages were the only traces left of my childhood programming.
Swiffy saved the day for us recently on a project where we needed an animation to support IE7+ as well as iPad. We were able to have our designer create a flash animation and upload to swiffy to test that the conversion worked. We then used the swf as a fallback for when canvas was not available.
The one HUGE drawback for me with swiffy is there was no standalone compiler that we could use and integrate into the site build. So we now have this manual step of converting the files on the (hopefully still functioning) swiffy website every time a change is required to the animation.
It’s hard to have absolutes. It’s not like it’s completely gone. These were 60- to 80-year-olds we tested. These are folks that are completely healthy. It’s along the lines of a 10 to 20 percent degradation. That degradation was enough to cause memory deficits.
I believe IPv6 provides a start for what is necessary to solve Step 2.
IPSec is part of the protocol so these connections can be trusted. Also no NAT issues so connecting directly between trusted 'plugs' may be simpler than with IPv4. May need to start with a mesh network over a mix of paths that you own and paths that you may not.
I have no real world experience implementing IPv6, just been looking into it lately.
You don't need to allow others write access to your repositories on github. Simply have them fork your public repository but don't add them as a collaborator. They can commit all they want and send you or any one of your 'admin' collaborators a pull request. This idea that git/github is losing changes is not true. You have at least until the next time the gc is run (90 days at github?), which is well beyond the time required to resolve the issue in any active project.
I've just recently ported a python/Django site to c#/.NET. The switch was not done for performance reasons (or community for that matter) but as a consideration the .NET version was an order of magnitude faster on the same hardware without any effort to optimize.
Re-thought for-loops hurt the brain. Please don't do that.
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." – Brian W. Kernighan
Another complication to note is that pitch != frequency. Pitch is how we perceive the thing. The same frequency at different volumes can be perceived as different pitches. So you really can't ever find perfect without knowing some exact context.
See wikipedia entry on pitch perception for more examples:
"He's like the early hackers at MIT such as [open source advocate Richard] Stallman who fought for people not to have passwords or secrets." .. and now fights for people not to confuse "Free Software" and "Open Source"
"ALL PERSONS UNDER THE AGE OF 18 ARE DENIED ACCESS TO THIS WEBSITE. IF YOU ARE UNDER 18 YEARS OF AGE, IT IS UNLAWFUL FOR YOU TO VISIT, READ, OR INTERACT WITH THIS WEBSITE OR ITS CONTENTS IN ANY MANNER. THIS WEBSITE SPECIFICALLY DENIES ACCESS TO ANY INDIVIDUAL THAT IS COVERED BY THE CHILD ONLINE PRIVACY ACT (COPA) OF 1998."
The site looks like it will be a great resource especially for young people learning. Just curious why are you disallowing anyone under 18 from using it?