Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Cassandra is only carbon now (xgranade@wandering.shop)'s status on Saturday, 07-Mar-2026 21:12:55 JST Cassandra is only carbon now

   "It writes boilerplate faster."

   Is that all we aspire to now? Not abstraction or templating or better language design, just... output boilerplate faster.

   It's depressing.

2. Embed this notice
   Matt Hamilton (eriner@noauthority.social)'s status on Monday, 02-Mar-2026 14:01:19 JST Matt Hamilton

   Someone reportedly deployed an energy oscillation (?) in the Strait of Hormuz with the ability to disrupt onboard electronics (GPS, clocks, etc).

   IIRC, if you remove the load (a capacitor) across a crystal oscillator, the resonant frequency increases which would cause the clock to run faster.

   It allegedly disrupted GPS reception as well.

3. Embed this notice
   Jeff Johnson (lapcatsoftware@mastodon.social)'s status on Wednesday, 10-Sep-2025 01:39:16 JST Jeff Johnson

   Apple hardware is more powerful than ever, but this is not reflected in the user interface, because as fast as the hardware has become, Apple software has become de-optimized faster.

   It’s incredible how slow and clunky things feel on even the latest and greatest hardware.

4. Embed this notice
   Masto.host (mastohost@mastodon.social)'s status on Thursday, 02-Feb-2023 17:29:18 JST Masto.host

   in reply to

   @michael Yep, I agree.

   It's always a tradeoff. Using your example (1001 jobs) if you have 5 threads on a 'default' worker and 5 thread on the 'push' worker that will be slower overall to process than having a single Sidekiq worker with 10 threads. But yes, the single push will go faster.

   It depends on what you want to optimise for and what your bottleneck is at a given moment. If there is a surge in federation, you need to optimise differently than a surge in engagement.

   @aral