Live data from Hacker News

Goravel, Web framework inspired from Laravel in Golang

github.com

41–50 of 64 posts

Re: Goravel, Web framework inspired from Laravel in Golang

#41
post #8

Earlier quoted context omitted.

My intuition is that Golang people dislike frameworks.

So they roll their own stuff each time they do a web app?

Composition is king.

The standard library defines some decent interfaces already around HTTP handling and SQL calls. Most libraries are built to integrate with them. Then interfaces like io.Reader and io.Writer mean you can pretty much use anything to read requests and write responses.

This means that usually you're composing libraries and some application code together, rather than building everything on top of some jack of all trades framework. You get to choose the best tool for each job.

Re: Goravel, Web framework inspired from Laravel in Golang

#42
post #14

Earlier quoted context omitted.

Not OP. While I didn't quite PHP. I just don't work with Laravel. A lot of good points are written down here: https://old.reddit.com/r/PHP/comments/131t2k1/laravel_consid... In short, it just doesn't use good programming principles. It's not just easy to write code with bad principles, it's everywhere in the tutorials. There's of course Laravel apps out there that do have good programming principles. It's very much p…

Also not OP, but the linked reddit post sums up one of the major reasons I had to get out of PHP several years ago. Everything is/was moving to Laravel in PHP land. I got tired of dealing with highly coupled, non-unit testable code that seemed to go out of it's way to ignore SOLID principles. God help us if it this project becomes the normal way of writing http go servers applications. Maybe at that point it's time t…

What would you like to do with PHP/Laravel that isn't unit testable? Laravel is, from my experience, written in a way that specifically makes testing of most things very easy.

Re: Goravel, Web framework inspired from Laravel in Golang

#43
post #2

Laravel, the framework that made me quit PHP. Not sure the concept of "one framework doing everything" will resonate well with the wider Go community. I will keep an eye on it though.

care to elaborate? interested to hear more about your use case back then

Overly pedantic programmers always have trouble conforming to a framework where compromises are made in ways they can't get behind. For every one of these, there a thousands of programmers who are very successful with the same framework.

Re: Goravel, Web framework inspired from Laravel in Golang

#44
post #7

Earlier quoted context omitted.

Also interested in hearing more - first person i've heard say they do not like Laravel...

Poke around a bit more; you'll find plenty of people don't care for it.

Overly pedantic programmers always have trouble conforming to a framework where compromises are made in ways they can't get behind. For every one of these, there a thousands of programmers who are very successful with the same framework.

Re: Goravel, Web framework inspired from Laravel in Golang

#45
post #17

Please, no. While you can write really clean code in modern PHP, Laravel is a collection of anti-pattern. PHP has a bad reputation because in the past it was hard to implement clean code because of inconsistencies and lacking language features. PHPs reputation should improve, but Laravel is working against it. Please don't bring Laravel to Go.

Can you give a concrete example of what you mean by “Laravel is a collection of anti-pattern?” I would really love to understand what you are referring to.

Re: Goravel, Web framework inspired from Laravel in Golang

#46
post #38
post #2

Laravel, the framework that made me quit PHP. Not sure the concept of "one framework doing everything" will resonate well with the wider Go community. I will keep an eye on it though.

Since this has generated quite some interest, the reasons I dislike Laravel are: - so. many. godobjects. - I dislike ORMs. I could not put my finger on it, while using PHP frameworks, because they were omni-present; but after using Python, Go, and C#, I found it to be easier for me to just avoid the overhead of an ORM. - Terrible structure. Sorting classes by type is something I have experienced to be generally less…

I agree Laravel is a bit too much magic, but I’ve found Eloquent to be a top notch ORM. It hasn’t really failed me in any way, so I’d be interested to hear what you specifically disliked about it.

Re: Goravel, Web framework inspired from Laravel in Golang

#47
post #14

Earlier quoted context omitted.

Not OP. While I didn't quite PHP. I just don't work with Laravel. A lot of good points are written down here: https://old.reddit.com/r/PHP/comments/131t2k1/laravel_consid... In short, it just doesn't use good programming principles. It's not just easy to write code with bad principles, it's everywhere in the tutorials. There's of course Laravel apps out there that do have good programming principles. It's very much p…

Also not OP, but the linked reddit post sums up one of the major reasons I had to get out of PHP several years ago. Everything is/was moving to Laravel in PHP land. I got tired of dealing with highly coupled, non-unit testable code that seemed to go out of it's way to ignore SOLID principles. God help us if it this project becomes the normal way of writing http go servers applications. Maybe at that point it's time t…

People like you, not meant personally, are the reason I abandoned PHP. Too much dogma. Too much nonsensical paradigms without considering pragma.

Who gives a shit about SOLID or OO.

I used to love PHP for its simplicity. That was before zealots of your type flooded the ecosystem.

You wanted to apply what they taught you in uni, which was Java, to PHP. PHP was fine before. I earned good money with it and had fun doing so. Then 2010 the next generation of clueless devs enters the scene, polluting it with their nonsense.

Very much what's happening in Go right now with the cloud microservices fetish.

Can't you booksmart idiots STFU for once and let people do the pragmatic and sensible approach?

Fucking Hipsters

Re: Goravel, Web framework inspired from Laravel in Golang

#48
post #20

Earlier quoted context omitted.

When I studied computer science, I promised myself to never touch PHP again. But PHP has more to give than just as a birthing ground for teenage programmers. When I many years later accepted a PHP job as a senior developer, PHP provided a consistent experience of "bad practice everywhere", a fractal of cringe I couldn't ironically reproduce. Working with this for a year taught me a lot about how to deal with critical…

Many of my programming jobs in PHP had me working with people that were super anal about "good coding practices". Especially the Symfony guys seem to try to be the new ultra-corporate Java. So I don't think it a issue with the language but more that you didn't find your people. (Personally, I actual like working with legacy crap. It's easy money and reminds me of the past when things were simpler.) I feel most of the…

Symfony was the worst. Holy shit dude. I still have to deal with a legacy Symfony project, which needs to be rewritten because of their... I don't even know what to call it.

That stof guy was one of the worst. Inconsistencies, incompatibility. But the dogma was strong.

Indeed they wanted to be the Java of PHP. And so inefficient. Imagine duplicating all variables of a request context for dogmas sake. So you can later do Request->getVar() from their own copy. It shows a basic not understanding of the language.

Re: Goravel, Web framework inspired from Laravel in Golang

#50
post #38
post #2

Laravel, the framework that made me quit PHP. Not sure the concept of "one framework doing everything" will resonate well with the wider Go community. I will keep an eye on it though.

Since this has generated quite some interest, the reasons I dislike Laravel are: - so. many. godobjects. - I dislike ORMs. I could not put my finger on it, while using PHP frameworks, because they were omni-present; but after using Python, Go, and C#, I found it to be easier for me to just avoid the overhead of an ORM. - Terrible structure. Sorting classes by type is something I have experienced to be generally less…

While I enjoyed my (small) foray into the world of Laravel, I'm happy to see something other than unabashed praise for Laravel here on HN.

A technical decision should be done by weighting it's pros and cons, not just by looking at the pros.

Agree on the 'Sorting classes by types', it's something I've always found surprising too, and love the car-collection metaphor.

Post reply on HN