Thread

I see that everybody is happy with the delay, good for them.

I don’t think anyone, least of all the developers, are happy with the delay. There’s a difference between being understanding and supportive and being happy.

And you do have to realize the forums are probably mostly filled with EE cheerleaders that have received outstanding support in the past, so they’re apt to give them a pass on being late.

It’s not a good thing they missed their date. I don’t think anyone is saying this. Delays suck. But people have confidence they new product will be worth waiting for and getting “right.”

I’m just glad the delay was announced. I was more irritated at the fact there was no news than I am by the news itself. No there’s no need to wait to roll out a project.

I’ll catch 2.0 when it comes out. I’m still looking forward to it, still think 1.6 meets most of my needs, and still trust the EE team to make something cool.

My point is that with this kind of attitude (as you can see I’m avoiding to use the proper word), is not constructive.

My point is that with this kind of attitude (as you can see I’m avoiding to use the proper word), is not constructive.

this sounds very constructive.

Thanks for adding to our deconstructive effort.

My point is that with this kind of attitude (as you can see I’m avoiding to use the proper word), is not constructive.

Lost me a bit. Really not sure what word you want there.

I do think the EE developers can be held to task for missing a deadline. I know there’s a lot of people on here that are disappointed. Some people were comparing the release of EE 2.0 to Christmas, and the EE folks took Christmas away! (Or at least delayed it). But what’s the point to getting all bent out of shape? It won’t change anything.

I’m guessing you;d see a much different attitude if they said the release was canceled, but it’s just delayed! Don’t worry, Christmas is coming. It’s just not going to be in the summer as promised.

I’m not sure what kind of attitude you think would be constructive. From the reactions on here you see mostly understanding and supportive individuals.

EE miffed one. Oh well, it happens. If they had a track record of this sort of thing I’d be the first to pile on (pretty much anyone will back me up on that), but I just don’t see a reason to get pouty (yet). One, it won’t change anything. Two, it’s not really helpful.

What would you have them do at this point? Software delays are part of the industry. This doesn’t excuse the delay, but had they shipped it on time, and there was reason why it shouldn’t have made it out the door yet, then I’d bet you’d see quite a few complaints. They avoided a bad launch, which to me is worse than an inconvenient delay. Just look at Apple’s recent mobileme services.

It’s unfortunate that people have to wait. Again, I don’t think anyone is happy with this idea. But I think the consensus is that people would rather have a quality product late, than an unfinished product on time.

I do think the EE developers can be held to task for missing a deadline.

As far as I know there was never a deadline. EE 2.0 was said to be out by Summer 2008. There was nothing official about a particular date. That’s why I don’t think it is a big of a deal and I believe we sweat too much over this.

Even though we can’t wait to see EE 2.0, 1.6.4 is awesome and it does a lot as long as you are a good developer.

In other words, if you know what you’re doing, EE is great no matter what version.

I don’t think anyone is contending that a deadline wasn’t missed. Whether you say “Summer,” or give a specific date, announcing a delay on your release constitutes a missed deadline in my opinion. I also think it’s not a big deal.

It’s not unreasonable to hold people accountable. Reread Rick’s statement, and I think you’ll get the feeling that internally they are doing this. There’s nothing wrong with admitting things didn’t go as expected, taking responsibility, and moving on.

That said, I think the way people are dealing with this (on these forums) is the productive course. Suck it up, shrug it off, and hope the final product is more amazing than melted cheese.

agree.

I might be the bad guy here, but don’t forget that I’m also an EE user (and a customer). You can find elsewhere other people (including me) complaining about the delay. I believe this caused Rick to come out and explain a bit what is going on.
And finally, I do not understand why a delay will guarantee a better a product.

A delay will not guarantee a better product, but a rush job almost certainly guarantees a shoddy one. In the past, EllisLab have had a policy of not giving out release dates, even estimates, or roadmaps. This time, we decided to give our users an estimate. I am very glad about the—mostly—mature reactions about the delay; think about the alternative, ie not giving out a date at all (“it will be ready when it’s ready”).

I might be the bad guy here, but don’t forget that I’m also an EE user (and a customer). You can find elsewhere other people (including me) complaining about the delay. I believe this caused Rick to come out and explain a bit what is going on.

And finally, I do not understand why a delay will guarantee a better a product.

I take it you have never worked on something and experienced an unforeseen problem that took a little longer to fix. Or perhaps there is a better way of achieving something that will take longer to create?

I too am an EE customer but right now I am an EE 1.64 customer. It’s not like it’s buggy and a fix is whenever.

stinhambo, o.k. I understand that are you happy with with 1.64.
But wait…, you clever guy, you have a beta copy of EE 2.0, ehh?

stinhambo, o.k. I understand that are you happy with with 1.64.
But wait…, you clever guy, you have a beta copy of EE 2.0, ehh?

I didn’t think I’d ever use the ignore feature on EE’s forums, but there’s always a first time. Personal attacks don’t exactly win you any friends around here.

EL announced an intention to release EE 2.0 within a certain time frame. If for no other reason than the public betas not happening, the writing was on the wall that the schedule was slipping. Given the choice between a buggy product that’s rushed out of the door and waiting for a more stable .0 version, it’s a no-brainer to wait. EE 1.x works just fine and while the published features or EE 2.0 look interesting, it’s nothing that I must have right now.

stinhambo, o.k. I understand that are you happy with with 1.64.
But wait…, you clever guy, you have a beta copy of EE 2.0, ehh?

Hi Theos,

I see you have less than 20 posts in the EE Community, so we’ll cut you a little bit of slack. We are a group of professionals. We treat each other this way.

You’ve expressed your dissatisfaction with the delay, which is just fine. Criticism is perfectly acceptable.

However, you’ve moved on to being cynical and argumentative, which is not welcome here. Its not professional. Take that somewhere else. Thanks.

But wait…, you clever guy, you have a beta copy of EE 2.0, ehh?

I don’t think anyone but the dev team have a beta version in their hands. I could be wrong. But if I am I would not be upset with that. I haven’t yet earned the privilege. I still have much to offer to the community before I can be given this privilege.

I believe that only respect and contribution to the community can earn me this.

Also, what kind of argument is this? How old are you theos?

However, you’ve moved on to being cynical and argumentative, which is not welcome here. Its not professional. Take that somewhere else. Thanks.

with that being said, let’s please just call this over.