Jaguar last build is _?
- Thread starter toast
- Start date
jaguar isnt really that good... im sorry guys its reallly buggy.
satan you make that sound as though you're dissappointed...it's a beta build, not evne that...a developer build. Stuff breaks al lthe time until they finalize all the code.
Don' use jaguar yet and expect it to work perfectly, that said one of the earlier builds right after the WWDC was failry stable as these things go and had a decent performance boost as well.
Don't condemn all of jaguar just yet, it's not evne out of the gates.
Don' use jaguar yet and expect it to work perfectly, that said one of the earlier builds right after the WWDC was failry stable as these things go and had a decent performance boost as well.
Don't condemn all of jaguar just yet, it's not evne out of the gates.
voice-
Registered
To be honest I don't give a rat's bottom to how buggy it is, I expect that to be solved by the time Joe Average gets hold of Jaguar anyway, what I care about is speed. Apps launch quickly people say, I expect them to RUN quicker too(hey, I don't sit around LAUNCHING my apps all day long).
If speed is decent now then I trust Jaguar will rule.
If speed is decent now then I trust Jaguar will rule.
Speed has been inproved greatly. It boots about 40% faster than 10.1 which makes me believe many routines have been optimized. Something we'll notice not only during boot, but while performing other operations as well.
Apps seem to launch about the same but the over all feeling of Jaguar is not sluggish like OS X. Window resizing, scrolling, etc have all been improved.
Most of the bugs I noticed were visual glitches. Jaguar didn't recognize the combo drive though and did have difficulty figuring out how to install some apps.
The seed I tested was from late May so I'm sure many improvements have been made since.
A lot has been changed to make it more like OS 9, but on the other hand, other changes have made it more like NeXTSTEP.
One thing that kind of bothered me is that the simplicity of OS X is being lost. Yes, Jaguar has a lot more features but does it have to feel more complicated as well?
Anyway, when it's released it's sure to be a success. I think Jaguar may be what OS X was truly meant to be.
Apps seem to launch about the same but the over all feeling of Jaguar is not sluggish like OS X. Window resizing, scrolling, etc have all been improved.
Most of the bugs I noticed were visual glitches. Jaguar didn't recognize the combo drive though and did have difficulty figuring out how to install some apps.
The seed I tested was from late May so I'm sure many improvements have been made since.
A lot has been changed to make it more like OS 9, but on the other hand, other changes have made it more like NeXTSTEP.
One thing that kind of bothered me is that the simplicity of OS X is being lost. Yes, Jaguar has a lot more features but does it have to feel more complicated as well?
Anyway, when it's released it's sure to be a success. I think Jaguar may be what OS X was truly meant to be.
Also in the area of speed Apple needs to fix NOW is just window "rendering". (I could not think of a better word). For example: I use a chat program called ICQ. For every message you send, you need to pop a little window with a text box. To do this, you double click a users name. In OS 9 the window pops right up and all the contents of the window are there. In OSX, first the window pops up with the drop shadow, then the contents of the window appear. This all happens in a split second, but it is noticeable. This is a major pain when using Graphic apps like photoshop, when a new window needs to be popped up for a filter or alert messages.
I think it's known as a self repairing window. In OS X they repaint themselves noticably slower than OS 9 or Windows.
What I don't like is how you have to click on the desktop or folder window to show the updated contents, like if you download a file to it or move a file to it through the terminal.
What I don't like is how you have to click on the desktop or folder window to show the updated contents, like if you download a file to it or move a file to it through the terminal.
You can paste files in the Finder, cannot cut them (but copy). We had a very long discussion about whether to include 'cut', too, on Apple's Human Interface Design mailing list, shortly before the list was cancelled altogether.
The basic problem for most nay-sayers was that when you cut a file (like you can in Windows), the state the file shows is 'half-still-there'. To be true to the thought, you would have to make it invisible until it's pasted somewhere else (moved and turned visible again). If you choose *not* to paste it somewhere else but copied another item (even in another application), the file would have to turn visible again. This would mean that the Finder has control over the clipboard, which is not exactly what we want. (It needs to know you're copying something else.) Also, the 'cut' command is not only meant to 'copy & erase from current location' but used (by many users) as 'clear', because they just ignore that the thing is in the clipboard. But this 'functionality' of the 'cut' command could not reasonably be implemented in the Finder, you have to have a different command for 'clear' or 'delete'.
As Apple wants the functions in the Finder to be as clear as possible, this seems to be a no go so far.
You'll need third party software for that functionality.
I tend to use the Terminal for transferring/copying more than just a few files and the Finder for a smaller group of files. I also work visually in the Finder, if I want to move files. Spring loaded folders are GREAT in Jaguar for exactly this task: Take the files you want to move ('cut'), move them to the left end of the Finder window, so it automagically scales back to 'Computer', then hold the cursor over the folder, it automagically spreads open and you can go all the way down into the directories until you let go of the mouse button ('paste'). It's one action less than cutting and pasting with the keyboard and feels more natural to me.
The basic problem for most nay-sayers was that when you cut a file (like you can in Windows), the state the file shows is 'half-still-there'. To be true to the thought, you would have to make it invisible until it's pasted somewhere else (moved and turned visible again). If you choose *not* to paste it somewhere else but copied another item (even in another application), the file would have to turn visible again. This would mean that the Finder has control over the clipboard, which is not exactly what we want. (It needs to know you're copying something else.) Also, the 'cut' command is not only meant to 'copy & erase from current location' but used (by many users) as 'clear', because they just ignore that the thing is in the clipboard. But this 'functionality' of the 'cut' command could not reasonably be implemented in the Finder, you have to have a different command for 'clear' or 'delete'.
As Apple wants the functions in the Finder to be as clear as possible, this seems to be a no go so far.
You'll need third party software for that functionality.
I tend to use the Terminal for transferring/copying more than just a few files and the Finder for a smaller group of files. I also work visually in the Finder, if I want to move files. Spring loaded folders are GREAT in Jaguar for exactly this task: Take the files you want to move ('cut'), move them to the left end of the Finder window, so it automagically scales back to 'Computer', then hold the cursor over the folder, it automagically spreads open and you can go all the way down into the directories until you let go of the mouse button ('paste'). It's one action less than cutting and pasting with the keyboard and feels more natural to me.
genghiscohen
Membrum virile
Veering back on topic, there are reports of 6C83.
