mintydev.bsky.social
I make websites, learn languages, solve Rubik's Cubes, and do other cool things. Creator of https://cubingcontests.com
70 posts
32 followers
19 following
Regular Contributor
Active Commenter
comment in response to
post
Nobody says there's no point in putting a lock on your door, because smo can still break a window and get in 😑
2/2
comment in response to
post
I just don't use algorithmic feeds. I feel like they just waste time, and usually just end up developing an unhealthy habit.
comment in response to
post
I did try #Fedora and #Debian after giving up on #Arch too, but I really missed Pacman and the Arch repos + AUR, so I went back to Arco. For my next install, I'll just set up pure Arch with my post-install script.
2/2
comment in response to
post
That being said, not planning enough can be even worse, cause you might have to do a major migration much sooner, so it's about finding the balance between planning and just getting on with it.
comment in response to
post
and you'll *have* to migrate a big chunk of your #code. So it's best to just pick a tech stack and start working on your project. 2/3
comment in response to
post
The thing I hate seeing the most is people avoiding new technologies, because their LLM can't handle writing sensible code with them. Adopting one breakthrough technology shouldn't mean dismissing others.
2/2
comment in response to
post
That sounds kinda lit, ngl!
comment in response to
post
Add more if needed meaning migrate to Next JS when you realize you want better SEO?
comment in response to
post
So let me announce our BRAND NEW BULLSHIT #AI SERVICE: Deep Senior Developizer ✨ (in partnership with OpenAI). Supercharge your skills by fastforwarding your training with our AI-powered headset that fills your frontal lobe with hundreds of years of coding experience. Only $699 a month!
comment in response to
post
... but on the other hand there's no shortcut to becoming a good one. You just have to experience all the frustrating issues and learn problem solving, and that can only happen with thousands of hours of experience. 🧵
comment in response to
post
Hmm, this is interesting. But then why not provide a way for all of the existing ActivityPub platforms to migrate to ATProtocol and interop with it during the transition of the ecosystem? Or is that in the works?
comment in response to
post
Not on JSR :)
comment in response to
post
Yeah, it finally clicked for me recently, and I actually quite like the RSC data fetching solution
comment in response to
post
But hey, if I'm honest, Svelte would probably be my top choice if I had to go for a non-JSX option.
comment in response to
post
I find it hard to agree with that last part, as I specifically only want to use JSX frameworks now, even after having used various templating options: JSX, Vue, CSHTML, and RoR's .erb syntax. Also, I don't get the need for strict enforcement of single file components.
comment in response to
post
You can even have them integrated into VS Code with the Continue extension, which now even has agent mode (not sponsored, just a happy user). Let's not stay stuck in the past and actually embrace new technologies and use them for good 😉
2/2
comment in response to
post
Fair enough. I've tried both approaches, but I really feel like JSX "won" for good reason. I think it's a good standard, and it's the only one used by multiple frameworks afaik.
comment in response to
post
Yeah, but in my mind those JSX features are just reusing existing JS syntax, which is why I think JSX is a relatively minimal abstraction.
comment in response to
post
It's things like Svelte's # if, :else, # each, # await, :then, :catch, etc. that I was referring to. To me that special syntax feels unnecessary. Although I gotta admit, that await, then, catch feature is quite cool; I just found out about it.
comment in response to
post
Wouldn't this have to be wrapped in <template> in Vue? In any case, to me this feels like a non sequitur.
comment in response to
post
I'm not sure what you mean. Solid allows the use of JS reserved keywords, so why wouldn't regular HTML copied into a Solid JSX template just work?
comment in response to
post
But I'll accept the React own, haha. Also, Vue Vapor and Svelte 5 don't have the performance drawbacks of React from what I've heard. But I'd still choose Solid 😎
comment in response to
post
You can in Solid
comment in response to
post
I'd only use #React or, preferably, #SolidJS, which basically fixed React. And I say this as someone who was a Vue dev for the first two years of my #webdev journey.