it surely does, how people can invest in a such useless app, well there is market for everything, but this is insane, well not as insane 16 billion whatsapp valuation, the market is crazy, CRAZY!!!
it looks good, but one recommendation: the call to action button that is in homepage ("Contact Us") that is color green, change it to maybe an orange color or a complementary one. The same in http://www.sprypoint.com/pricing. Just my two cents :)
We follow a "Marvel" scheme, for example: one server named ironman (background processing), another capt-america (sessions) and finally thor (storage) and so on, but follow any that is usable and meaningful for your team
Its not bad, is really nice, but Git has one problem, when you codebase is big, the process takes a long time, imagine git scanning those 8GB every time you do a commit, that is why Facebook was looking to port all their code to another VCS
I think it's worth making a distinction between the Git plumbing and the Git porcelain when talking about performance. The core functionality (the plumbing) is very fast regardless of repository size. The slowdowns people describe are almost always related to the porcelain commands, which are poorly optimized. Almost every porcelain-level command will cause Git to lstat() every file in your tree, as well as check for the presence of .gitignore files in all of the directories. It's very wasteful.
The fix for this is pretty simple: use filesystem watch hooks like inotify to update an lstat cache. I wrote something like this for an internal project and the speed difference was night and day. I remember reading that there had been progress on the inotify front on the git dev mailing list a few years ago, don't know what the current status is.
one thing you should wonder, do you think is good enough to leave a image to represent a heading? you might think, oh cool that look nice, but remember it affects SEO, there is another solutions for this workaround (cufon) but is not as flexible as webfonts, i think that webfonts will never replace a system font, but the web designers need to get a fallback, a reliable fallback.
Answering your question, i think is not possible to get the benefits from a webfont, but one possible solution for your problem related to the downsides is to ask the visitor to install the font required, but it would be not practical.
do you think is good enough to leave a image to represent a heading? you might think, oh cool that look nice, but remember it affects SEO
Having an image for a logo often consumes less bandwidth than a web font (because there's a lot of CSS and a font file involved with a web font). SEO shouldn't be a problem if you use the "alt" attribute in the image tag.
I'd like to say something, stick to PHP. PHP is a very neat programming language; I recommend you to read about Composer and PSR standards, but if you want to learn something different, try with Python or Ruby, both languages are kind of similar, hope it helps.
I would recommend you to use PouchDB, its a similar approach, but in this case you use CouchDB as a database, it can be used offline and it syncs http://pouchdb.com/
