Replacing Ruby on Rails: Let's Go • Hacker News Board

Re: Replacing Ruby on Rails: Let's Go

#31

Post by CookWithMe » Thu, Apr 23, 2015, 5:26 PM UTC

> Simply "not using Rails" anymore however is, well, not that simple!

After the OP has described why he likes Rails ("good toolset", "Ruby gems cover everything"), I would've really liked to know why OP wants to switch away from Rails.

> so what's around that has a chance of replacing Rails? Go!

Again, the OP gives no reason why he switched to Go instead of looking at another web framework for Ruby, and also not why he chose the particular Go frameworks to replace Rails.

That's what would've really interested me, after the introduction I didn't quite see a Go-tutorial coming...

Re: Replacing Ruby on Rails: Let's Go

#32

Post by steamy » Thu, Apr 23, 2015, 5:27 PM UTC

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.

Even Node or Ruby based static site generators can't compete with WP & PHP on the server. The ubiquity of PHP on web server installations is astounding and the ease of use of WP sp. for non techies in contrast with the technical knowledge and expertise expected to build and maintain a Jekyll powered website or [insert your favorite Nodejs generator] powered website.

Re: Replacing Ruby on Rails: Let's Go

#33

Post by iends » Thu, Apr 23, 2015, 5:27 PM UTC

BringTheTanks wrote: post #17

Odd. RoR and Go address entirely different app domains. The only thing that connects them is that RoR was trendy yesterday, and Go is trendy today. If this is the rationale for replacement, the author will be writing plenty of "replacing" articles in the years forward.

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

Re: Replacing Ruby on Rails: Let's Go

#34

Post by 0xdeadbeefbabe » Thu, Apr 23, 2015, 5:32 PM UTC

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…

The idea that programming languages are "worlds apart" and "vastly different" is hyperbole that would make Turing frown or maybe giggle. Have you considered that Ruby is written in C [0], and that you can do plenty of things with a general purpose programming language and some good ideas?

Edit: Would you care to substantively explain the downvote(s)? The parent is so preoccupied with frameworks he's overlooking the basics.

[0] http://en.wikipedia.org/wiki/Ruby_%28programming_language%29

Re: Replacing Ruby on Rails: Let's Go

#35

Post by atmosx » Thu, Apr 23, 2015, 5:32 PM UTC

steamy wrote: post #32

higherpurpose wrote: post #5

Earlier quoted context omitted.

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.

Even Node or Ruby based static site generators can't compete with WP & PHP on the server. The ubiquity of PHP on web server installations is astounding and the ease of use of WP sp. for non techies in contrast with the technical knowledge and expertise expected to build and maintain a Jekyll powered website or [insert your favorite Nodejs generator] powered website.

Sorry but that's doesn't seem like a compelling argument. We're not talking about editors... You don't choose the language based on the ubiquity of the language on UNIX/Windows servers, otherwise everything would be running on Perl probably.

I guess most people, like me, choose the language they know/like and then setup the server accordingly.

Re: Replacing Ruby on Rails: Let's Go

#36

Post by nine_k » Thu, Apr 23, 2015, 5:35 PM UTC

vec wrote: post #15

higherpurpose wrote: post #5

Earlier quoted context omitted.

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 don't think you're going to see a serious competitor to Wordpress in anything but PHP for a long time. The core target audience for a CMS is content creators and designers without strong compsci backgrounds. The things that make it hackable (trivial to modify in-place, extremely forgiving of type errors, no internal sandboxing, etc.) are the very things that make it attractive to non-developers. Nothing is going to…

The beauty (which can also be seen as a disadvantage) is that writing Go does not exactly require comp sci skills. I suspect that Go is even simpler than modern PHP as a language.

You can of course go full comp sci implementing clever algorithms in Go, but you could do that in PHP, too, and none of content creators is usually interested in this.

Re: Replacing Ruby on Rails: Let's Go

#37

Post by steamy » Thu, Apr 23, 2015, 5:36 PM UTC

atmosx wrote: post #35

steamy wrote: post #32

Earlier quoted context omitted.

Even Node or Ruby based static site generators can't compete with WP & PHP on the server. The ubiquity of PHP on web server installations is astounding and the ease of use of WP sp. for non techies in contrast with the technical knowledge and expertise expected to build and maintain a Jekyll powered website or [insert your favorite Nodejs generator] powered website.

Sorry but that's doesn't seem like a compelling argument. We're not talking about editors... You don't choose the language based on the ubiquity of the language on UNIX/Windows servers, otherwise everything would be running on Perl probably. I guess most people, like me, choose the language they know/like and then setup the server accordingly.

We're talking about two completely different market segments here; the corporate/enterprise market which provides more room for creative & cutting edge solutions to be implemented and then there's the SME & consumers which favor more conventional, user-friendly and "popular" solutions like WP and the likes.

Re: Replacing Ruby on Rails: Let's Go

#38

Post by xasos » Thu, Apr 23, 2015, 5:44 PM UTC

navd wrote: post #4

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 just don't see a monolithic web framework being high up on the list of "must haves". And I think that's what makes Go so welcome to many people. In fact, I'm tired of frameworks that do everything for me because they tend to do everything just "well enough". And I noticed the OP is using Martini - which isn't necessarily bad - but it's not needed. It does make learning a language like Go a lot easier for newcomer…

In fact, Go's standard library is fantastic, so you don't need Martini for many things. I think it provides a nice layer on top of the code for comprehensibility when reading through code

Re: Replacing Ruby on Rails: Let's Go

#39

Post by jlhonora » Thu, Apr 23, 2015, 5:45 PM UTC

arxpoetica wrote: post #10

higherpurpose wrote: post #5

Earlier quoted context omitted.

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've had the same thought, but using Node (which is more accessible to a wider group of people). Part of the (sad) state of affairs that made WordPress so popular was accessibility to the code. Can't be overlooked.

Ghost (https://ghost.org) is built with Node

Re: Replacing Ruby on Rails: Let's Go

#40

Post by jlhonora » Thu, Apr 23, 2015, 5:47 PM UTC

tptacek wrote: post #14

I've had nothing but bad experiences trying to do things I'd ordinarily do in Rails in Golang instead (and I really like Golang). Writing "Rails apps" in Golang feels a like like writing them in Sinatra used to feel: good at first, but halfway through you realize you're just wasting time reimplementing a buggier version of half of Rails. On the other hand, I've had very good experiences factoring subsets of Rails app…

Why use Rails as a frontend? One of the reasons I'm using Go for service decoupling is to get rid of Rails long startup times. I just route the requests using Nginx and skip Rails altogether.