Skip to content

Several questions and ideas #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
PaulMaly opened this issue Jan 31, 2017 · 3 comments
Closed

Several questions and ideas #272

PaulMaly opened this issue Jan 31, 2017 · 3 comments
Milestone

Comments

@PaulMaly
Copy link
Contributor

Hi, Rich!

First of all, let me thank you for this great idea. And also I know that you're founder and one of main maintainers of RactiveJS - best JS framework I ever used. I believe that Svelte has really great prospects. Thank you for that.

For me Svelte could be great because of several reasons:

I already use RactiveJS the last 3 years and obviously Svelte has very similar API
I'm already using Webpack to build my code and it's great if this process will transform my code to vanilla JS
But right now Svelte is a little bit dampish and it's justified. Main questions for me to make a decision to switch from Ractive to Svelte would be:

integration with complex data structures (not POJO objects, like classes etc.). In Ractive we've Adaptors and it's great tool to do something like this:
ractive.set('post', fetch('/posts')); // using Promise adaptor

integration with DOM specific libraries (like Jquery etc.). In Ractive we've Decorators and I never get a problem with it and even more - it helps me encapsulate my browser specific code in my isomorphic (universal) apps.
Whether you plan to include similar features in Svelte ?

And my main idea - Ractive API is awesome, just implement it. Thanks!

@Rich-Harris
Copy link
Member

Thanks Paul!

integration with complex data structures (not POJO objects, like classes etc.)

There was some tangentially related discussion around this on #11. Because of how Svelte works, and because I learned through Ractive how tricky adaptors can get, I'm hesitant to add first-class support for them (i.e. allowing any arbitrary keypath to be occupied by a promise or a Backbone model or whatever else the user might have) — it ends up adding overhead that everyone has to pay.

So something more like what's outlined in #11 might be more realistic. I'd be interested in collecting examples of how people have used adaptors so we can come up with a decent API (or perhaps rather a decent set of conventions, since it probably wouldn't be part of Svelte itself).

integration with DOM specific libraries (like Jquery etc.). In Ractive we've Decorators

Yeah, I think we should do decorators. (At first I wasn't sure, because I thought you can use components for everything you'd use decorators for, but towards the end of #61 I became convinced otherwise)

@andymans
Copy link

andymans commented Feb 3, 2017

+1 for decorators - one good use case being the wiring up of something like Mobx. Inferno-mobx has some nice examples of what might be possible...

@Rich-Harris Rich-Harris added this to the N/A milestone Mar 1, 2017
@Rich-Harris
Copy link
Member

I'll close this issue in favour of #469 — thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants