Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Svelte 3: Rethinking Reactivity

svelte.dev

Post reply on HN
Print view View original

111–120 of 186 posts

Re: Svelte 3: Rethinking Reactivity

#111

Post by gedy »

oogway8020 wrote: post #107
gedy wrote: post #22

Since you are reading here Rich Harris; while I really admire your solutions, one weak point with Svelte seems to be a clear unit testing solution, or at least docs last I looked. I also noticed this with Ractive, and feel it weakens these in the eyes of many businesses considering these tools. I know it's a solved/solvable problem but it feels like better docs and samples in quick start guides would help.

I admire Rich Harris' work as well. 4 years ago I was picking my first SPA framework. Narrowed it down to Ractive and Vue. Picked ractive, it had a beautiful documentation and tutorial. Still have an app in production based on ractive. But author abandoned it. Then vue 2 took off. I didn't have a choice but switch. Recently I started playing with Svelte/Sapper again. I like it a bit better than vue for some reason an…

> But author abandoned it.

To be clear though, Ractive is still under development by other maintainers: https://github.com/RactiveJS/Ractive.

> he should narrow his focus

Not to speak for him, but I think Rich is an "idea guy" and we'd all miss out if he were throttled to just one thing :-)

Re: Svelte 3: Rethinking Reactivity

#112

Post by nickdandakis »

machiaweliczny wrote: post #42

Nice handling of reactivity - I think this should already be in language as well. I'm not sure I like this single components approach and embedding JS in HTML. The problem with this is that it's too frameworkish. The big benefit of JSX/React rendering is that it's composable and declarative (as it's just functions), but it's also simple to get - render just returns wanted structure, given the state and you can use si…

Svelte exposes a [preprocess function](https://svelte.dev/docs#svelte_preprocess) that (in theory?) you could use to preprocess markup JSX-style.

Re: Svelte 3: Rethinking Reactivity

#113

Post by bjz_ »

tux3 wrote: post #5

I'm really impressed that the release announcement starts by explaining what Svelte is. It's a little thing, but it's appreciated.

Yeah, I first saw this approach taken by the Rust announcements in the early days. It's a great demonstration of empathy to the reader!

Re: Svelte 3: Rethinking Reactivity

#115

Post by keerthiko »

tux3 wrote: post #5

I'm really impressed that the release announcement starts by explaining what Svelte is. It's a little thing, but it's appreciated.

It's really not a little thing. The number of blog posts that talk about why version N+1 of X is great, assuming I know what X or version N did is stupid, and I am immediately churned out.

Re: Svelte 3: Rethinking Reactivity

#116

Post by ChrisCinelli »

I tried Svelte/Sapper a few weeks ago. It is definitely not the new framework of the month that come and go.

I love it. I cannot believe how fast the app load on both first and second time visits. 100% in lighthouse.

I think Svelte is the way to go! I hope the community will accelerate and eventually catch up with React and Vue!

Re: Svelte 3: Rethinking Reactivity

#117

Post by moosingin3space »

arxpoetica wrote: post #94
moosingin3space wrote: post #92

Very happy for this. I wrote a Firefox extension with Svelte v1, and will take this release of Svelte v3 as an opportunity to refactor my extension. Thank you, contributors!

Would be interested in learning the size difference. What does your extension do?

This is my extension: https://addons.mozilla.org/en-US/firefox/addon/workspaces-fo...

It's a Sublime Text-inspired navigation tool for Firefox. I use it to jump around between tabs on different workspaces or different monitors. (Yes, I know the default keybinding is bad. I'm going to change that in the post-refactor version.)

My plans are to refactor it for the new Svelte, then improve the fuzzy search, and possibly go cross-browser.

Re: Svelte 3: Rethinking Reactivity

#118

Post by [deleted] »

seandougall wrote: post #104
phailhaus wrote: post #52

Earlier quoted context omitted.

Eslint already warns you about issues like this, and is framework-agnostic. Does Svelte just use eslint under the hood? Otherwise you risk fracturing the ecosystem with framework-specific a11y requirements.

Accessibility requirements for the web have a centralized source in the WCAG. As long as linters/checkers conform to that, it doesn’t seem like it should be a source of fragmentation.

[deleted]

Re: Svelte 3: Rethinking Reactivity

#119

Post by adrianhel »

keerthiko wrote: post #115
tux3 wrote: post #5

I'm really impressed that the release announcement starts by explaining what Svelte is. It's a little thing, but it's appreciated.

It's really not a little thing. The number of blog posts that talk about why version N+1 of X is great, assuming I know what X or version N did is stupid, and I am immediately churned out.

This is basically v1 though, so it's a bit different.

Re: Svelte 3: Rethinking Reactivity

#120

Post by rajangdavis »

What I think is really interesting is that the Virtual DOM was touted as the better abstraction when React came out (in comparison to Angular 1's dirty checking).

I think Svelte is doing a lot of things right (simple code, computing CSS animations, accessibility built in, focusing on a compiler versus a full on framework) and I can't wait until Sapper is updated to dig in.

Post reply on HN