You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been following big and resource for a while and I see some amazing aspects but I can't be quite sure I totally get the whole picture. I myself don't have a computer science degree so this doesn't mean as much as it should:
".. a next generation application zero-framework which solves the domain problem of building web applications"
What does this mean in practical terms? Can you show the users how big and resource would improve their application development? What is the 'domain problem' in node.js and how to we use big to solve it? What is the pattern you think is the right way to use big?
Maybe a small philosophy explanation, an annotated demo application or a comparison with the lesser alternatives would make adoption easier.
The text was updated successfully, but these errors were encountered:
Thanks. I did see them earlier, they are the simple basic practical use example. I was more thinking about a bit more substance and insight in what the specific magic about resource based development is. I'm pretty sure there is a vision behind this.
I've been following big and resource for a while and I see some amazing aspects but I can't be quite sure I totally get the whole picture. I myself don't have a computer science degree so this doesn't mean as much as it should:
What does this mean in practical terms? Can you show the users how big and resource would improve their application development? What is the 'domain problem' in node.js and how to we use big to solve it? What is the pattern you think is the right way to use big?
Maybe a small philosophy explanation, an annotated demo application or a comparison with the lesser alternatives would make adoption easier.
The text was updated successfully, but these errors were encountered: