11–20 of 64 posts
It's there a "default" web framework for Go which most of people use?
Earlier quoted context omitted.
> Laravel, the framework that made me quit PHP. I would be interested to hear more.
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…
God help us if it this project becomes the normal way of writing http go servers applications. Maybe at that point it's time to become an embedded rust programmer or a monk.
It's there a "default" web framework for Go which most of people use?
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.
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?
IMO it's a rough way to make a web page but people keep doing it so it must have some advantages.
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…
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 legacy software beyond repair and being responsible with what you've got.
I think there is no better way to get your hands consistently dirty than with PHP.
Coincidence: I do embedded Rust, and my wife is a buddhist monk. ;-)