Ouh,
I didn't realize what kind of the avalanche of arguments I would start.
Maybe this tells that there is something bubbling under.
I don't want to hurt anyones feelings. I don't want bad blood.
I think there are so many different level persons involved in this, that
it will cause some misun
The whole thread had changed the subject a long time ago ...
On 04/18/2012 03:29 PM, Mark H. Wood wrote:
On Wed, Apr 18, 2012 at 11:34:26AM +0200, Derek Hohls wrote:
It all depends on your environment and the "rate of change". There are
many back-end systems (running on old but reliable technol
Although I don't think this mailing list is the appropriate list to discuss
these kinds of issues I will post my final word on this.
Just like we all use Java (at least the ones working with Cocoon) most of us
should be fair to admit that Java's progress is heavily been slowed down by
trying to
On Wed, Apr 18, 2012 at 11:34:26AM +0200, Derek Hohls wrote:
> It all depends on your environment and the "rate of change". There are
> many back-end systems (running on old but reliable technology) that
> hardly change at all. However, the web (and now tablets/mobile) has a
> very high rate of ch
On Wed, Apr 18, 2012 at 11:54:40AM +0200, Thorsten Scherler wrote:
> On 04/18/2012 11:24 AM, m...@digikartta.net wrote:
[snip]
> > Half of us would be out of jobs?
>
> jeje actually that is point of view. I know of colleagues that maintain
> some buggy developments and earn a good living. The pro
On Wed, Apr 18, 2012 at 11:30:58AM +0200, Robby Pelssers wrote:
> You should read this article 'Why Good Programmers Are Lazy and Dumb'
> http://blogoscoped.com/archive/2005-08-24-n14.html
>
> I think it's not so much about losing our jobs but about
> - trying to become more productive (gettin
Yep,
this fits for the theories and it holds true mostly. But..
it depends on the stakeholders you are dealing with.
If you are building apps and services for others or for production
anyways, there's no point on using beta code and in no case, alpha. Also
there is no point of choosing the lat
Well,
I also have a pretty strong opinion about the remark you make now.
Let's first make the distinction between
- innovators (people who are always trying to improve the way of working
themselves --> E.g. Reinhard Poetz who started C3)
- early adapters (people who see clear benefits i
On 04/18/2012 11:24 AM, m...@digikartta.net wrote:
Absolutely. But trying to stay on the edge of the trends won't fit for
us all.
And continous rewriting of apps doesn't make any sense. Why on earth
we can't create something that would last at least a decade?
jeje, I actually know about some
Torsten,
I understand your points.
Still, it depends on what are trying to achieve, how much do you have
time for it and what are your skills and competence. Also, from the
point of the business view, there is a concept of opportunity costs. It
may be reasonable to go on with the old framework
That's a good one!
- mika -
On Wed, 18 Apr 2012 11:30:58 +0200, Robby Pelssers
wrote:
You should read this article 'Why Good Programmers Are Lazy and
Dumb' http://blogoscoped.com/archive/2005-08-24-n14.html
I think it's not so much about losing our jobs but about
- trying to become more p
On 04/18/2012 07:58 AM, m...@digikartta.net wrote:
Ciao Alberto,
you'll probably right.
What comes to Cocoon lifecycle, I don't get it. Has C3 anything in
common with C2 except the concept of pipelines? Can you do the same
things with it?
When C2.2 was published, I fell off the wagon because
Mika
It all depends on your environment and the "rate of change". There are
many back-end systems (running on old but reliable technology) that
hardly change at all. However, the web (and now tablets/mobile) has a
very high rate of change (and expectation of change). The point here is
that by u
You should read this article 'Why Good Programmers Are Lazy and Dumb'
http://blogoscoped.com/archive/2005-08-24-n14.html
I think it's not so much about losing our jobs but about
- trying to become more productive (getting more done in the same amount of
time)
- avoiding repetitive work
The
Absolutely. But trying to stay on the edge of the trends won't fit for
us all.
And continous rewriting of apps doesn't make any sense. Why on earth we
can't create something that would last at least a decade?
Half of us would be out of jobs?
- mika -
On Wed, 18 Apr 2012 10:50:37 +0200, gelo
I totally agree with Robby's opinion. The trend is to use HTML5 on the
client side in case of Web apps.
Greetings,
Greg
18-04-2012 10:27, "Robby Pelssers" napisał(a):
> Just my 2 cents on this topic...
>
> Cocoon forms was at the time in my eyes a pretty awesome solution to build
> highly dynami
Hello,
I would like to share my opinion on C3. I think that dropping support for
the most of native Cocoon components is a good step forward. As you see
trends now in enterprise applications, everybody from RedHat to Oracle
limits the amount of code from bare application server core engine making
Just my 2 cents on this topic...
Cocoon forms was at the time in my eyes a pretty awesome solution to build
highly dynamic forms with support for continuations. But as we all know this
puts considerable strain on the server side. Gradually we started seeing a
tendency towards AJAX (XmlHttpRequ
18 matches
Mail list logo
