We're Python fans too. Python is a great language and makes sense in many applications. At the same time it does not make sense for every developer in every project. We believe that many people will find NetHesive to be an easy and effective way of moving their applications onto their intranet or onto the web.
NetHesive is not necessarily part of the component-think that you reject so thoroughly. It is a way to communicate with a new or existing application over HTTP. We provide the functionality to *allow* developers to connect their projects to component frameworks, but it is not required in any sense.
Your disdain for components and web services is certainly justifiable for your work environment and your projects. NetHesive encourages flexibility by providing XML-over-HTTP functionality without locking the developer into any particular framework.
Perhaps you will better "get it" once we have our tools available online. It might be difficult for some people to understand how NetHesive simplifies development without seeing screenshots and other demonstrations.
As people interested in the way our product relates to the rest of the development world, we posted the/. article somewhat early in the release process. Your feedback has been extremely valuable; we look forward to introducing the release version of NetHesive in the coming months.
Most of your comments are accurate, but I do think you missed one point. The developer who uses the release version of NetHesive will not need to write the configuration file by hand. We have some nice tools coming online to do that for you. Does that make your life easier? =)
The question about licensing is also a very good one. We recognize that OSS is changing the world in many significant ways. Contrary to the assumptions in one of the posts here, the web site does not specifically state whether NetHesive will be open or closed source. We're still debating which way to go. Why don't you share your thoughts in our survey?
Click here to participate!
We're listening and want your input. Tell us how we can maintain an open source product, control quality and keep paying our developers! (And yes, we've read the many many posts about that exact topic on Slashdot. Consider our ongoing debate an indicator of how well those posts answered this question.)
Slashdot Mirror
We're Python fans too. Python is a great language and makes sense in many applications. At the same time it does not make sense for every developer in every project. We believe that many people will find NetHesive to be an easy and effective way of moving their applications onto their intranet or onto the web.
/. article somewhat early in the release process. Your feedback has been extremely valuable; we look forward to introducing the release version of NetHesive in the coming months.
NetHesive is not necessarily part of the component-think that you reject so thoroughly. It is a way to communicate with a new or existing application over HTTP. We provide the functionality to *allow* developers to connect their projects to component frameworks, but it is not required in any sense.
Your disdain for components and web services is certainly justifiable for your work environment and your projects. NetHesive encourages flexibility by providing XML-over-HTTP functionality without locking the developer into any particular framework.
Perhaps you will better "get it" once we have our tools available online. It might be difficult for some people to understand how NetHesive simplifies development without seeing screenshots and other demonstrations.
As people interested in the way our product relates to the rest of the development world, we posted the
We're not sure which distribution method we are going to use. We'd love your input: tell us what you think!
Most of your comments are accurate, but I do think you missed one point. The developer who uses the release version of NetHesive will not need to write the configuration file by hand. We have some nice tools coming online to do that for you. Does that make your life easier? =)
The question about licensing is also a very good one. We recognize that OSS is changing the world in many significant ways. Contrary to the assumptions in one of the posts here, the web site does not specifically state whether NetHesive will be open or closed source. We're still debating which way to go. Why don't you share your thoughts in our survey?
Click here to participate!
We're listening and want your input. Tell us how we can maintain an open source product, control quality and keep paying our developers! (And yes, we've read the many many posts about that exact topic on Slashdot. Consider our ongoing debate an indicator of how well those posts answered this question.)