I was just making the case for investing in Apple on seeking alpha (an investing site). I've seen few people switched to the iPhone and even I was tempted with the release of the iPhone 5. To be honest, I haven't played with an android phone that matches it hardware wise. The lack of nexus 4 devices in the store really hurts google as there's no way one can just walk in a store and 'test' it out, like one can do with the iPhone. You have to make do with youtube unboxing videos, which are good, but leaves much to be desired. FWIW, I'm now seeing the value of iPhone's especially for people already in the eco-system. I could have never seen this before
I like bootstrap, but only for bootstrapping my project...or using it for backend/admin styling. Bootstrap is really just a style guide (with some good styles for layout), however if you've got design comps to work from, it's probably better to make your own style guide. I mean, if they could somehow accomplish making this process easier, then that'd be a game changer: basically less like a framework and more like a library.
EDIT
a good example: If you wanted to rebuild hacker news, would you start with bootstrap? I wouldn't
Hi Finbarr, I'm interested in learning more about this strategy. I've been using the Garber-Irish method (http://viget.com/inspire/extending-paul-irishs-comprehensive...) for running scripts based on controller/actions, but everything is still always served to every page...With your solution, only truly global scripts seems to be served. I'll try to throw up a test app on github to test out what you've done here, but do you have any existing app that uses this paradigm? I'd love to take a closer look.
How do you know that someone knows what he/she is doing? You can't always just look at the end result. For example, designing a web page today, you can still use tables to layout the structure and have the same look as a non-table layout; but obviously the latter is more desirable on so many levels.
80-20 principle working here. Not to be picky, but I think most app must've been downloaded at minimum a few times, if it's even by friends of the app builder.
Heard about sammy, but never looked into it until now. It looks really interesting. I've been looking at emberjs for the past couple of days and I do like what I see, but I always felt it was a little too heavy for what I really wanted. I'm just not ready to make my app just an api enpoint...it's just too much abstraction. Regardless, I'll continue to follow emberjs.
"Global mass market" meaning? try to have a more focused definition for your audience. It all depends on the audience in general. For example, if you're making an e-commerce site, you wouldn't want to limit it to just folks who have a twitter/facebook account...but then again that depends on what you're selling. If however you were making some sort of a social app that leverages people's connections already, then there's really no need to use any other authentication strategy than OAUTH. So I'd say think about your target audience and make your decision.
I think you're right about the "slaving" away practice part. After all, one of the world's greatest minds Von Neumann put it this way: “In mathematics you don't understand things. You just get used to them.”
I agree. Just like dropbox gets more useful when your friends are using it. This is possibly why a google social network doesn't seem to work: all your contacts are already in gmail, there's no added benefit, no viral effect when they add a 'social' network like facebook is. If I want to talk to someone, I'll just gchat.
"..possible to understand the entirety of practical computation from top to bottom without C..." - what level of understanding are you talking about? You don't need to implement data structures, for example, in order to know how to use them, but implementing them gives you deep understanding of the trade-offs you need to make, and implementing them in C specifically helps even more. You get to dig into the memory with malloc for example, you "see" and can even calculate all the memory that each struct will use up. I mean, this level of enlightenment does so much good, even if you don't use C to write production code on a daily basis.
You're so right about learning how to deploy your app. I'm using linode myself. I've been investing some time learning to use Chef to provision my servers. And Capistrano for deployment. This is a bottleneck of uncertainty for me, so I just finally decided to forget everything else and focus and figuring this thing out. By the way, if anyone has a good link to a tutorial on provisioning linodes with Chef Server, I'd love to have a link. In the meantime, I'm grinding...