_virtu

Pro tip you don’t even need an illustrator. While I do encourage hiring humans to do this work you can also use PolyCam with a phone that supports lidar, export it to Claude with Blender and voila.

I've been in elixir for nigh a decade now and the one thing that you can try to pry from my cold dead hands is the BEAM. Elixir and Gleam are my go to languages right now and damn are they fun to write and reason in, but the part that has left me never wanting to leave the ecosystem is BEAM + OTP.

- BEAM makes monoliths sexy. You don't have to worry about a bunch of microservices, just focus on using proper process division for modeling your problem. - Debugging on the BEAM is first class. Drop into an interactive shell, pull up telemetry, or recon and hammer down on where your live app is slowing down if your metrics have a blindspot.

I could go on and on. I'm constantly blown away every day by the amount of time and effort and all of the sage learnings in distributed computing problems that came out of Ericsson that became the foundation of erlang + OTP + BEAM and in turn elixir + Gleam.

At least for me, I pirate music, but I make an effort to contribute directly to the bottom line for artists. This is best done by buying overpriced merch at shows or donating directly if possible.

Have you tried reaching out to people who have installed your app and asking what they did and why they did it?

Why does the JavaScript ecosystem pride itself in not having a framework? That’s the very thing that drove me out of the ecosystem. JavaScript was my first professional language of focus and I was in love with the growth oriented mentality as a younger engineer, but the part that irked me was that I had to constantly be rebuilding the same set of patterns with different tooling, which is the special choose your own adventure hell that is the JS ecosystem.

I left it for elixir and Phoenix and never looked back. There’s just no true ownership and direction that can come close to that of Jose Valim and Chris McCord in the JS ecosystem. It’s so fragmented that it takes the fun out of maintaining a JS codebase.

I came here thinking that there would be more comments discussing this. This seems like the wrong direction to go for fixing the comfort problem. Tilting your wrists down like that is not proper typing posture.

Thanks for the rundown. I just started using cmux and the pane behavior you’re describing is my biggest gripe. I’ll check this out.

That's not the only reason I was using the tooling at the time. Specifically everything else regarding the JetBrains ecosystem kept me hooked, but when I was looking to replace what I liked in JetBrains with other tooling the last piece of the puzzle was replacing the git workflow.

Remember this type of comment. Never let yourself fall into this type of thinking when trying to understand what your users want.

Instead of passing judgement on why someone values something, why not ask?

For example, if you were to ask me why I chose to keep using an IDE that I had spent years of my life building muscle memory using perhaps you would get a better understanding of the specific part of the lifecycle I was at when paying for software.

It's not that the git gui was the reason why I signed up for the software in the first place. The git gui was the last reason for me to not jump ship when switching to something like neovim or helix. This was during a time where LSP was becoming popular so refactoring tools and intellisense were finally getting better adoption outside of the JetBrains tooling. Most of this was achievable with editor du jour + lsp plugins, but the git ui was the one piece I hadn't personally solved outside of the JetBrains ecosystem.

What’s stopping you from using it in the terminal view of VSCode? Perhaps I’m misunderstanding your comment so please forgive me if I am.

Maybe you’re saying that you wish VSCose itself was a TUI?

The commit workflow was what kept me locked in to the ecosystem for so long. LazyGit was so good that it convinced me I didn’t need JetBrains anymore. If you love the workflow with JB for commits check out LazyGit. It’s a TUI so you can use it in any editor without much friction.