this post was submitted on 28 Mar 2024
156 points (95.3% liked)

Technology

59381 readers
3043 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (1 children)

Production is about using the best tool for the job

I find this attitude kinda simplistic and problematic. This attitude applied elsewhere can be used as justification for all sorts of terrible things, I don't know why it should get a pass in tech. Sometimes the best tool for the job is produced by an evil company you want to boycott. Sometimes the best tool causes lots of collateral damage or harm, or has potential to lock you into an ecosystem. Maybe you want to support the growth of other tools and are willing to sacrifice some performance.

Even if only profit is considered, I think it's reasonable for a company to conclude that open source software is inherently better due to reasons that go beyond immediate utility and profit making potential by thinking longer term.

[–] [email protected] 3 points 7 months ago (1 children)

Obviously you do what you can to avoid supporting bad/"bad" companies

But... me and my engineers aren't getting paid more to make a support tool for what we are paying or to help a project out with their teething issues. So picking a solution with poor support/poor capabilities just means we are putting in a lot more hours for work that we won't get paid for.

Versus having a budget to buy tools other people developed and possibly even support. Which means we have more cycles to dedicate to what our actual job is.

And our customers aren't going to say "Hey, good for you. Thanks for supporting this project". They will say "We have downtime. We either want to be compensated or will change to a different solution.

[–] [email protected] -1 points 7 months ago (1 children)

We're all free to make the calculation that makes sense for us. Not everyone wants to sacrifice everything for profit, and this is a viable tactic.

[–] [email protected] 3 points 7 months ago (1 children)

So.. not gonna read the response where I point out it has less to do with "profit" and more to do with the people who actually do the work for a company?

Good chat.

[–] [email protected] 1 points 7 months ago (1 children)

Well I agree with that part, when I'm saying using open source vs proprietary, I'm not proposing companies use alpha software in production. I was thinking more along the lines of avoiding MS Exchange in favor of of Postfix/Dovecot/CalDAV even though Exchange is arguably superior at managing one's emails and appointments.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

For as much as we all hate MS Teams with a passion: It is not arguable. It is superior. And Exchange and Outlook couples well with MS Teams which gives you a corporate chat client, teleconferencing, document sharing, etc.

That hodge podge of tools? It is someone's job to maintain that. Likely someone who is maintaining significant parts of corporate infrastructure and doesn't have time to work through what the 55 year old waste of space refuses to even try to understand but will instantly get blamed in meetings with the c-suite if that idiot can't figure out how to write an e-mail.