Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
WWDC 2013 Rumor Roundup: iOS 7, OS X 10.9, iRadio, and New Macs
- Thread starter MacRumors
- Start date
- Sort by reaction score
It isn't a usability problem. It does work if you use it right. Press the eject button and pull out the drive. If done correctly it is completely transparent.
The user has to communicate with the system.
The perspective of "I don't need to tell you what I'm doing" is the problem. Not usability. Being selfish and myopic is the flaw.
How is that any different than pressing the eject button one the drive on the Finder. the power for ejection? That isn't transparent.
The nominal mode for Time Machine is to back up constantly. Perhaps when turn off TM it should perhaps offer an option to dismount the drive also at that time. ( or can have preference to make it do "off and dismount" in without confirming. )
That's the way CD ROM and Floppy drives used to be. Apple has gone with buttonless ( e.g., Thunderbolt display with nothing. not even power ).
Buttons for USB sockets would take too much space (e.g., has to live on laptop edges with very limited space. )
It is doubtful that would work because most of the USB device is outside the box. Most folks who are in the "I just want to do it my way, I don't care what the proper way is" are just going to grab and try to yank it out anyway. More than a few of them are going to break the button and/or its mechanism.
It isn't a usability problem. It is more of an issue that the process is characterized as so simple don't have to learn it. That's a joke. Along with the almost zero user manuals these days because "it is all intuitively obvious" so needs no training hooey.
-> there is a limited amount of good engineers. You can't hire every guy who claims to be an engineer because he did a webpage once.
-> 9 Women can't make a baby in one month. Same with software.
Some problems can't be parallelized and needs to be implemented serial.
-> it doesn't make sense to hire more people if you don't need them unless you have a crunch time. In most cases it is better just to move the release.
Especially apple says "its done when its done".
iOS isn't built on Objective-C. The Coca-Touch libraries that application use, but not the operating system itself. C (and maybe some C++) are in the OS bowels.
Android OS layer is not Java. It is linux and same issue C ( and some C++ ). A large subset of the application libraries is layered on Java, but somewhat gain the JVM quite capable of coding done to assembly level if warrarnted ( just-in-time compiler).
Huge problems with a decent garbage collection implementation typically have the exactly same root cause: poorly coded app.
A garbage collection system probably need more working space but given appropriate working space area to work it can be effective. It is far more trotted out as a boogeyman by C (and derivative ) fans than is a bigger problem than poor app coding. There are bad implementations of a GC, but Java doesn't necessarily have to use one of those.
Stoked..
Well.. we're always hoping for more, but I'm stoked to drop some money at the end of the week on a new retina pro.. can't wait (I'm still on first gen thunderbolt).
Well.. we're always hoping for more, but I'm stoked to drop some money at the end of the week on a new retina pro.. can't wait (I'm still on first gen thunderbolt).
In the 6 years since 2007 Apple could have rounded up 200 highly potention students. Paid their way through 4 years of college and a year of Graduate school and they still would have been available before they were needed in 2013.
It isn't that limited. That is an tired excuse Apple trouts out when they have done a crappy job of long term HR management. It chronic problem becaues Apple keeps it in that state. 5 years is plenty is of time to staff up.
That really isn't what is happening here. Basically there is bubble of workload because alot of stuff is just being thrown out and redone. It really isn't new stuff it just changing what is there.
In that sense it is better just to use the folks you already have since they are famillar with the infrastructue. The OS X folks being pulled off probably have to do much of the same kind of "flattening" on OS X too. What should happen is that the iOS folks are in turn "borrowed" to help offset some of the OS X delay. Again if it is similar flattening to equivalent parts of the bundled applications then the work should go even faster this "second pass" through.
However, what is completely missing though is that "it is done when it done" presumes that the scope is set right. It took several iterations of iOS/OS X to glossy/shiny/skeumorph them. It could just as well take 2 iterations to yank all that out if they wanted to. Part of the resource alloaction adjustment is because they are trying to do a "big bang" change. Well Apple isn't on a "big bang" update schedule anymore. They had put themselves on a yearly update schedule. That means eithre need to scope down to what fits into a year or staff up so can do more in a year. One of the two. Not scope up and keep staff constant and kneecap other products.
Last edited:
I really hope you're not a software/hardware developer, with that attitude to the user experience.
The problem is a one step task (removing a drive) is being made into a two step process (press the eject button, then remove the drive). Users can easily forget the additional step, and a unforgiving interface is never a good one.
Exactly! Well stated.
It wasn't until 2007 that Apple began shifting engineers, resulting in OS delays. Moving to a yearly cycle is not helping matters.
I've been called selfish many a time, but never because I didn't respects the needs and feelings my my operating system.
I know how virtual memory works, and it's paging to the disk more often than Windows does and my Macbook has double the ram, so no, it uses more RAM.
I also know the differences between programming languages and how far away they are from machine code, yes JAVA's a bloated bitch, everyone knows that, but the differences between Objective C and C resources wise is practically non existent, therefore the OS itself must use more ram, not the programming language.
Nope, iOS boots up and uses half of my RAM (iPod touch 5, so ~256MB in use, although I get about 170MB free ram, so it's more like ~300MB upon boot.)
I hope they fix the issue in Finder and OS X in general where the disk access is not on a separate thread! Whenever you press "save" in some app, any external hard drives have to wake up before the window shows up, even if you just want to save it to your internal hard drive. They should make the disk access a separate thread.
Also, Finder really hates it when AFP servers drop. It sometimes crashes. Please fix.
Also, Finder really hates it when AFP servers drop. It sometimes crashes. Please fix.
Maybe or even iWatch (just to get people's hopes up
Tim Cook didn't sound that confident about iWatch during D11. But I read somewhere on this forum about an iBookstore workshop, so something related to iBooks might get updated.
You are disconnecting from what is really going on. Usability and the user experience has encompass what is actually happening. Not what users wish would happen. Users and compter systems are engated in a shared activity. They both have responsibilities. To heap all of the responsibility onto the computer and none on the users is a cop out.
No it isn't. It is two step process. The communication is a necessary step. It isn't optional or magical.
The USB drive is being shared with the computer. If it was another person an object was being shared with and some just walked up to them and snatched it out of their hands with communicating that would be a selfish and myopic act. It isn't particular different if do that with the computer. Still selfish and myopic.
Just simply going to through the step of communicating "I want to take this away now" is not onerous action.
Promoting the notion that the computer has to do what you want to do even when you don't give it instructions on what to do is not promoting usability.
Although I wouldn't agree with this status, as Apple OS's are always better at memory management than the competitors, I will however agree they need to up there game as the latest Apple OS's have been far more memory hungry. Mountain Lion eats up a hell lot more than Snow Leopard ever did - further more the Retina Macs seem to eat up even more - not sure if it's the pixel doubling or double size images but it's not cool - I have 16GB of ram and am constantly at 400mb or less - and I really don't have much open - this is my 4th retina mac and if you look at activity manager apps usually take up around double the ram that they did on a non retina mac.
I love my retina mac when it comes to portability, I love the display (except my 2013 one is now ghosting like the other few did) and I love it for fast application opening, fast startup and quick file transfers - but general performance wise is **** for the money paid for it.
I love the features of Lion/Mountain Lion (except the scroll bars can be annoying when trying to click the last item in finder) but yet again it really doesn't perform well. I wish I could put Snow Leopard on my rMBP and see if it is a Mountain Lion problem or not.
----------
He's got to be secretive, but yes I wouldn't hold my breath, doesn't seem fitting for a developer conference anyway
I was just joking.
I, and I think I am not alone, disagree and still listen to radio. Local radio. The iPod, to me made satellite radio redundant - why pay to listen to music I already own. But local radio still offers something an iPod and satellite cannot - Local info. From weather, news, traffic, concerts/events, etc. That is why I still listen to local radio. If it was dead, they'd have all gone under, no?