21–30 of 64 posts
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?
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?
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…
Laravel was the first framework, that "just worked" and had everything, you need to make your first steps in a web application. Nowadays, people write PHP components that are usable in Laravel and that means a lot of code out there is compatible to a lot of other code. That alone did a lot to the PHP community. 2010 or so, the PHP landscape was much more scattered and things didn't look good.
Since then a lot happened and Laravel carries old stuff with it, and I'm very happy about that! I'd hate to be forced to do big refactoring work on every update of the framework. As strange as some decisions in Laravel are, they try new things, and they also try to stay compatible to the old stuff. Between Laravel 5.5 (released 2017) and 10 there were not much breaking changes. For a framework, this is a big plus.
You can almost hear one of these dudes say it.
https://m.youtube.com/watch?v=njUa_1FY8rA&pp=ygUPVGhlIGhvYmJ...
Goooravell...
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.
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…
I think the reddit post missed the point multiple times. Laravel does not use the best principles everywhere, yes. Taylor Otwell is a (very) strange person, yes. But "Laravel should be considered harmful for the PHP community" is just wrong. Laravel was the first framework, that "just worked" and had everything, you need to make your first steps in a web application. Nowadays, people write PHP components that are usa…
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…
I think the reddit post missed the point multiple times. Laravel does not use the best principles everywhere, yes. Taylor Otwell is a (very) strange person, yes. But "Laravel should be considered harmful for the PHP community" is just wrong. Laravel was the first framework, that "just worked" and had everything, you need to make your first steps in a web application. Nowadays, people write PHP components that are usa…
Earlier quoted context omitted.
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…
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…
I feel most of the PHP community is pretty mature these days. More pragmatic than Rust, sure but that is a good point in my book. Though I am glad you found your enlightenment.
It's there a "default" web framework for Go which most of people use?
AFAIK, no. There are some helper frameworks [1], but none of them is dominant. Two possible reasons: it's quite easy to write a (web) service with the library functions (it even includes a gzip stream), and it's practically impossible to write an ORM framework like you have in Java and Python, so the Go frameworks I've seen are basically a bunch of helper functions. [1] https://github.com/avelino/awesome-go#web-frame…
genuinely interested in knowing why it is so. I quite like Go, but I also like Django, so I would like to know why a Django-like ORM would not be feasible.