>Nirvana is CoffeeScript web development backed by erlang and Riak.
OH COME ON, I would almost bet money @nirvanacore follows the great traditions set by @rolfscale and @hipsterhacker.
That said!, good luck :D.
>The idea then becomes, instead of executing the code for every component in every request, if the component has no context specific requirements (e.g.: it is the same for every user, it's a static element, or it's dynamic, and but doesn't need to be generated every time) .. then it can be flagged as cacheable.
How are you going to win over everyone else's caching solution? Why are you going to be easier than
I'd love to find a place on the internet where I can talk about my project seriously with people. I'm the only engineer in our small startup, and building this platform to decrease the cost of development for myself going forward. I'm open sourcing it because there isn't a solution like this out here (or I'd just use that instead.) My focus is actually on zero-operations-dudes-on-payroll scalability up to medium sized services, not "it's gonna be huge man" scalability. I'm not using MongoDB because its "wicked fast!!!", I'm using Riak because "no ops guys needed, just add nodes."
Seriously, anyone know such a place? I guess I'll have one when I make the first release, since I'll make a mailing list and issue tracker, etc. But right now, before the first release, when I'm thinking about serious architectural issues, that's the time I could use someone off of whom I could bounce ideas and get feedback, positive or negative. I mean, constructive feedback.
That's why I made the comment on this post, because it's reasonably relevant to what I'm doing.
In answer to your question, I have no interest in winning over anyone else's caching solution. I'm not building a web cache, I'm building a web development platform. This makes web development a whole lot easier for the kind of development I do. I expect it will be useful for others, but even if it isn't, the time invested in it is almost nearly recouped developing our MVP.
Oh stop whining. My jest at the top of my post obscured my seriousness at the bottom.
My point largely was, "I can't tell if you're being satirical or not". You're meshing three extremely new and very fancy technology stacks together and inventing a whole new framework to go with it.
So… maybe you do want to figure out a good stock way to counter my skepticism. Waving your hands and saying "it's a web development platform!" feels unsatisfying :).
OH COME ON, I would almost bet money @nirvanacore follows the great traditions set by @rolfscale and @hipsterhacker.
That said!, good luck :D.
>The idea then becomes, instead of executing the code for every component in every request, if the component has no context specific requirements (e.g.: it is the same for every user, it's a static element, or it's dynamic, and but doesn't need to be generated every time) .. then it can be flagged as cacheable.
How are you going to win over everyone else's caching solution? Why are you going to be easier than