sunsu

I created a similar open source project that lets you host a blog powered by your Google+ profile: https://github.com/lylepratt/Plusify

Taxing someone based on their unrealized gains only makes sense if you have liquidity! Instead of making the tax system more complicated with propositions like this, we should just switch to a consumption based tax system.

All I want to know is how long till it replaces the current implementation of WebView in the Android SDK.

150,000 acres annually.

I would much rather see a completely consumption based tax system. The mortgage interest and charity reductions could easily be left in.

I totally had this idea for a business in Austin. I was thinking about $20 for a basic car wash. Other tiers would be $30-$40. Washers would qualify to do the other car wash tiers based on their previous performance and reviews. Every washer would start out at tier one and have to earn the ability to wash in tiers above it. Hope it works out for Cherry!

I use google plus along with a simple tool I made for a really simple blog that's hosted on my domain: https://github.com/lylepratt/Plusify

He should just use my tool so he can host all those posts from his own domain while still posting to Google+: https://github.com/lylepratt/Plusify

If I were you, I would start messing around with Javascript first. Yes, there are MANY weird things about Javascript. But, the nicest thing about it (for you) is that all you need to start programming with it is a web browser!

Codecademy also has some great simple Javascript tutorials. All you need to worry about now is learning the basics, and the core concepts you learn in Javascript will apply to almost every other language you learn.

This is why I'm sticking with EC2 for now as well. Though one of my instances might go down or become unreliable, all I have to do to fix it is Stop and Start it!

No messing with support tickets or waiting (sometimes hours) on someone to talk out to the data center to troubleshoot it. Its just fixed.

Feature Suggestion: would be great if they automatically lazy loaded images as well.

This just isn't universally true. Some ccTLDs will indeed take anywhere from 12 to 48 hours to update.

If you are launching a service on a new domain and are about to link to that domain to make the launch public, do not assume that just because its working on your computer after 10 minutes that it is working for the rest of the US, or the world.

I think it's fairly ridiculous that jQuery Mobile is on the list, but Sencha Touch is not.

Nice tool! This will be helpful in the Sencha forums when a dev asks you for code related to bug reports. Although, I wish it was using ST2, and not ST1.

Here's one I did in a couple of minutes that displays HN items: http://senchafiddle.com/#Ba4nZ -- Fiddle Mode http://senchafiddle.com/server/full.php?token=Ba4nZ -- Full Screen

Lately, I've been experiencing update approval periods of about 2 business days. This is definitely an improvement from what it used to be.

You can use Google+ to write and manage your blog, but also host the content, with a simple tool I made: https://github.com/lylepratt/Plusify

As a part of serving the blog, it backs up all your G+ posts to an SQLite database. You can set how frequently you want to check Google for content updates.

You could also check out Fwix's API.

Sencha Touch 2 is in developer preview now. It has a steep learning curve but I think it is worth it.

I think that there are times when HTML5 apps wrapped in UIWebViews make a lot of sense.

To me, I would rather spend a small amount of time getting a HTML5 app out on BOTH iOS and Android to test an idea or concept. If the app on either platform looks like it has some traction, then I'll take the time to write a native app for that platform.

This line of thought definitely does not apply to this Gmail app. I also wouldn't recommend it for anything remotely resource intensive, but the vast majority of apps are not.

The new version of Sencha Touch (version 2) is very well done. It has a steep learning curve, but I think its worth it to be able to quickly throw together an app that works on both iOS and Android to test a product idea.

So what does this mean for Windows Phone 7? Will Silverlight eventually go away for it as well? Since the majority of WP7 apps are developed with Silverlight (i think?) what will replace it?

The first programs I wrote were complex BASH scripts that solved specific problems I needed solving. I had a friend that was there to help me a long the way. But the main reasons I continued learning were because I had the immediate benefit of having my problems solved and also because I had tangible evidence of my progress. The rest snowballed from there.

I understand where Joel is coming from with his advice, but I don't think I agree with it. I had read quite a few programming books in the past (C & Java), muddled through the exercises, and thought I understood the concepts, but until I dived into solving real problems, I didn't "get it".

Hopefully battery tech will progress fast enough to power these devices. Right now it definitely isn't there as evidenced by Darpa's exoskeleton which is still powered via a cable.

I understand your point, but the documentary video said that most of the 30 people were volunteers.

Link to Github Repo: https://github.com/lylepratt/Plusify

From the article:

"I’ve already used Ruby at work to dramatically speed up some of our vaccine screens—for processing and summarizing data—but I’ve always had to pipe my numbers into R for statistics and graphing. Because unfortunately, despite all the hubbub around Ruby, no one is crunching numbers with it! I’m sick of R, though, and I want a complete solution for my numbers needs."

I'm surprised at how well it worked on my first gen iPad!

Would be great if android implemented encoding to that format now. Its a pain to try to get the same audio formats from both Android and iOS devices because both platforms encode to completely different formats.

I'll second the "watch new hires carefully".

You can save yourself a lot of problems if you just keep an eye on your new people for the first month. Obviously you don't need to be overbearing, but at the end of that first month you should do a detailed work evaluation (code review if a programmer). If the employee shows signs of producing crap in their first month, get rid of her/him then. Do not wait unless there is a really, really good reason to.

Besides being a great library, its an excellent example of well written PHP code.

Just another example of why you should enable 2 step authentication on your Google account. Seriously...do it today!