joshvince
Joined 5 years ago
Joined 5 years ago
One of the compelling reasons to write JS on the server was to have the same language and ecosystem in the client and server, and things like Turbo for Rails really go a long way towards delivering on that for Ruby (although of course you still need to understand javascript and browsers.)
That said, if you're already familiar with something else, then pick the most mature batteries-included framework in that language. Languages are just a tool for the job, it's incredibly unlikely as a solo dev that you can pick a "wrong" one.
Perhaps it’s worth reflecting on whether, in a pandemic, someone’s personal freedoms are incompatible with the means by which a virus can be prevented from spreading. And then, what is “worth” more?
The fact that part of the journey involves mutually beneficial behaviours (like using VC money to acquire more users, build a better UX, and make the community larger) is just an accident, and the incentive to capitalise the whole shebang will always win out.
This sort of thing feels like The Price We Eventually Pay for a massive, free-to-use online community.
This is spot on. Current state-of-the-art models are, in my experience, very good at writing boilerplate code or very simple architecture especially in projects or frameworks where there are extremely well-known opinionated patterns (MVC especially).
What they are genuinely impressive at is parsing through large amounts of information to find something (eg: in a codebase, or in stack traces, or in logs). But this hype machine of 'agents creating entire codebases' is surely just smoke and mirrors - at least for now.