3 ms·

I started a project about a year ago and I specifically wanted to answer this question. As a result, I wrote that project in revel. Ultimately I don't hate rev

I started a project about a year ago and I specifically wanted to answer this question. As a result, I wrote that project in revel. Ultimately I don't hate revel and the result is an operational system today. I don't exactly regret the decision to use revel, but I also think that revel ultimately didn't bring many useful things to the party. I do know I'd have a better, more extensible easier to understand application if I had not used revel. I do know that if I was just using standard net/http I would have developed things faster. I found myself more often fighting against the framework to bend it to my will than benefitting from it. All that said, I don't think I would have the confidence that "just use net/http" is the correct answer had I not done a project in revel. I did a few projects before and after and in-between the revel project, while still actively developing and maintaining the revel project. Ultimately, I now find myself dreading working on the revel project to the point where, when I have time to spare, I'm much more likely to work on one of the non-revel projects.

GolDDranks 8y ago
I just started a project with Revel. I dabbled with Go some years ago, and I was excited to try it again because I like statically typed languages and the simplicity of Go. However, the package management story was insane. I had really hard time with that. Fortunately they are acknowledging the problems and fixing them. Also, I kept missing Rust-style error handling. I've been programming in Rust extensively for a few years, and I thought Go might provide benefits of being "a simpler (garbage-collected) Rust". However, I keep longing some nice things from Rust. Revel was... Ok. The fact that it builds the code while it's running is nice for rapid prototyping, but it was also really hard to fix if/when it didn't work. ( https://github.com/revel/revel/issues/1349 https://github.com/revel/revel/issues/1349 ) I found the default template engine to be a bit lackluster – template inheritance is the basic pattern I'd like to see everywhere as the default, but it didn't support that. The project is still in an early phase so it's hard to say more than that.
deleted 8y ago
[deleted]

GolDDranks 8y ago

I just started a project with Revel. I dabbled with Go some years ago, and I was excited to try it again because I like statically typed languages and the simplicity of Go. However, the package management story was insane. I had really hard time with that. Fortunately they are acknowledging the problems and fixing them. Also, I kept missing Rust-style error handling. I've been programming in Rust extensively for a few years, and I thought Go might provide benefits of being "a simpler (garbage-collected) Rust". However, I keep longing some nice things from Rust. Revel was... Ok. The fact that it builds the code while it's running is nice for rapid prototyping, but it was also really hard to fix if/when it didn't work. ( https://github.com/revel/revel/issues/1349 https://github.com/revel/revel/issues/1349 ) I found the default template engine to be a bit lackluster – template inheritance is the basic pattern I'd like to see everywhere as the default, but it didn't support that. The project is still in an early phase so it's hard to say more than that.

deleted 8y ago

[deleted]