Vue RFC: Expose logic-related component options via function-based APIs instead • Hacker News Board

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#251

Post by ergo14 » Tue, Jun 25, 2019, 8:41 AM UTC

arxpoetica wrote: post #250

ergo14 wrote: post #236

Earlier quoted context omitted.

Yes but svelte is on v3 - I'm asking about that.

That first link was to the v3 docs. Here it is again for your convenience: https://svelte.dev/docs#svelte_compile

There is also, Custom element API section that is "TODO". Yes I saw those options the first time, but woulnd't you say the documentation is limited ;) if such is the case.

So far I see 2 sentences related to the subject, compare that to V2 docs.

I will try to see how svelte performs for this, but so far Vue wc-wrapper seems to be the most promising option out of "non-wc first" ecosystems.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#252

Post by mvgmvg » Tue, Jun 25, 2019, 1:32 PM UTC

simonw wrote: post #71

Classes really seem to have gone out of fashion in JavaScript land these days.

JS land and Frontend in general changes fashion every 6 months (tops)

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#253

Post by mvgmvg » Tue, Jun 25, 2019, 1:33 PM UTC

tannhaeuser wrote: post #100

Romanulus wrote: post #64

I'm glad I've held off for this long... almost time to jump in!

You're making the assumption JavaScript frameworks are iterating towards perfection when in reality it's just generational churn. We're still talking about mostly trivial business form apps. Yet they need to be thrown away after 3-5 years because nobody can maintain them, and nobody wants to. Much better to lure young developers with "exciting" (immature) tech.

That.