The company i work for didn't necessarily think open source was crap,
they were more afraid of being sued.
On Apr 2, 1:52 pm, Ryan Waterer wrote:
> "Do you know why your previous company, or any other for that effect
> would want to limit open source software?"
>
> A company that I've worked at
On Thu, Apr 2, 2009 at 3:55 PM, Viktor Klang wrote:
> On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer wrote:
>>
>> "Do you know why your previous company, or any other for that effect
>> would want to limit open source software?"
>>
>> A company that I've worked at in the past had this belief that
Viktor,
Isn't that the truth!
I can't believe the murder that some third party "solutions" get away with.
On Thu, Apr 2, 2009 at 1:55 PM, Viktor Klang wrote:
>
>
> On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer wrote:
>
>> "Do you know why your previous company, or any other for that effect
>>
On Thu, Apr 2, 2009 at 9:52 PM, Ryan Waterer wrote:
> "Do you know why your previous company, or any other for that effect
> would want to limit open source software?"
>
> A company that I've worked at in the past had this belief that if they
> didn't pay for the product,
> then it must be crap.
"Do you know why your previous company, or any other for that effect
would want to limit open source software?"
A company that I've worked at in the past had this belief that if they
didn't pay for the product,
then it must be crap. In essence, if someone isn't charging you for their
product, t
Thank you Justin.
Bear with me a little longer please.
On Thu, Apr 2, 2009 at 3:36 PM, Justin wrote:
> This question is easy to answer, my last two employers
> forbid the developers from using Spring (one company limited open
> source software ...
Do you know why your previous company, or any o
Marcelo,
It sounds like what you are really asking is why would people use EJBs
over Spring. This question is easy to answer, my last two employers
forbid the developers from using Spring (one company limited open
source software and the other had ideological problems with Spring).
I haven't use
TBH It's mostly because the shop is more comfortable with EJB. I think
we're still in it's "sweet spot" but only because every time we venture out
of the sweet spot, it hits us with a large, blunt hammer. Like I stated
before, EJB + Seam is almost nice, however we went a different route for our
f
Josh
On Thu, Apr 2, 2009 at 10:00 AM, Josh Suereth wrote:
> Being an EJB 3.0 user (and previous Spring user), I still think Spring has
> the upper hand in terms of architecting an application. EJB 3.1 is closing
> this gap, but it's more a matter of how soon can it do so vs. how many
> people a
Being an EJB 3.0 user (and previous Spring user), I still think Spring has
the upper hand in terms of architecting an application. EJB 3.1 is closing
this gap, but it's more a matter of how soon can it do so vs. how many
people are jumping ship.
Right now EJB 3.0 is a box. IF your app fits in th
IMHO there simply is none. The only argument I see creeping into
projects from time to time is a political one: it's standardized.
Regards,
Ollie
On 1 Apr., 17:44, Viktor Klang wrote:
> I never really understood the need for EJB, the 2.x version was so
> boilerplatey it could kill on sight, and
I never really understood the need for EJB, the 2.x version was so
boilerplatey it could kill on sight, and by the time 3.0 was out, I'd
already moved on...
I'd really love some compelling arguments on why to use EJB, anyone care to
enlighten me?
On Wed, Apr 1, 2009 at 5:11 PM, Marcelo Morales w
12 matches
Mail list logo
