1,564 karma · joined April 16, 2008
meet me with lizi: http://lizi.ai/railsjedi
Low barrier to entry, but high barriers for completion is our theory. We'll see how it works in practice and adjust.
It also takes no equity and benefits no one except the participants.
Cheer up man! Enjoy the good times while they last :)
We'll add a "how do we work" link that brings up this information directly on the landing page.
Also, we got a great suggestion from someone else about setting up inboxes for everyone so you can just sign up with services with [yourname]@saasly.com and then we just look at your bills instead of all your email.
I seriously doubt this is anything more than a stupid omission on their part. They'll fix it and won't be doing anything notorious with your data.
Though Google.. I'd appreciate if you didn't "publicly perform" my google docs. kthx
Even a very simple Rails sample app will often take over a minute to spin up on heroku. I don't think it's smart to completely focus on server startup time when the real fix is available on most other deployment environments.
That said, I still like Heroku and can deal with this for a while until they fix it :)
Hoping Heroku will fix what I consider a major bug. Until then, I've resigned to having to redeploy to heroku in the middle of the night to avoid customers getting pissed.
Simple solution, hire someone who understands secure backend infrastructure, wire up the push notifications, and charge a small monthly fee for the service. If they could convert a small percentage of their user base, they'd make their investment back and more.
I really hope this trend continues and we can see power user replacements for Safari and Calendar as well.
Should weed out the cruft
Click it to quickly wrap any site in responsive.is.
A bookmarklet would be great too
I use pry, however I've found it's very unreliable for stepping into shoulda tests, and often it errors out. I haven't been able to find stable alternatives to the most common ruby-debug commands 'l', 'e', 'n' and 'c'.
Ruby Debug is impossible to get working in 1.9.3. The maintainer of ruby-debug has gone AWOL so we're forced to deal with solutions like this http://blog.wyeworks.com/2011/11/1/ruby-1-9-3-and-ruby-debug that don't work within bundler or a team environment.
1.9.2 + Rails 3.x is attrociously slow (30+sec). With falcon (a very unstable ruby hack) the startup speed goes to 10seconds. But 10sec is still way too slow
Sorry, it sounds bad when I just rant. In the grand of scheme of things, Rails makes me more productive as a web dev than I ever thought possible. It's just easy to pull out the daily frustrations and complain. I've been trying to help fix these issues but they are so dependent on a web of gem authors, and core ruby fixes that it takes an extraordinary amount of time.
I'm almost to the point where I think things need to be fixed top down. Matz needs to take control and try to make stuff not suck as soon as possible. Since he's working for Heroku now, it's in his best interest to push the platform and keep new users engaged.
I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.