The Value of TypeScript × Vue vs Svelte × Leetcode
Ғылым және технология
In this potluck episode of Syntax, Scott and CJ serve up a variety of community questions, from the nuances of beginner vs. advanced TypeScript to the pros and cons of SvelteKit. They also discuss falling out of love with React, shipping private packages via NPM, and the eternal struggle of always starting but never finishing projects.
Show Notes
00:00 Welcome to Syntax!
01:06 Brought to you by Sentry.io.
01:49 Today's format.
02:23 Beginner vs advanced TypeScript.
09:23 Does Sveltekit replace Svelte with Astro?
13:09 Handling multiple languages.
19:52 Falling out of love with React.
25:53 Shipping private packages via NPM.
29:00 How do you feel about importing packages from a URL?
30:36 VueJS vs Svelte.
36:15 Leetcode type interview questions.
41:58 Learning a new language for personal growth.
46:21 Always starting, never finishing.
50:23 Code quality vs tackling tickets.
55:36 Sick Picks + Shameless Plugs.
All links available at syntax.fm/781
------------------------------------------------------------------------------
Hit us up on Socials!
Scott: / stolinski
Wes: / wesbos
Randy: / @randyrektor
Syntax: / syntaxfm
www.syntax.fm
Brought to you by Sentry.io
#webdevelopment #webdeveloper #javascript
Пікірлер: 30
Such a cohesive team, CJ just fits naturally, And i share scotts impluse to always reach for Svelte
Love seeing CJ on the pod! Congrats on the family extension Wes.
@WesBos
13 күн бұрын
thank you! And thank you CJ for doing such an awesome job :)
I vuejs ecosystem is really awesome. Vite unjs nitro etc. all contributing to the whole js ecosystem not just vue.
@friendly__drone9352
4 күн бұрын
Evan You, Ant Fu and the team carrying the Vue side of the web. It's a pleasure to work with.
Alright Scott, you've sold me on Svelte. I'm gonna give it a try. I totally agree with you about having Stockholm syndrome using React.
Vue is amazing, especially with Nuxt
Why is no one asking for CJs moustache care, drop it
+1 more CJ content (plus the sick stash)
When I finally got the chance to get into "reasonably modern" web dev, I skipped over React precisely because it looked like there were a lot of things that could trip me up and I needed to get up to speed fast. Learned Vue, Svelte, and I'm now thinking of picking up Qwik, Solid, and HTMX. I might get slightly overly excited by new concepts, :-) And yes, React is starting to look more interesting as well.
Congrats Wes! CJ great job! You filled those big shoes well! Now ... how can we make it so when I watch this video here - it marks the episode as played in my pod catcher of choice? Great content as always y'all!
@syntaxfm
13 күн бұрын
I wish that were possible. Podcasts are plain ole rss feeds so not much we can do there.
Vue already grow to have a place in the job market, not as many jobs as react, but there's more. Also Vue/Nuxt is one of the options Indie Hackers use to create their apps. It's curious but must Nuxt Devs don't take full advantage of Nuxt, they use it for the frontend and they have a Laravel, Rails or especially a Node Backend.
when the jsdocs episode?
CJ is a 💎
The only reason I learned react was due to the Vue 3 days. I loved Nuxtjs but the migration took too long to stabilise in that time I picked up Next.js
Every time one of my coworkers puts an "any" in a PR, I go look and take out the any and find out that they put in the "any" to deliberately ignore an actual bug that typescript correctly identified. I've never in my life "fought with the types" in typescript, I feel like if you're doing that you have actual bugs and what you're fighting with is the bugs you're writing, not typescript. You probably just have gotten used to and prefer to write the bugs and then print-debug them rather than not write the bugs in the first place.
@syntaxfm
Күн бұрын
There are some scenarios where the dynamic nature of JavaScript does not fit 1:1 with how types can be expressed in TypeScript. You can of course reach a point where the TypeScript compiler no longer finds an issue with the code but sometimes we know the specific use case better than the TypeScript compiler and can ignore it. A few scenarios to consider: parsing and using inconsistent API responses, converting legacy JavaScript code bases with heavy dynamic usage of objects, time-constrained / budget constrained prototypes and technical spikes etc. Anyone that has used TypeScript for long enough and in enough scenarios will come across these issues.
I think the ultimate react will be useSvelte() Ya ya its a bad joke, i don't hate react i just like svelte more hahaj
i think cjs likes vue nuxt3 is good
@syntaxfm
12 күн бұрын
I think CJ’s nickname should just be .cjs from now on
Don't waste talent, bring CJ more often!
@syntaxfm
13 күн бұрын
He’s recorded 6 this month while Wes is on leave
Always has been
WHERE IS WES!!!
@syntaxfm
13 күн бұрын
Wes will be out for a few episodes because he had a baby. kzread.info/dash/bejne/iJ5tvJZ9o9KeqZc.html
TS is useful but has turned into a religion.
44:00 Was thinking to myself... Please say C# Please say C# Please say C# 🤞😝🤞 And then it happened and... I just... no ... words... 🥹