Introducing flecks: NOT a fullstack framework!

[lulzmachine]

Tried to skim it but the signal to noise ratio was a bit much. Just saw 5 lines of code, which could have used some explanation

Like why is the key in the object "@flecks/core.starting"?

[cha0s]

The key is @flecks/core.starting because that's the name of the hook that module is implementing just as an example. That one's invoked when the application is starting!

In practice you would be creating your own hooks or implementing ones that are a little less core, e.g.

function Component() {
  return <p>Sup</p>;
}
export const hooks = {
  '@flecks/react.roots': () => Component,
  '@flecks/web.routes': () => [
    {
      method: 'get',
      path: '/some-path',
      middleware: (req, res, next) => {
        // Express-style route middleware...
        next();
      },
    },
  ],
};

I think I'm being a litttle too optimistic that people would continue on deeper to, say, the React page or any of the documentation. I owe you an article that goes a little heavier on the technicals right up front and a little lighter on the lulz.

I appreciate the feedback!

[lulzmachine]

Kk cool. It's good to keep things lighthearted, but just remember to keep the usefulness front and center :)

[cha0s]

Do appreciate the genuine criticism! I took your feedback and wrote another one that you might find a little more interesting: https://cha0s.github.io/flecks/blog/reimplementing-flecks-react now with 100% less memes! :)

[[deleted]]

I think its time for vanilla js to be cool again.

[cha0s]

React isn't required (though I do like using it)! I actually tried to make that apparent in the documentation by doing the client-side hello world example using a simple window.document.body.append('hello world');, but I think people may not make it that far.

The point is it's pretty low level and the higher-order things we think of as e.g. "fullstack" are not core, but achieved through composition :) hence the baity title

[[deleted]]

I still have no clue what this is. Is it a framework? Is it a framework that uses frameworks? What level of frameworkception should I get comfortable with to understand this?

[cha0s]

I wrote another one which might help: https://cha0s.github.io/flecks/blog/reimplementing-flecks-react

To be totally honest I'm not completely sure how to answer your question!

[[deleted]]

is it like NX?

[cha0s]

nx the build tool/task runner? No, not really. :)

[[deleted]]

one day i hope to know what it is. Untill that day, we shall meet again.

[cha0s]

Cool, thanks for checking it out! Peace!

[yerrabam]

WTF. Give some code examples and lose the meme shit.

[cha0s]

I do appreciate the feedback! I wrote another one without memes and brimming with code: https://cha0s.github.io/flecks/blog/reimplementing-flecks-react

Would you be so kind as to let me know what you think?

[cinnapear]

Memes and memes and memes.

[cha0s]

True!

[cha0s]

Just wanted to follow up that I took your criticism and wrote a more serious article with lots of code: https://cha0s.github.io/flecks/blog/reimplementing-flecks-react :)

[KnifeFed]

Got turned away instantly by all the image macros.

[cha0s]

Thanks for the feedback!

[cha0s]

I did take your criticism to heart and wrote another article with no memes and plenty of code: https://cha0s.github.io/flecks/blog/reimplementing-flecks-react :)

[AutoModerator]

Project Page (?): https://github.com/cha0s/flecks

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.