3 ms·
This looks intriguing. Thanks for sharing it. That said, I'm having trouble figuring out what it is. :-) I think the challenge may be that it's multiple things
by smarx 14y ago
This looks intriguing. Thanks for sharing it.
That said, I'm having trouble figuring out what it is. :-) I think the challenge may be that it's multiple things: a way to generate some code, a way to create databases, a way to run automated tests, a way to do model validation, a different "flavor" on top of ASP.NET MVC for things like parameter binding. I guess I'm wondering how those things relate, which could be used independently, etc.
I wonder if others are similarly struggling to understand what this is all about.
- amirrajan 14y agoI can see how that can be confusing. Rails is a development stack. It gives you exactly what's needed to get an app up and running quickly. It also provides the means to keep the app maintainable. Oak tries to provide that same experience to .Net devs. These components can be used independently, but the whole is definitely greater than the sum of its parts.