(no title)
EarthLaunch | 1 year ago
For small to medium web projects, the benefits of having JS across the stack has kept me from using Laravel again. That doesn't apply to all projects, though, and I still love it.
Waiting for the next thing. Toying with Deno Deploy (no association).
spiderfarmer|1 year ago
_the_inflator|1 year ago
I fiddled around with Flow, from Typo3 and a bit of Laravel.
If you only add a controller here and there and do some simple database query you can work in 20 frameworks in one language in parallel.
I side with you, frameworks per project on a rapidly changing basis won’t work. Experience is a must, 3-6 month extensive exposure to doing some heavy lifting as well as debugging is a necessity. Staying up to date and dealing with migration issues as well as older version maintenance is a must, code reviews, build pipelines, even bug fixes or change requests.
Also frameworks evolve quite a bit over time and there also seems to be trends and biases towards certain tools or add-ins in certain cases, setups, configurations.
So in my experience I never met a jack of all trades, only real masters of one framework with all the ins and outs.
unknown|1 year ago
[deleted]
n3storm|1 year ago
dotancohen|1 year ago
After doing it a dozen times in each direction it gets easier - the advantage of being old is that one has much experience.
EarthLaunch|1 year ago
One reason for switching and trying is a fascination with finding the next amazing thing, always hunting for something new and better. Usually it's only slightly better, or not better. But sometimes you find Elixir, Laravel, or Deno. And it's more fun and productive, plus you're ahead on the resume.