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
Mandarine has been a successful framework in the Deno community. It has had a very positive response towards all the features that make Mandarine great. The Deno community and Deno itself have been an important part of this process of making Mandarine a solution for enterprise-sized problems.
To The Future... and Beyond.
Recently, our team has made multiple tests on how Mandarine can be used. Initially, Mandarine was thought to be a server-side framework like Spring Boot. Although, the extensive API of Deno & Javascript (through typescript) as well as the excellent flexibility Mandarine has in its core have made us shaped our vision towards what Mandarine can get to be.
The tests that have been ran by our different collaborators have shown that Mandarine can be used for CLI applications thus building much better, readable, and extensive CLI systems. With that said, we have demonstrated Mandarine can be used for:
Server Side Applications
CLI's
With this investigation, we can't stop wondering where we are heading towards.
The options
Throughout the last 5 months we have been working on Mandarine, we have made Mandarine perhaps the most stable server-side framework in Deno, but now, we want to separate ourselves from server-side and go beyond. For that, we have thought Mandarine can be used in:
Server-side applications
CLI Applications
Desktop Applications that run on Deno
Any Deno application by exposing Mandarine's internal APIs
While there is not agreement where we are heading towards as we continue to investigate how we want to make Mandarine multi-platform in terms of development needs, we would love to know your opinion. Do you have any thought? Join the discussion below.
The text was updated successfully, but these errors were encountered:
Intro
Mandarine has been a successful framework in the Deno community. It has had a very positive response towards all the features that make Mandarine great. The Deno community and Deno itself have been an important part of this process of making Mandarine a solution for enterprise-sized problems.
To The Future... and Beyond.
Recently, our team has made multiple tests on how Mandarine can be used. Initially, Mandarine was thought to be a server-side framework like Spring Boot. Although, the extensive API of Deno & Javascript (through typescript) as well as the excellent flexibility Mandarine has in its core have made us shaped our vision towards what Mandarine can get to be.
The tests that have been ran by our different collaborators have shown that Mandarine can be used for CLI applications thus building much better, readable, and extensive CLI systems. With that said, we have demonstrated Mandarine can be used for:
With this investigation, we can't stop wondering where we are heading towards.
The options
Throughout the last 5 months we have been working on Mandarine, we have made Mandarine perhaps the most stable server-side framework in Deno, but now, we want to separate ourselves from
server-side
and go beyond. For that, we have thought Mandarine can be used in:While there is not agreement where we are heading towards as we continue to investigate how we want to make Mandarine multi-platform in terms of development needs, we would love to know your opinion. Do you have any thought? Join the discussion below.
The text was updated successfully, but these errors were encountered: