Ruby | Stonecharioteer on Tech

So the other said that I could look into using the Qt4 bindings for Python with PyQt4. He mentioned that the Ruby Qt bindings weren’t maintained. … I’ll be the first to admit that’s a bad thing, though. The fact that everything is shoe-horned into Python is a really bad thing. Python is a great language, but it also allows you to write what you think is production level code after a two day bootcamp. That is dangerous. Airflow, notoriously enough, teaches users to run bash scripts from within its Python environment and treats that as a normal thing. Operations engineers who first look at it think that they can run complex shell scripts from airflow and that it’s very safe to do. Data engineers think that data munging with it is easy as pie and then complain that someone else’s DAG brought airflow down. … The ideas I just spoke about seem almost obvious to us now, but they weren’t, back in the day. Smaller frameworks made developers feel productive, but we are left writing a lot of code just to do things the right way, or we can MacGuyver stuff around and YOLO our way into an application that will inevitably break. … ## Implicit not Explicit, Ruby from a Pythonista ### Editor and LSP I experimented with LSPs for neovim, having tried `sorbet` and `solargraph`, I settled on `ruby-lsp`. I think Solargraph had some problem with resolving tests in a rails project, I’m not sure what it was, but I installed Ruby-LSP and it worked without any tweaks. I prefer that for now, but my preference might change eventually. … But after I had gotten over the initial shock, my developer brain immediately wanted to know *how* Ruby managed that. Let’s focus on that. I first ran into something related when I installed a different version of Rails and wanted to downgrade to match the version in the tutorial. Now that made my neurons fire at full power.