Great there are other true open-source tools to be used zed, nvim.
I also noticed that copilot nowadays is forcing you to upgrade to their with following text:
"You've reached your monthly code completion limit. Upgrade your plan to Copilot Pro (30-day Free Trial) or wait until 2025-12-19 for your limit to reset to continue coding with GitHub Copilot"
Was using it actually like smarter auto-completion. But paying for that, hell no.
> Great there are other true open-source tools to be used zed, nvim
without going into the actual qualities of the editor, they simply lack extension support, for now.
In the embedded space, many manufacturers have switched - or are switching - to a suite of VSCode plugins and gradually discontinued the previous tools. Which is great on one hand: they don't have to keep supporting heavily modified IDEs from 10 or 20 years ago and they can better integrate with the rest of the ecosystem of plugins, scripts automation and such. LSP has been a good thing.
The problem is that you are now at the mercy of microsoft not fucking up with the environment at every other release. To put it simply, we are screwed. And i tried for so long not to use it because i knew this day would come, but it's just so much better.
And no, i will not just use a text editor and a makefile. I want an IDE. IDEs are good, when they seamlessly integrate with tools.
Now every system design interview expects you to build some monstrous stack with layers of caching and databases for a hypothetical 1M DAU (daily active users) app.
> Bumble's difficulties reflect evolving feelings about dating apps as habits shift and people report app fatigue. Shares of rival firm Match Group, whose portfolio includes Tinder and Hinge, have dropped about 79% since peaking in April 2021.
> Dating apps have become an increasingly harder pitch to shareholders as paying users have either fallen off or, in Bumble's case, decided they want to pay less for the service. With user fatigue on the rise, dating app companies have scrambled to stay relevant by pouring money into creating a more unique user experience.
Any reason you stick to ruby? Why not use any statically typed language which offers this feature out of the box? We don't argue against typing. We argue about typing like it is done in ruby rbs/sorbet.
This is just a rehash of the discussions people were having about Smalltalk/Lisp 20 years ago... All the Java/C++ IDE people who were wondering how people survived without those tools, forgetting that Smalltalk/Lisp have live-coding, REPLs, and their own tools. Ruby is the same, the terseness + REPL/live-coding makes it easy to be productive and write bug-free code.
I know I'm far, far more productive in Ruby versus, say, C++ or Odin (my newest hobby language).
It is developer responsibility to ensure that you will not receive cat during designing stage of your classes. And inheritance is bad, this is also sharp knife. But annotating everywhere
sig { params(cat: Cat) }
does not improve your design, it just makes noisy and clumsy. I would think that if your code need type annotations, it smells like bad design and should be considered for refactoring.