• 7 Posts
  • 30 Comments
Joined 11 months ago
cake
Cake day: August 6th, 2023

help-circle

















  • The go community is strongly opinionated in unique ways. For example, using libraries is generally frowned upon. You either use something included in the language itself (standard library) or copy/paste the code you wrote in another project. There’s also advocacy for shorter variable names which generally seems counter to the normal “write descriptive variable name” mantra.

    All in all, I hope the ideas / opinions came from a good place and then some people took them as black & white rules. But they also come off as one or two people’s pet peeves who got to build a language around them.




  • FlumPHP@programming.devtoProgrammer Humor@lemmy.mlNames
    link
    fedilink
    arrow-up
    343
    arrow-down
    1
    ·
    7 months ago

    These people don’t even read their own literature. The Catholic church’s ban on alchemy is about falsely claiming something is a valuable metal in order to pay for debts. It has nothing to do with the occult – the ban was because it’s a sin to lie / cheat / steal. A saint is even on record saying that alchemical gold is ok if the end if product is real gold.

    With that context, of course God doesn’t give a shit if you use SQLAlchemy as long as you aren’t using it to defraud people. If you were defrauding people, it wouldn’t matter what tool you used.

    .




  • I too want my query results in an object, but thankfully libraries like sqlx for golang can do this without the extra overhead of an ORM. You give them a select query and they spit out hydrated objects.

    As far as multiple DBs go, you can accomplish the same thing as long as you write ANSI standard SQL queries.

    I’ve used ORMs heavily in the past and might still for a quick project or for the “command” side of a CQRS app. But I’ve seen too much bad performance once people move away from CRUD operations to reports via an ORM.