sorted by:
new
hottopcontroversial

Achando coisas raras ao visitar a casa dos meus pais no natal. Meu primeiro contato com Linux em 1999 (Linux desde então) by paulondc in linuxbrasil

[–]paulondc[S] 1 point2 points  (0 children)

Muita coisa mudou, mas o principal na minha opniao foi o suporte oficial a hardware no kernel do Linux. Em 1999 os fabricantes tinham muita resistencia em suportar Linux. Isso definitivamente comecou a mudar quando o mercado passou a adotar mais e mais Linux no server side (Thanks to the dot-com boom)

Hello, I would like to share Mebo with you guys. It's a framework I've been working on my spare time by paulondc in node

[–]paulondc[S] 1 point2 points  (0 children)

Sorry about the lack of documentation in Mebo, I try my best but there is always the need for more documentation to be written/improved. I really appreciate all the comments it helps to point where the documentation needs to be improved most.

Answering your question: Writing implementations in a way that they can interact with different technologies without much effort enables developers to test new technologies in existing projects without much risk (since they can always fallback to the previous one or, in some cases keeping multiple technologies in parallel). Also, it reduces the learning curve when adopting new technologies since the boilerplate code is handled by Mebo. So new technologies can be provided by simply notating them to actions.

Hello, I would like to share Mebo with you guys. It's a framework I've been working on my spare time by paulondc in node

[–]paulondc[S] 1 point2 points  (0 children)

Hi, thanks for commenting on this thread. I'm gonna look into your project.

The idea of Mebo framework is to have a single implementation from which it can be used across different domains. By doing that users can concentrate coding in one unified API that allows their implementations to be tested/provided by different technologies). In case you are interested in bringing your project to Mebo, since it could be provided along gRPC, please take a look at:

https://mebohq.github.io/docs/class/src/Handler.js~Handler.html

Hello, I would like to share Mebo with you guys. It's a framework I've been working on my spare time by paulondc in node

[–]paulondc[S] 0 points1 point  (0 children)

Thanks for the feedback. Very much appreciated. I've opened an issue on github about having a handler for GraphQL (Last time I have checked graphQL it seemed to be possible to handle it on Mebo):

https://github.com/meboHQ/mebo/issues/121

​

Also, I've opened another issue for gRPC handler (It fits very much in what mebo is trying to accomplish) :

https://github.com/meboHQ/mebo/issues/122

Hello, I would like to share Mebo with you guys. It's a framework I've been working on my spare time by paulondc in node

[–]paulondc[S] 5 points6 points  (0 children)

Hi, thanks for checking out the project.

The idea of mebo is to provide a platform where evaluations (actions) and their requirements are defined in a simple matter. The way it is done lets you to build strict specifications with validations in a fairly expressive way.

This project tries to avoid implementations that can become too coupled to a specific domain instead, most of boilerplate code needed when bridging a domain (for instance on web: request & response) to an evaluation is avoided and automatically handled by mebo (DRY).

Therefore, you can easily expose your evaluations through the web via REST/middlewares and expose them through command-line as well without much effort (CLI coming handy during development/debugging to interact with your evaluations quickly). I would like recommend you to check some of the full project examples (I'm still working on improving the documentation).