Conversation

Notices

1. Embed this notice
   hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 08:29:05 JST hobbsc

   time to lay into some contract work that i neglected while i was sick. i'm doing my damnedest to containerize a legacy application and boy is it an uphill fight.

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 08:29:04 JST esmevane, sorry

     in reply to

     @hobbsc rails?

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 08:31:55 JST esmevane, sorry

     in reply to

     @hobbsc yup that’s what I figured! Containerizing some of those asset build processes can be such a hassle, especially if you have a stack which is a few years past on updates

   • Embed this notice
     hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 08:31:56 JST hobbsc

     in reply to

     • esmevane, sorry

     @ironchamber yeppers. you've touched this codebase. it ain't been upgraded in a hot minute.

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 08:32:17 JST esmevane, sorry

     in reply to

     @hobbsc oh that’s good. At least there’s that!

   • Embed this notice
     hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 08:32:18 JST hobbsc

     in reply to

     • esmevane, sorry

     @ironchamber thankfully it's being put on life support.

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 08:55:38 JST esmevane, sorry

     in reply to

     @hobbsc even recent upgrades to recent upgrades are a little too expensive imo, the framework is built on a rickety scaffold of paper clips lol

   • Embed this notice
     hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 08:55:39 JST hobbsc

     in reply to

     • esmevane, sorry

     @ironchamber yeah, wrap this dude in an OCI container, update the underlying servers, run it probably with podman, add an updated external database, and let it rot.

     biggest challenge right now is circular system library dependencies. i'd almost rather deal with this than another rails upgrade, though.

   • Embed this notice
     hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 09:09:42 JST hobbsc

     in reply to

     • esmevane, sorry

     @ironchamber i never thought i'd say it but i'm happy to not be using rails these days. i do miss ruby but not rails.

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 09:09:42 JST esmevane, sorry

     in reply to

     @hobbsc it’s such a mess. callbacks, inheritance, shoving everything into mixins and saying it’s “clean”; simply determining cause and effect is like 12+ file bounces for me some days, and I need the whole suite of apps and client apps running to verify, because those same problems discourage people from doing any real testing. No thanks

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 09-Sep-2024 09:13:06 JST esmevane, sorry

     in reply to

     @hobbsc Haha yeah. You’re right though, just writing it in Ruby and then plugging that into Rails is still great. Works wonderfully

   • Embed this notice
     hobbsc (hobbsc@social.sdf.org)'s status on Monday, 09-Sep-2024 09:13:07 JST hobbsc

     in reply to

     • esmevane, sorry

     @ironchamber it seemed like a good idea at the time... 🤷♂️