Skip to main content

Nevow of the Future

I am not a core Nevow developer, but am only a developer who uses it. I do talk a lot with the developers, and try to keep up with what is going on there. So, I do know a bit about what is going on, and where things are supposed to go. I know that contexts (a type of object passed around that gives access to the current tag being rendered, remembers adapters between interfaces, and does other stuff that isn't so good) is supposed to go away, eventually, at some point, somehow. There is little talk of how, when, and that sort of solid thinking on the subject.

So, for the heck of it, I'll propose a plan of action, and this is it.

Step #1
Fork it, so that all the refactoring can be done and if anyone needs a backward compatible Nevow, it can still be around for them. There is already xmantissa and xquotient, so it wouldn't be a stretch to add xnevow. My other favorite is to just say that Athena is the new Nevow (see Step #2)

Step #2
Pull everything out of the fork that Athena doesn't need, so things can be focused. Refactor so that there is no difference between Page and LivePage, and you can just make any page become live. At this point, things can start to change and context can be factored out entirely. New flatteners would be needed, of course, but those should be more or less straight forward to adapt.

Step #3
Expand the templating system to be smart enough to handle both server- and client-side work. I recommend a nevow:insert directive that defines sub-templates to fill and insert the resulting node at some place, which could replace nevow:pattern and also carry over for used in live pages on the client. While we're at it, add in some good widgets to start with, like containers and tabs and such.

Step #4
Create a fake nevow module that can map existing API calls to the new stuff that would be in xnevow/athena. This would allow for easier transitions to the new system.

I might try and convince the usefulness of this to an employeer and see if some of my project time can be spent sprucing up athena in such a way, depending on just how much this would take to be really useful, or just usable. Then I could contribue something useful, and get some moneys.

Comments

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…