>
> The notion that new code does not interfere with an existing code
> base is a false premise. If you don't understand the harm involved in
> increasing the size of a code base, you're not qualified to comment.
>
Alright well if you read the rest of the thread you should have realized
Will suggested putting this into StripesStuff, not into the core. I'm not
one to simple add more code to anything just for the sake of adding code.
I'm much happier removing code before I add some and you have no idea what
qualifications I may or may not have to make comments. Please keep personal
references/attacks out of this.
>
> But, there's a community problem too.
>
> Cocoon was like this. They keep rolling in every shinny new object
> that was flogged by the Java press. Then they had to start throwing
> around the word "deprecated". I would ask about such and such a
> feature on the listserv and they would be told that I'm not supposed
> to use that anymore, it has been deprecated. Then I'd return the page
> that had the breathless description of how powerful the feature and
> look for the word deprecated, but wouldn't be able to find it.
> Basically, the community had a new shinny object and didn't want to
> be bothered with last year's shinny object.
>
Again, this is a new 'shiny' object as you put it, but outside of the core.
It's not in the main codebase, shouldn't touch the main code base and
doesn't belong there, how this harmful again? Please explain.
>
> To date, my experience with Stripes is that the documentation talks
> about the things that I can use and want to use and do use. Stripes
> itself is free of flights of fancy. I'm using Stripes and Stripersist
> and it's a complete framework.
I agree, we use stripes here mostly for what it DOESN'T do, not because it
has the most shiny objects in it. It does what it does well and thats it.
You think I want to turn Stripes into the next JSF or whatever? No thanks.
>
>
> My only disappointment is that I'd like to have a lot more control
> over the URLs. That's a more important component of Basic/Core/Pure
HTTP than the strange stumpy tail or 6th finger of the HTTP verb.
Well you should have that already with the more friendly URL stuff in 1.5,
no need to concern yourself with that stumpy 6th finger if you don't want.
>
>
> --
> Alan Gutierrez | [EMAIL PROTECTED] | http://blogometer.com/ | 504
> 717 1428
> Think New Orleans | http://thinknola.com/
>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Stripes-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
