Re: About instance's integrity.
Re: About instance's integrity.
- Subject: Re: About instance's integrity.
- From: "dododo2020 dododo2020" <email@hidden>
- Date: Mon, 24 Nov 2008 11:24:09 +0900
> > I think WO is the best tool but EO is not for everyone.
> I would agree with this ... EOF is excellent, but there are aspects
> that I wish were more configurable. That said, I have never found a
> problem that I couldn't solve.
> > When I try to find developers for WO other than me,it was difficult
> > or high cost.
> > People who can select to learn WO or EO is very limited.This is
> > contrast to PHP.
> Yes, there are a huge number of PHP developers. If you find a WO/EO
> person, they are likely to be a lot more expensive (and harder to find
> in the first place), but if you do, they are likely self-selected to
> be a much better quality developer on average. We don't hire WO
> people. We hire good developers and we train them on WO. Honestly
> this would be true of almost any organization. Most companies use a
> mix of technologies and you rarely find someone who can just roll in
> off the street and work on your system. There is always a training
> investment.
Thanks for good advice.
But unfortuantely I can not invest much for new developers by now.
PHP guys may invest to learn by themselves. WO developers may live mainly with contract works only for clients who can understand them. The clients may decrease finally. This may be a weak point in WO.
Ruby guys are breaking their situations and I hope WO also break something.
> > So I am afraid that using EO may not be the best solution.
> I'm not sure I would necessarily conclude this ... This same argument
> could equally be made for the "WO" part of WO/EOF, right?
EOF may be sufficient for most web projects.
But for cross projects with existing resources or something EO(I mean DB layers of WO) may not the best.
I think cross projects will increase more and more even if you can work with EOF and EOF works fine by now. So adjusting with EO each time will be a extra work.
I myself am new to Hibernate(know what hibernate is from its early versions but it was not my solution). And started to consider it yesterday again.
I also use my own generator in addition to EOGenerator.
My generator uses simple format which defines one object per one line of text for input.
I may like POJO for my generator.
I just want something to break WO's situations.
And I am designing my reusable architecture for my current problems.
I am taking this list as digest and am not sure whehter I have read all the answers and could reply or not by now.
Best regards,
Ken
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden