On Wednesday 28 April 2004 3:38 pm, Tom Trenka wrote:
That's a tough one.
I spent far too much time trying to come up with a suitable name
for f(m); in the end I resorted to one of my native NY
collilquisms: f*cking magic. Of course, you can't release something
that way, so it became f(m) :)
Heh. That's really funny. I was wondering if that's what f(m) stood
for, or if it was some functional programming in-joke.
I would suggest that we decide what it is we're really doing first,
and keep ideas for a name in the back of our heads. If someone
thinks they've got something great, post it.
Well, to some extent it's helpful to just get _a_ name so you don't
have to got "oh yeah, that thing that Alex and Tom and a bunch of
other people are doing...."
I'd also suggest that we make sure we split it up into a group of
several technologies that are grouped together conceptually. In
the same way that J2EE and the .NET Framework are really monikers
for a related set of APIs. Because I can definitely see there being
several pieces to whatever it is we are doing.
I don't think we should split pre-maturely. As I see it (and after
having Leonard help me filter my thinking a bit), there are 3
different groups of people that are gong to be on this list (and
already should be represented):
1.) people who will hack on the techonog(y||ies).
2.) people who will use the tech
3.) those who can get behind the tech without doing either (usually
decision makers and developers on the sidelines)
Sub-dividing group 1, I think that there will be people that
contribute more heavily to the DHTML/JS core side of thigns, people
who spend more time on widgets, and people that work more on the
server-side aspects. All of those I expect can and SHOULD overlap
very heavily since I don't think there's anyone on this list today
who can't wear all of those hats. Artificial project sub-division
helps when it comes to the marketing and description side of things,
but I don't know that we should plan to split things up until such
time as it becomes an obvious necessity that things should split off.
firstname.lastname@example.org BD10 7AFC 87F6 63F9 1691 83FA 9884 3A15 AFC9 61B7
alex@netWindows.org F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46