![]() ![]() ![]() ![]() Thus, my need for Leopard-compatible SD is not urgent, but I’d like it some time in the not-too-distant future. I’m on Time Machine for the time being on my main machine, but the other two Macs on the network are not being backed up, but their data is not changing much so old backups are sufficient. I, for one, appreciate your thoroughness and conscientiousness when it comes to getting SD for Leopard right the first time. at 09:50 am | not sarcastic-just pre-acknowledging the inevitable, hopefully with a that’ll certainly work: low-level copying like that avoids the kinds of things we’re seeing, because it doesn’t really work with the file system structures at all. People do have reason to be frustrated… That’s why regular updates are important - and appreciated. I commend your decision to post an update. However at some point the comparison between the relative bugginess of the currently used and shipped version to the relative (lack of?) bugginess of the upcoming internal version makes us decide to release, and then everything repeats itself. The only difference is that at some point we’re less aware of them. Software is a tricky thing - at any given point of the development process it always has bugs. Don’t allow the pressure beast cast a shadow on your programmer day It’s ready when it’s ready. I’d rather wait for a backup solution that I can trust. So I’m still running Tiger on all but a couple of test boxes. There are alternative backup methods available but I don’t have the confidence in them that I have in SuperDuper. Seriously, I’m glad you guys are beating the hell of this so we don’t have to worry. Your laziness, incompetence, lack of communication and general suckitude are now legendary. Once they have the finished product in their hands, they’ll shut up and move on to some other personal crisis.Īs long as I know progress is being made, than I’m a happy camper! I know you get a lot of whining from those with entitlement issues, but you always will. I want my SD!, but I don’t want it to break anything, so you guys keep at it, and I"ll grit my teeth, too. I just wish more software developers had your level of laziness, incompetence, lack of communication and general suckitude. Greetings from Germany and good luck with your new “workaround” DVD) and then use the Apple Disk Utility.app? Thanks for informing us about the new problems.īTW Is it right, that till now the only secure method of cloning my macbook drive is to boot from another 10.5 volume (e.g. Your dedication is appreciated.Īfter 97 comments a new thread with a lot of room for new fun! I’ve worked for some of the industry’s largest software companies and too many times I’ve seen a product rushed out the door with the “we’ll fix it later” attitude. I have tremendous respect for your desire to get things right before releasing the product. The trackback URL for this entry is: Trackbacks are disabled for this entry Sorry for any inconvenience: it's not that I don't want to hear what you want to say. I'll turn them back on after the backlog clears. You can still review existing comments by clicking the title of this post. Note: I've had to turn comments off for a little while because the subscriptions to comments are overloading my outbound servers (every time someone posts something, it's sent to the 200 people above their post), causing delays for regular support mail, etc. If my new idea works, this will hopefully only delay things a few days, which will be plenty of time to fill the comments with complaints of our laziness, incompetence, lack of communication and general suckitude. Then, the failure needs to be investigated, understood, reproduced.Īnyway, we'll leave that between me and my ulcer. ![]() Sometimes, 99% of the way there, you get red. We always are hoping for green lights at every stage. This is why we don't just implement a fix and release, of course: we want to ensure it works before we toss it out there, and so we smoke test, test internally and then-if internal tests are OK-test externally, every time. I can't begin to tell you how frustrating it is to have a set of simple tests work and then find that the thing we found rearing its ugly head again in another (more complex) scenario that can (and did) happen in "real life". These tests are really time consuming, as you might guess: it can take eight hours to rebuild a complex-case volume (so I try to keep one building while another is testing), and then more hours to run the test. I think I have a way of dealing with it, and so we're going to implement Workaround Part IV: The Reworkening and run it through the wringer. Unfortunately, we've found a case where the workaround doesn't, um, work. A few days ago, we were happy to get a workaround for the bug mentioned in a previous post, so we went about implementing and testing-and things were working quite well. ![]()
0 Comments
Leave a Reply. |