I'm a staff software engineer at Sunrun, the USA's largest residential solar installer.
I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.
I'm a staff software engineer at Sunrun, the USA's largest residential solar installer.
I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.
Server migration has been completed
Server maintenance 3:00 UTC
Your server owner is now banned from participating on lemmy's Github
Outage - Oct 14/15
Test object storage
Password limit is set to 60 characters
A thousand miles
What God or Goddess would personify Testing?
Threads and the Fediverse
Flow testing with Turbine
Rewriting the Ruby parser
Dynamic Kotlin with Zipline
MonoSketch is a cool ASCII flow drawing app fully written in Kotlin JS
Database optimization changes
Community Request Thread
Kotlin goes WebAssembly!
Welcome to programming.dev
These were exactly the things that drew me to Svelte as well. And yes, the author is right. If they had claimed that you should use Svelte for everything I would have immediately stopped trusting them.
Svelte is very nice for backend engineers to use for a frontend framework. It makes way more sense from a mental model, and it's incredibly lightweight, at least from what I've seen in other frameworks.
It's the exact same way I feel about Ruby. You definitely shouldn't be using it for everything, even most things, but the stuff it's good at it beats Python by a mile. And it's so much more pleasant to use.