No TCP/IP stack in the palm? That's funny. I guess all of the BSD sockets-based networking stuff I have written for the Palm is running on magic. And every byte of it was written on a linux box. The only money i have spent on palm development tools was to buy the o'reilly title on palm programming. Try finding a BSD-style interface to a Psion! Furthermore, go to http://www.palm.com/devzone. As of mid-February, they are officially supporting the GCC-based toolchain.
Mobile phone vendors have a vested interest in keeping their developmnet tool chain closed. why would you buy a new cell phone if you could go to freshmeat and get the features you want, or even roll your own?
Not for me. I'll not look to interbase for embedding in my web apps. i might use it for a transactional back end. But no DBMS runs faster alongside apache than mySQL (AFAIK). I can't imagine a better prototyping platform than PHP/mySQL.
Suppose I don't like the java servlet API. Maybe I think it is too complicated. So, i throw a few pieces out. Then I produce a servlet engine based on this new 'simplified' API. 95% of all current servlets are still compatible.
If I understand Bill Joy's comments, he says this is ok. I can 'fork' the servlet API by reverse-engineering it and modifying it.
But this flies in the face of what I understand to be Sun's licensing WRT java standard extensions, of which the servlet API is a member. So, what's the deal?
Drop facades wrt the OSS community ("Let's stand on each other's shoulders and not on each other's toes". "A JVM for linux is hard to do because the linux distributions are SOOOO disparate".)
This is just vapor. Guess what? IBM, Inprise, and Transvirtual have DELIVERED java on linux. OK, Inprise is really just a JIT for Blackdown. But it's something, and it's commercial. Sun is blowing smoke in the hopes of taking the wind out of their sails. Disgusting. Sun becomes more like Microsoft every day. And why not? What business would not want success like that? Keep your eye on the sparrow...
Geez, all of a sudden i'm a Cobalt rep. If you want to buy a turn-key solution, look at the Cobalt CacheRaq. Or go to freshmeat and look for something called 'squid'. Or roll your own.
That's silly. the RaQ is clearly intended to be a web-hosting appliance. why would you buy one and then complain about not having X? Why didn't you buy a Cube?
I have PHP, mySQL, egcs, servlets (JSPs and JDBC, too!) all running on my RaQ. I even managed to build Orbit (why?)
Right now we have low-level protocols like TCP/IP, we have medium-level protocols like HTTP. On top of that, we're going to have various kinds of XML-based data-exchange protocols. Dave Winer's XML-RPC is a sign of things to come. It's a bad sign that Microsoft knows more about this than the leaders of the Linux community. They've already incorporated it into a new protocol that they are calling SOAP.
At first, I agreed with Tim. But, after thinking about it, I am not worried. In fact, I'm happy for Microsoft. Yes, they are still trying to take an open platform and engineer it into their own technology tarbaby. And this does threaten a lot of what we hold dear. Microsoft is tilling new ground, and that's good for us all. We all know their seeds won't germinate. So, in the end, there will be opportunities aplenty.
I don't intend to take up for the KBE. However, i am amazed that folks accept the theory of evolution so readily. having been educated in the natural sciences, i must say that Darwin's theory is, in places, stretched beyond reason. i'm not saying it's wrong, but there's a lot it does not explain. rattle snakes, for example. i think we need to re-consider the origin of species, especially as chaos might be applied. evolution really is a dated theory.
now, a GNU reference implementation of some XML DTDs would be nice. without it, XML is another hatchling produced by commercial vendors. The point of XML is to separate you, the buyer, from your current technical commodities (eg: ASCII, HTML). that's just my opinion.
It must be a decent product if a Visual Studio weanie can fire it up and run it. I just wish a developer would post some comments with respect to: what compiler it uses, does it create makefiles, does it ship with any frameworks, libraries, etc. what languages, processors, etc it supports, is the java stuff worth looking at...
"Class wizard, I beseech thee. Grant unto me the power to render my application."
In a nutshell: peer review. The projects i have worked with spend a great deal of energy on reviewing ideas. They are all quite egalitarian about the review process, and it mostly takes place on email lists. Large pieces of work tend to get adopted by small groups, who may work off-line and then publish the result. A good example of this is the evolution of apache's mod_jserv, housed at java.apache.org. Thus, requirements and high-level design are covered. The mail list bantering, change logs, and source comments are all that is needed to keep many OSS projects afloat. Of course, this is amongst some very experienced and dedicated code-grinders. It should, however, serve as a point of reference. Oh, and BTW: not all of these developers use English as their primary language, yet the projects are expressed in English.
The worst programmers i ever worked with were game programmers. age matters not; its the paradigm. very hard it is to keep them from tear-assing through code. Old-time DOS hacks tend to be the best. that vintage had to learn the science of being bit-efficient AND the art of managing complexity. Coding without a net, so to speak...
I recommend you confine the 'app server' to: 1. managing state between http requests 2. connecting legacy stuff to HTTP responses 3. mapping HTTP requests into a transaction space.
If you can architect thusly, you can use this recipe: apache mod_jserv mod_php, mod_perl, etc. mySQL gnuJSP jWebForm
And remember, none of the above are mutually exclusive. Don't pay enterprise-class java grinders to hack html, and vice-versa.
Slashdot Mirror
No TCP/IP stack in the palm? That's funny. I guess all of the BSD sockets-based networking stuff I have written for the Palm is running on magic. And every byte of it was written on a linux box. The only money i have spent on palm development tools was to buy the o'reilly title on palm programming. Try finding a BSD-style interface to a Psion! Furthermore, go to http://www.palm.com/devzone. As of mid-February, they are officially supporting the GCC-based toolchain.
Mobile phone vendors have a vested interest in keeping their developmnet tool chain closed. why would you buy a new cell phone if you could go to freshmeat and get the features you want, or even roll your own?
Not for me.
I'll not look to interbase for embedding in my
web apps. i might use it for a transactional back end. But no DBMS runs faster alongside apache than mySQL (AFAIK). I can't imagine a better prototyping platform than PHP/mySQL.
Yeah, it bites that team Blackdown gets little recognition for their heroic efforts.
Since 'tis the season, you can help Blackdown by going to their website and ordering books. It's not much, but it may be all they ever get.
"While it is an interesting development, there's probably little cause for worry unless it
becomes a trend."
It is something of a trend, and has been for a while. But it is OK. the trend is something like this:
an idea gets some funding and a startup is born.
the startup, running on neophytes and/or directed by suits, turns up their services on NT.
the startup begins to mature, and eventually migrates off of NT.
Doesn't always work that way, but that's the trend.
Suppose I don't like the java servlet API. Maybe I think it is too complicated. So, i throw a few pieces out. Then I produce a servlet engine based on this new 'simplified' API. 95% of all current servlets are still compatible.
If I understand Bill Joy's comments, he says this is ok. I can 'fork' the servlet API by reverse-engineering it and modifying it.
But this flies in the face of what I understand to be Sun's licensing WRT java standard extensions, of which the servlet API is a member. So, what's the deal?
Here's some suggestions:
Produce a JVM for linux.
Don't kill NetBeans Enterprise for Linux.
Drop facades wrt the OSS community ("Let's stand on each other's shoulders and not on each other's toes". "A JVM for linux is hard to do because the linux distributions are SOOOO disparate".)
This is just vapor. Guess what? IBM, Inprise, and Transvirtual have DELIVERED java on linux. OK, Inprise is really just a JIT for Blackdown. But it's something, and it's commercial. Sun is blowing smoke in the hopes of taking the wind out of their sails. Disgusting. Sun becomes more like Microsoft every day. And why not? What business would not want success like that? Keep your eye on the sparrow...
Geez, all of a sudden i'm a Cobalt rep.
If you want to buy a turn-key solution, look at the Cobalt CacheRaq. Or go to freshmeat and look for something called 'squid'. Or roll your own.
mips
That's silly. the RaQ is clearly intended to be a web-hosting appliance. why would you buy one and then complain about not having X? Why didn't you buy a Cube?
I have PHP, mySQL, egcs, servlets (JSPs and JDBC, too!) all running on my RaQ. I even managed to build Orbit (why?)
Right now we have low-level protocols like TCP/IP, we have medium-level protocols like HTTP. On top of that, we're going to have various kinds of XML-based data-exchange protocols. Dave Winer's XML-RPC is a sign of things to come. It's a bad sign that Microsoft knows more about this than the leaders of the Linux community. They've already incorporated it into a new protocol that they are calling SOAP.
At first, I agreed with Tim. But, after thinking about it, I am not worried. In fact, I'm happy for Microsoft. Yes, they are still trying to take an open platform and engineer it into their own technology tarbaby. And this does threaten a lot of what we hold dear. Microsoft is tilling new ground, and that's good for us all. We all know their seeds won't germinate. So, in the end, there will be opportunities aplenty.
I don't intend to take up for the KBE. However, i am amazed that folks accept the theory of evolution so readily. having been educated in the natural sciences, i must say that Darwin's theory is, in places, stretched beyond reason. i'm not saying it's wrong, but there's a lot it does not explain. rattle snakes, for example.
i think we need to re-consider the origin of species, especially as chaos might be applied. evolution really is a dated theory.
Sun's community source license has done nothing but get in the way of java on linux. i don't think it will do anything for solaris.
why are they releasing the code to solaris, anyway?
now, a GNU reference implementation of some XML DTDs would be nice. without it, XML is another hatchling produced by commercial vendors. The point of XML is to separate you, the buyer, from your current technical commodities (eg: ASCII, HTML). that's just my opinion.
I'll take a dozen.
They use linux in their own cell-phone project and let the gnokii project go begging.
It must be a decent product if a Visual Studio weanie can fire it up and run it. I just wish a developer would post some comments with respect to: what compiler it uses, does it create makefiles, does it ship with any frameworks, libraries, etc. what languages, processors, etc it supports, is the java stuff worth looking at...
"Class wizard, I beseech thee. Grant unto me the power to render my application."
In a nutshell: peer review.
The projects i have worked with spend a great deal of energy on reviewing ideas. They are all quite egalitarian about the review process, and it mostly takes place on email lists. Large pieces of work tend to get adopted by small groups, who may work off-line and then publish the result. A good example of this is the evolution of apache's mod_jserv, housed at java.apache.org. Thus, requirements and high-level design are covered. The mail list bantering, change logs, and source comments are all that is needed to keep many OSS projects afloat. Of course, this is amongst some very experienced and dedicated code-grinders. It should, however, serve as a point of reference. Oh, and BTW: not all of these developers use English as their primary language, yet the projects are expressed in English.
The 1st RFC for FTP is older than I am.
The worst programmers i ever worked with were
game programmers. age matters not; its the paradigm. very hard it is to keep them from tear-assing through code. Old-time DOS hacks tend to be the best. that vintage had to learn the science of being bit-efficient AND the art of managing complexity. Coding without a net, so to speak...
I recommend you confine the 'app server' to:
1. managing state between http requests
2. connecting legacy stuff to HTTP responses
3. mapping HTTP requests into a transaction space.
If you can architect thusly, you can use this recipe:
apache
mod_jserv
mod_php, mod_perl, etc.
mySQL
gnuJSP
jWebForm
And remember, none of the above are mutually exclusive. Don't pay enterprise-class java grinders to hack html, and vice-versa.