Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Replacing Ruby on Rails: Let's Go

madebymany.com

Post reply on HN
Print view View original

61–70 of 89 posts

Re: Replacing Ruby on Rails: Let's Go

#61

Post by stcredzero »

higherpurpose wrote: post #5
colbyh wrote: post #2

I like Ruby/Rails, I like Go. I like frameworks that make your life easier when starting a new project. I don't think Go is anywhere near the list of languages to build a Rails successor on top of. Rails can do so much of the cool stuff it does because Ruby is an incredibly flexible language. Go, on the other hand, could be described as "inflexible as a feature". You have a beautifully simple language that optimizes…

I for one would like to see a serious Go-based alternative to Wordpress. Virtually every major CMS out there uses PHP, and all of them are highly prone to hacking.

I would also like to see a serious Go-based alternative for forums. Simple Machines is truly excellent, but it's still in PHP. Go would be a far better alternative to build upon from the standpoint of security.

Re: Replacing Ruby on Rails: Let's Go

#62

Post by karmajunkie »

BSousa wrote: post #56
matt2000 wrote: post #53

I never personally learned Rails so I'm just an interested observer, but can someone explain the problems with Rails currently? And why the switch in language rather than just making fixes to the framework? After looking through the article it doesn't seem like there was a very strong case made for Go. Thanks!

In a nutshell: Rails isn't shinny anymore. By migrating from (now) old Rails to new shiny Go, people can write these kinds of articles and pretend to be cutting edge and forward thinking.

its a bit more complicated than not being shiny anymore. For a lot of veterans, what's touted as best practices in the Rails community lead to maintenance headaches and performance issues in large scale long-lived applications. Rails apps tend to have a high degree of coupling internally and to gems that Just Work™ (except for when they Just Don't™).

Re: Replacing Ruby on Rails: Let's Go

#63

Post by aikah »

thibaut_barrere wrote: post #59
iends wrote: post #33

Earlier quoted context omitted.

What do you see the app domains of Rails and Go as?

I've worked (as a freelancer) on a number of apps recently using Rails for the "front back-end" and either Erlang or Go for the "back back-end" and it's been working great. Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Erlang and Go work nicely for all the "heavy work", think se…

> Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff.

Nothing that Go cannot do. The only difference between Go/web and Rails is the maturity of the libraries.

Of course Go libs are way less mature for various "business tasks".

Re: Replacing Ruby on Rails: Let's Go

#64

Post by thibaut_barrere »

aikah wrote: post #63
thibaut_barrere wrote: post #59

Earlier quoted context omitted.

I've worked (as a freelancer) on a number of apps recently using Rails for the "front back-end" and either Erlang or Go for the "back back-end" and it's been working great. Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Erlang and Go work nicely for all the "heavy work", think se…

> Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Nothing that Go cannot do. The only difference between Go/web and Rails is the maturity of the libraries. Of course Go libs are way less mature for various "business tasks".

You can do that in Go, yet like pointed out in [1], it tends to take more effort (well, this has been my experience at least).

But well: do what works for you, really :-) I'm not commenting to persuade you, I'm just sharing one data point.

[1] http://blog.gopheracademy.com/advent-2014/atlas/

Re: Replacing Ruby on Rails: Let's Go

#65

Post by wukerplank »

0xdeadbeefbabe wrote: post #48
whateveracct wrote: post #45

Go seems like a terrible choice for any programming problem that requires data modeling/manipulation. Basic structs, slices+maps, and loops are all you have. Go is good at plenty of things, but building abstractions is not one of them.

Sorry, I'm not from around here I guess. What do you mean? Have you seen etcd https://github.com/coreos/etcd or sync.pool?

I read your posts and I don't know if I just don't understand you or if you are trolling.

I believe what the parent post refers to is that Ruby - being a dynamic language - is way more flexible with types and data structures. On top of that it has very convenient methods for data manipulation. This allows you to express solutions in a fewer lines of code compared to lower languages (with the added downside of slowness of course).

Re: Replacing Ruby on Rails: Let's Go

#67

Post by aikah »

thibaut_barrere wrote: post #64
aikah wrote: post #63

Earlier quoted context omitted.

> Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Nothing that Go cannot do. The only difference between Go/web and Rails is the maturity of the libraries. Of course Go libs are way less mature for various "business tasks".

You can do that in Go, yet like pointed out in [1], it tends to take more effort (well, this has been my experience at least). But well: do what works for you, really :-) I'm not commenting to persuade you, I'm just sharing one data point. [1] http://blog.gopheracademy.com/advent-2014/atlas/

Did you write Gopher academy (fellow french?) ?

Re: Replacing Ruby on Rails: Let's Go

#68

Post by thibaut_barrere »

aikah wrote: post #67
thibaut_barrere wrote: post #64

Earlier quoted context omitted.

You can do that in Go, yet like pointed out in [1], it tends to take more effort (well, this has been my experience at least). But well: do what works for you, really :-) I'm not commenting to persuade you, I'm just sharing one data point. [1] http://blog.gopheracademy.com/advent-2014/atlas/

Did you write Gopher academy (fellow french?) ?

No I didn't! Yet I felt exactly the same. Sorry if my message was confusing :-) (I'm french indeed).

Re: Replacing Ruby on Rails: Let's Go

#69

Post by Kabukks »

higherpurpose wrote: post #5
colbyh wrote: post #2

I like Ruby/Rails, I like Go. I like frameworks that make your life easier when starting a new project. I don't think Go is anywhere near the list of languages to build a Rails successor on top of. Rails can do so much of the cool stuff it does because Ruby is an incredibly flexible language. Go, on the other hand, could be described as "inflexible as a feature". You have a beautifully simple language that optimizes…

I for one would like to see a serious Go-based alternative to Wordpress. Virtually every major CMS out there uses PHP, and all of them are highly prone to hacking.

I'm working on Journey[1] which, while "just" a blogging engine, has plugin support via Lua in the development branch. That feature is not stable yet, but hopefully in the next few days.

[1] https://github.com/kabukky/journey

Re: Replacing Ruby on Rails: Let's Go

#70

Post by matthewmacleod »

aikah wrote: post #63
thibaut_barrere wrote: post #59

Earlier quoted context omitted.

I've worked (as a freelancer) on a number of apps recently using Rails for the "front back-end" and either Erlang or Go for the "back back-end" and it's been working great. Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Erlang and Go work nicely for all the "heavy work", think se…

> Rails works great for things like authentication, creating a nice and maintainable UI, handling billing code, sending emails, managing the database schema, and all the web related stuff. Nothing that Go cannot do. The only difference between Go/web and Rails is the maturity of the libraries. Of course Go libs are way less mature for various "business tasks".

It's also 'nothing that C cannot do', but we still don't generally find it being used for such!

I've tried writing web front-ends in Go. It's a fiddly pain in the arse, and the benefits aren't really obvious. If it works for your situation then use it, but IME they're targeted at different problem domains.

Post reply on HN