fabio,
@fabio@manganiello.social avatar

Just migrated from to .

Same API, same features, same UI, and support for other DBs than MSSQL.

One single stand-alone application vs. Bitwarden’s 10 Docker containers. 70MB of RAM vs. 2GB. 3MB of db storage vs. 300MB.

Why was a password manager supposed to take so many resources in the first place? Just because it runs on a Microsoft-only stack and on .NET’s inefficient VM? Just because somebody thought that it was a good idea to separate everything into different containers (even icons and 2fa are modeled as separate services in Bitwarden)?

It reminds me of my recent migration from Mastodon to Akkoma. I got more features, 5GB of RAM freed up and 300GB of storage freed up almost overnight.

Writing and running inefficient software that pointlessly consumes all the resources available on a machine should be a crime in a world with limited resources.

It makes me think of how much shitty bloated software like @bitwarden, probably based on awfully inefficient languages and frameworks like Java, Ruby on Rails and .NET, is running out there, pointlessly sucking up resources for doing simple jobs that could easily be done with 99% less resources.

Today’s developers, spoiled by IDEs, powerful machines, docker-compose and shortsighted “just throw more RAM at the problem” approaches, have forgotten how to write efficient software. Time for them to learn how to write good efficient software again. Software doesn’t eat the world. Only shitty software built on shitty framework does.

davidculley,
@davidculley@sigmoid.social avatar

@fabio I’m curious to learn your view on why Ruby on Rails is bad. (Sorry to distract from Bitwarden, the original issue.)

Is the design already bad? Or is the design fine, just the implementation is suboptimal?

I’ve never written Ruby code and am just wondering because DHH is always so proud of what he built.

fabio,
@fabio@manganiello.social avatar

@davidculley my experience with Ruby on Rails application mostly involves running both Mastodon and Gitlab on my servers.

In both the cases, what I’ve noticed is that it’s not the language itself that is slow and heavy (Ruby’s weight is comparable to that of e.g. Python), but Sidekiq.

Sidekiq is the standard framework used by Ruby on Rails application to schedule and run asynchronous jobs (processes, threads…), kind of akin to what php-fpm does for PHP.

In my experience, it’s hard to configure properly, and when not configured properly it ends up with endless pools of active jobs doing all kind of things and sucking up all resources you give to them.

kikobar,
@kikobar@acc4e.com avatar

@fabio perhaps AI will takeover sooner than expected... 🙄

  • All
  • Subscribed
  • Moderated
  • Favorites
  • bitwarden
  • GTA5RPClips
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • Durango
  • cubers
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • ngwrru68w68
  • kavyap
  • tacticalgear
  • ethstaker
  • JUstTest
  • InstantRegret
  • Leos
  • normalnudes
  • everett
  • khanakhh
  • osvaldo12
  • cisconetworking
  • modclub
  • anitta
  • tester
  • megavids
  • provamag3
  • lostlight
  • All magazines