Hacker Newsnew | comments | show | ask | jobs | submit | login

Many of my users were friends I met at various Ruby/Rails development circles. HomeMarks is a passion project that I have strived to re-write every few years. I threw away ~7K lines of custom MV* JS (before there were any) written in Prototype.js to create this new version in Rails/SpineJS. I hope others find it useful. History here.

HomeMarks, My First Ruby On Rails Pet Project http://metaskills.net/2006/12/21/homemarks-my-first-ruby-on-...

Hell'OO HomeMarks http://metaskills.net/2008/08/18/in-hell-oo-for-homemarks/

The "AJAX Head" Design Pattern http://metaskills.net/2008/05/24/the-ajax-head-design-patter...

-----


I never liked Rails templates because I felt the quality of the final product was never on par with what you would setup from scratch. To that end, I created my own system that I call a Rails application prototype. If you are interested you can learn more about it here.

https://github.com/metaskills/holy_grail_harness

I can see both sides of the argument here. My application prototype is really slim and focuses on bootstrapping an application with a major emphasis on testing tools. Even tho it has a JavaScript MVC framework (Spine.JS) it will remove all traces depending on your setup questions. This approach to a lean prototype means it can easily be updated like a normal Rails application and changed/forked as needed. Best of both worlds hopefully.

-----


This project from @metaskills is worth a close look, particularly to see the choices Ken's made in assembling a development stack. It's a great example of using a starter app as beginning point for a discussion about best practices. Carbon Five's RayGun is another. Compare the two and you'll learn a lot about high-powered Rails development and where it's going.

-----


I learned touch typing in high school '90 not knowing what career I would be in. I can type very fast now and love the fact that I took the time to learn. Know your instrument!

-----


http://www.youtube.com/watch?v=mGS2tKQhdhY

-----


We are software nerds people. It is supposed to be cool to se how others solve problems. It is as simple as that.

-----


To be fair, Wayne has always said that RVM was made for production first and development second. Not sure if it is fair to say it is not production ready since it has always been geared toward just that.

-----


It doesn't matter what Wayne has always said. He's designed a collection of fragile shell script hacks that want to be run as root that fundamentally change the behavior of key system commands.

-----


Root? I don't think I've ever run RVM as root. Why does it need to? Not saying you're wrong, I just don't know what you're referring to.

-----


You don't have to run them as root. You can run them as a regular user. I'm pretty sure Wayne recommends against RVM system-wide and the preferred method is just installing it for individual users.

-----


login as regular user, download some version of ruby, compile for use as logged in user, install rvm, shazzam install any version of ruby you want - all of this only applies to the logged in user and has zero impact on the rest of the system. RVM rules :)

I no longer install ruby at a system level, not needed, only users running ruby stuff need ruby installed and never use distro ruby, creates all sorts of issues...

-----


Guidelines | FAQ | Support | API | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: