Hacker Newsnew | past | comments | ask | show | jobs | submit | more figured's commentslogin


the best part of the post for me, was the interview with Posterous. Amazing how much they have done, with a four man team.



previous post: good comments http://news.ycombinator.com/item?id=443542


I know you are asking about ruby and python, but I don't think their strengths lie in interfacing with bluetooth, gps hardware devices, and running background jobs. You might want to look at some more industry standard languages.


Python and Ruby both work fine for bare metal systems programming. Plenty of bare-metal systems programming projects have been executed on both.

I'm a Ruby advocate, but if "being like everyone else in industry" is one of your decision axes, Python is a more conventional choice for low-level programming (at least, outside of security).

The "industry standard language" choice you're alluding to is C, which is a terrible choice for a primary language in 2009.


"It is this type of change that has lead me to automate my regression testing"

Maybe I am wrong, but I think this post from Sam is about making sure you automate your test environment, so you can keep up with changes. Not complaining about how fast Rails changes.


The quote at the top of the page says: "the greatest difficultly of Rails development is that 'best practices' have a shelf life of < 12 months"

Sam is quoting this (as opposed to making the statement himself), but putting it at the top of the page seems to indicate that he agrees with it.

My understanding of the post is that Sam also deplores the rapid pace of change, and has automated his test environments as a workaround.


The way he worked through the design really resonated with me, especially when he would break away from his original only to come back to it later on.



the fckeditor plugin handles this problem, we use it at our business and people seem to like it.


HTML is the metadata around your content, and CSS is the style that you apply to your content.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: