imothee

I was building something similar in Go for the exact same reason so looks like there is validation for the product at least! Great work on shipping, incredibly well commented and clean.

I use railway.js in production for a social bookmarking tool. I come from a rails background but a Rails API has some up and downs. I wanted to try node and have been very impressed. I use railway.js to serve up the iOS API (private beta) and the public beta website. It serves 800 reqs/min on a shared m1.small with one process and I've had no issues with it at all.

It plays a lot more smoothly with MongoDB and I find it far simpler to hook into more modern functionality with Websockets and client side JS rendering. I had a few issues with jugglingdb (which I forked and fixed) and it's all going smoothly.

I still use Rails for some sites but Node and railway.js let me bootstrap the whole API on MongoDB in a few days and get very acceptable performance.

This got me as well, luckily I saw this post. I went straight to the checkout rather than the cart and never saw the coupon area either.

Bought and anxiously waiting for my email with the books! I've always had trouble writing wishy washy content and need to do a huge update for SEO so this couldn't have come at a better time!

Congratulations, thanks and best of luck all in one!

Hand't seen that before. Not quite the same situation but applicable, I learnt a crash course in trademarks and cover your ass for startups. Guess I should look at it as a big learning experience instead of a downer.

It's not that the app is worth less than the cost of changing the name. Though right now it seems a bit worthless to try and compete with Apple.

It's the fact that I thought I had made my intentions very clear of my intent to use the brand with Apple through iTunesConnect. Apart from releasing it I did everything else. Just feels like Apple didn't even care to look and it makes me question developing for their platform.

I kinda thought that the whole iOS platform was perfect for the little guys without needing the hassle of the cover your ass lawyers. Guess I was wrong, lesson learned the hard way.

I launched a site in production using a slightly modified bootstrap. It was a weekend project I showed off here.

Unless it gains traction, spending any time or money on a themeforest design just seems like a waste. If it takes off then I can always get it professionally designed later!

Plus, bootstrap looks amazing and the design of the site got a ton of complements from non-technical folk.

We've been using ASIHttpRequest for a few years now without issue. If the code's in place already just launch! It's rock solid for what we use it for.

If you've yet to fully integrate it then it may be worth switching but none of the one's linked seem as full featured and simple to use as ASIHttpRequest.

It's a sad day and hopefully someone else will take over the reigns.

I was trying to work out possible future site updates such as embedding contact forms on your website or possible add-ons for a premium membership.

Adding the page was about 20 minutes work so I thought let's see what the usage is and remove/hide the other for A/B testing.

If it pollutes the site I'll probably remove it or offer it as a checkbox/premium add on.