How is this[1] diagram built? I have seen this font in quite a few places. [1] https://claudioholanda.ch/assets/blog/en/0003/1.svg
excalidraw
Thoughts on Svelte(Kit), one year and 3B requests later
21–30 of 222 posts
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#22> by wrapping a vanilla lib to a component or an action, you’ve essentially created basic Svelte version of that lib This is the key to making framework churn go away. The DX of using vanilla JavaScript is getting better every day. And is a much better experience than it was a decade ago. > Islands architecture and partial hydration can help you render static HTML with just a small portion of JavaScript for those com…
This is all fun and games until you work on a platform that requires dynamically loaded modules, error boundaries and suspense (or another form of components loading their own data) and then the no-nonsense approach falls flat.
It is easy to put your nose up towards bloated frameworks when you’re doing small (static) stuff but as soon as you need the bloat you’re just reinventing a wobbly wheel without one.
There’s always an air of disdain against front end frameworks on HN but people often project their own not-needing-a-framework on the tool itself.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#23How is this[1] diagram built? I have seen this font in quite a few places. [1] https://claudioholanda.ch/assets/blog/en/0003/1.svg
draw.io if I'm not mistaken !
Actually, it looks like Excalidraw[1] to me. The shading and line style match very closely.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#24I've moved my little hobby website to SvelteKit[1] from react and I am not regretting it.. yet. The only main frustrations I have are: - Library support is pretty lousy. You need to fudge things around to get working. I.e, with leaflet and others I have vendored in the libs and redone them. - Incremental static refresh with svelte kit is not really there. I'd like a web hook or api callback that allows me to refresh…
Library support is pretty lousy.
Next 13's app directory and React Server Components is killing library support in React, so that's not such a big problem.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#25I gave up the Javscript rat chase, for now I am sticking with React.js.
Svelte has been around for years, and in my opinion it won’t really gain that much traction anymore. (It’s just an opinion, let’s not be religious)
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#26How to build a custom CMS and new frontend codebase in 2 months that can handle 3 billion hits per year in a corporate setting.
Would be more interested in how your work flow was managed.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#27I've moved my little hobby website to SvelteKit[1] from react and I am not regretting it.. yet. The only main frustrations I have are: - Library support is pretty lousy. You need to fudge things around to get working. I.e, with leaflet and others I have vendored in the libs and redone them. - Incremental static refresh with svelte kit is not really there. I'd like a web hook or api callback that allows me to refresh…
Library support is pretty lousy. Next 13's app directory and React Server Components is killing library support in React, so that's not such a big problem.
What does that mean?
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#28You need very strong argument not to take the most popular technologies these days. I don’t hear any arguments against react here strong enough to justify not choosing VueJS or React. It’s not in the interests of your client.
He said that he couldn't have met the deadline without Svelte.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#29I've moved my little hobby website to SvelteKit[1] from react and I am not regretting it.. yet. The only main frustrations I have are: - Library support is pretty lousy. You need to fudge things around to get working. I.e, with leaflet and others I have vendored in the libs and redone them. - Incremental static refresh with svelte kit is not really there. I'd like a web hook or api callback that allows me to refresh…
Library support is pretty lousy. Next 13's app directory and React Server Components is killing library support in React, so that's not such a big problem.
I don’t know much about the former, but it’s not clear why React server components are going to kill library support.