First off I downloaded SurgeLab to check out some of the code and the development environment. The curl code itself is extremely verbose, (aka takes lots of typing to create simple things) and is not very intuitive.
Second, I think the whole idea of an "everything including the bathroom sink" technology like this will make the development of even semi-large applications difficult. I much prefer to be able to seperate data from logic and to have a language for each that is taylored to its specific purpose. The whole idea of trying to mix display elements with the programming logic that controls the display is crazy. Anybody that has worked on even a decent sized web-app knows this.
Third, the licensing policy for curl is obscene. Can you imagine a start-up company having to fork over $1000/month (minimum) at the very begining just to pay for usage? Curl is the anthesis of the open source movement.
I saw a couple people remark that it would great to have a new web technology that is not controlled by one of computer giants. That's crap! Everybody wants to stand behind some David that is waging war against a giant, but I have no reason to believe that the people behind Curl aren't trying to make a giant of themselves.
I'd rather keep my text & images in resource & XML files, the display formatting information in stylesheets and XSL files, and the code all by itself.
Major difference between an opt-in list and slapping a GPL on your code is that you don't have to go through some other authority to GPL your code. Can you imagine how fun open source would be if there was some central server that had to verify the open-ness of your code everytime somebody wanted to download it?
Slashdot Mirror
I have several major reservations about Curl:
First off I downloaded SurgeLab to check out some of the code and the development environment. The curl code itself is extremely verbose, (aka takes lots of typing to create simple things) and is not very intuitive.
Second, I think the whole idea of an "everything including the bathroom sink" technology like this will make the development of even semi-large applications difficult. I much prefer to be able to seperate data from logic and to have a language for each that is taylored to its specific purpose. The whole idea of trying to mix display elements with the programming logic that controls the display is crazy. Anybody that has worked on even a decent sized web-app knows this.
Third, the licensing policy for curl is obscene. Can you imagine a start-up company having to fork over $1000/month (minimum) at the very begining just to pay for usage? Curl is the anthesis of the open source movement.
I saw a couple people remark that it would great to have a new web technology that is not controlled by one of computer giants. That's crap! Everybody wants to stand behind some David that is waging war against a giant, but I have no reason to believe that the people behind Curl aren't trying to make a giant of themselves.
I'd rather keep my text & images in resource & XML files, the display formatting information in stylesheets and XSL files, and the code all by itself.
Major difference between an opt-in list and slapping a GPL on your code is that you don't have to go through some other authority to GPL your code. Can you imagine how fun open source would be if there was some central server that had to verify the open-ness of your code everytime somebody wanted to download it?