Fusion.js: A Plugin-Based Universal Web Framework
1–10 of 79 posts
Re: Fusion.js: A Plugin-Based Universal Web Framework
#2I've been working with the Fusion.js team for the last year now, and I think it's evolved into a really interesting and modern web framework. Internally we've started rolling this framework to a few dozen web applications, and soon we will have hundreds of web apps running it. I think it's a great choice to use as a base for high-performance and complex web applications.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#3Looks like a competitor to next.js, and from their docs built on koa.
It’s nice to see more libs in this space, but it seems a little over complicated to me with the “plugin” style arch.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#4"Oh? What's this? ... 'uber.com'? Pass."
It may not be fair but that's literal though stream right there.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#5Can someone write a sales pitch / direct comparison to next.js please?
Does it only support react?
Re: Fusion.js: A Plugin-Based Universal Web Framework
#6Seems to use Flow instead of Typescript. I wish MS and FB just merged their projects already. Really unnecessary friction when their syntax is 90% the same AFAICT.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#7Seems to use Flow instead of Typescript. I wish MS and FB just merged their projects already. Really unnecessary friction when their syntax is 90% the same AFAICT.
They aren’t the same though. Flow’s type system is nominal, typescript’s is structural, which is a huge language difference.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#8Seems to use Flow instead of Typescript. I wish MS and FB just merged their projects already. Really unnecessary friction when their syntax is 90% the same AFAICT.
Yes. I wonder what's the future of Flow (even if it's still used and maintained). As I posted in another topic about TS:
> It's kind of crazy that Facebook has let TypeScript takes so much market share. I've been using Flow for so long now. The techno is good, the integration with the code editors is good too, but Flow has a lot of small-but-really-annoying bugs (2235 issues on GitHub right now), the type definitions for third-party libs are meh (you often have to update/fix the definitions by yourself), the team seems extraordinarily unstaffed for such an important project, they don't share the roadmap at all, the priorities are clearly internal first (like improving the performances instead of fixing the bugs) and they don't seem to do much marketing or communication about it.
> I'd love to still recommend Flow, and as I said the techno is good and does the job, and they continue to release new versions, but I just don't see what benefits you would get by choosing Flow over TS at this point. Flow and TS do exactly the same job, with almost the same syntax (with different ways to transform it in JS tho), but TS has a bigger community and MS seems to put more efforts/resources into it. This has been true for 1 or 2 years now, so…
Re: Fusion.js: A Plugin-Based Universal Web Framework
#9Looks like a competitor to next.js, and from their docs built on koa. It’s nice to see more libs in this space, but it seems a little over complicated to me with the “plugin” style arch.
It looks very similar to the Vue plugin system, which is one of the nicest parts about using Vue.
Re: Fusion.js: A Plugin-Based Universal Web Framework
#10Looks like a competitor to next.js, and from their docs built on koa. It’s nice to see more libs in this space, but it seems a little over complicated to me with the “plugin” style arch.
Correct about Fusion.js being based on koa. We find that this fits really nicely within the plugin system. The diagram is complex, but we inject the render phase into the middleware stack. Everything before `await next()` is pre-render, and everything after `await next()` is post-render. It makes it very easy to reason about the lifecycle of a plugin, as everything is in one place.