+1
This is not the complaints department. The incessant whining about the same things is depressing. Time Dwarf, Roaring Guy On 2012-03-16, at 10:51 AM, Peter Teeson < email@hidden> wrote: +1 to you, Jens, and Fritz.
If possible would the moderator please intervene. After all this is not Usenet.
If not I guess I'll have to add a rule to this mailbox. But I'd rather not. Sigh!
respect…..
Peter
On 2012-03-16, at 1:35 PM, Andy 'Dru' Satori wrote:
This has nothing to do with hearing negative. It has EVERYTHING to do with repetitive, non-constructive criticism.
So far in your 3 weeks of diatribe, you have offered not a single bit of constructive criticism. You haven't even offered a single well defined problem, just lots of un-reproducable anecdotes of YOUR problems and that Apple needs to 'Fix It'.
I walked away during the first week because I realized then that you are either A. unwilling to engage in constructive discourse, or B. incapable of seeing any view but your own. At this point, I can only add C. incapable and unwilling to see any point but your own, and unwilling to engage with the community in any positive manner.
Further, at this point, any action to moderate your posts will only result in you going into other venues and telling everyone how Apple is mistreating YOU.
It is a no win situation, and quite frankly, it's old. I cannot think of any solution that would work better for the community than if you pack up your toys and go home, and let those of us that find we can, do and will use Xcode quite effectively to do so and discuss how we can work around the issues that we occasionally run into. (like having an & in the company name would break many templates prior to Xcode4).
-- Andy 'Dru' Satori On Friday, March 16, 2012 at 1:23 PM, Alex Zavatone wrote:
Sorry if you don't like hearing negative feedback on the product, but I've worked on, tested and released many versions of complicated IDE/SDKs and other complicated products before and also have spent years listening to people's feedback on its strengths and weaknesses.
It doesn't matter if it doesn't work for "me". The product needs to be better.
I've seen numerous incidental reports here about people who can't get through a day of using Xcode without running out of RAM on a 16 GB Mac and without many crashes.
These are the EXACT issues that need to be reiterated about the product in addition to learning how to use it to provide solutions for its users.
If the group is not aware of its pitfalls and the pain it can cause its users, then people are only partly aware of what they need to be aware of or if they need to search for other tools to accomplish their goals.
While we use Xcode to make money, Xcode also costs us money when it does not work.
So, regarding the crash? You have to remove any invisible .SVN repositories out of your project if you have removed your project's SVN Repository from the Organizer. If you don't and desire to rename any of the project filed through the Xcode GUI, Xcode is likely to crash on you.
Naturally, this shouldn't happen.
On Mar 16, 2012, at 1:06 PM, Jens Alfke wrote: On Mar 16, 2012, at 8:02 AM, Alex Zavatone wrote: So, in Xcode 4.2, I just created a new UIViewControllerSubClass, named it and was ready to start working.BLAM! Xcode craters. Words failing me at the moment.
Dude. Your Twitter client is that narrow window over on the other monitor. What you actually typed into by mistake is your email client.
Random ‘FML' bitching is for your tweeps*. The Xcode-users mailing list is for posting constructive questions and answers relevant to hundreds (thousands?) of other developers who’ll end up reading them.
I can’t believe I’m saying this, but: Hey Apple folks? This list needs more moderation, right now. It’s becoming a real pain to shovel through the bitching and find the actual relevant content.
—Jens
* And hey Koko? Ad hominem attacks and physical threats are for /dev/null.
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|