I will never understand this complaint. i can't imagine anything more annoying than having to constantly minimize and restore, minimize and restore, alt+tab alt+tab alt+tab back and forth to the GIMP every time i want to look at something else.
it's much easier just to point my mouse at the window i want to use, and start working.
by the way... last time i checked, the tool palettes were dockable. and they still are, unless they've removed that since 2.2...
considering that most of these companies have come out strongly in favor of DRM and a bunch of useless crap like Java based menus... yes. this *is* good, precisely because it will increase the chances that *both* formats will fail -- particularly now that a significant number of customers have converted their collections over to DVD, and these discs would offer practically nothing except to a small percentage of high-resolution big-screen types.
if having some BSD networking code and userspace tools makes OS X "BSD-based", then by god, OS/2 is also "BSD-based" -- and there's a damn good argument that Linux is "BSD-based".
No, this is not about reducing spam in the comments on blogs. This is about reducing the number of blogs whose authors post only spam. The number of such blogs is enormous -- most counts put it between half and 2/3.
I agree. Python is an excellent starting point for beginning programmers:
It has a very clean, refined syntax; It can be used equally well as an object-oriented language as a simple procedural scipting language; It is open-source, freely distributed, and cross-platform (so that students will be assured of the ability to install it on their home PC's easily and legally); and while it is easily extended, it has a very useful standard library which will fill the needs of beginning programmers for a few years to come.
Ruby is very similar to Python, and is another excellent choice, although I feel that the documentation for Python (in English, at least) is somewhat better.
Neither PHP nor Rails are good choices for beginning programmers -- while developing web applications is very simple for advanced and intermediate coders, remember that beginners can get into some serious trouble learning a programming language, a query language, and a markup language all at the same time. Perhaps these would be better for a second course.
Apple charges a very very large markup on their hardware, I don't think the margin on their software would be nearly as high.
the marginal cost of making a copy of software is near zero.
it would be support that could potentially become expensive, but there's no reason they couldn't offer the software license at low cost, and a separate AppleCare program for their commodity-x86 OS X customers, as long as they price them appropriately.
I think the problem is that you used the iTunes MP3 encoder. It tends to produce pretty poor audio quality even at 192kbps. LAME will do you much better:-)
You can even install LAME as an iTunes import plugin.
As for why it's necessary?
I wrote a script to convert a large quantity of files to low-bitrate vorbis (from both high-bitrate vorbis and mp3 sources) because I wanted to put a random selection of music on my Neuros' flash memory unit. I could fit much more by creating a directory full of low-bitrate vorbis files before sync'ing it.
You seem to have made the assumption that I would delete the original files. Not everyone manages their music in the same way.
(nevermind, of course, that bittorrent handles all of the file-splitting, integrity checking, and reassembly... and that mpeg4/3/2 and friends handle all of the compression)
Your claim that there is a "substantial" loss indicates that you have never transcoded from one lossy format to another.
Yes, of course -- there is a loss of quality. But the difference when going from LAME standard to Vorbis Q5, for example, is something more accurately described as "barely noticeable" or "reasonably insignificant".
Certainly, if you frequently transcode your files from one lossy format to another, you will begin to notice artifacts. But the losses from a single transcoding are so slight that it is quite often worth it for some added convenience.
The tabbed interface was first introduced by IBM's OS/2 Warp v3, where tabs were located along the side of a window. Most people first experienced tabs in Windows 95, when Microsoft introduced tabs along the top of configuration dialogs. Once tabs had hit Win32, they spread like wildfire throughout graphic user interfaces.
It is true that Opera implemented tabbed browsing before Firefox (some might say that this is due to the fact that it was developed prior to Firefox), but that is an asterisk on a footnote in the history of tabbed user interfaces.
Slashdot Mirror
it's much easier just to point my mouse at the window i want to use, and start working.
by the way... last time i checked, the tool palettes were dockable. and they still are, unless they've removed that since 2.2...
...or did you RTFA?
does vesafb even support 1600x1200? and more importantly, if it did, how would i read the text?
considering that most of these companies have come out strongly in favor of DRM and a bunch of useless crap like Java based menus... yes. this *is* good, precisely because it will increase the chances that *both* formats will fail -- particularly now that a significant number of customers have converted their collections over to DVD, and these discs would offer practically nothing except to a small percentage of high-resolution big-screen types.
the Darwin kernel is based on Mach.
spam blogs, on the other hand, are maintained by motivated spammers. they require a feedback system to report the blogger to the site administrator.
No, this is not about reducing spam in the comments on blogs. This is about reducing the number of blogs whose authors post only spam. The number of such blogs is enormous -- most counts put it between half and 2/3.
we're talking about the state here. everything it touches turns to stinky brown goo.
What does Google need with a starship?
Almost none.
Don't worry about it, guys. If people ever start clamoring for MORE blog posts, you'll know.
well, apple generally has a different concept of "truth" than the rest of us. i'm not entirely surprised they would tell an outright lie.
hey, you spelled "spaces" wrong.
It has a very clean, refined syntax; It can be used equally well as an object-oriented language as a simple procedural scipting language; It is open-source, freely distributed, and cross-platform (so that students will be assured of the ability to install it on their home PC's easily and legally); and while it is easily extended, it has a very useful standard library which will fill the needs of beginning programmers for a few years to come.
Ruby is very similar to Python, and is another excellent choice, although I feel that the documentation for Python (in English, at least) is somewhat better.
Neither PHP nor Rails are good choices for beginning programmers -- while developing web applications is very simple for advanced and intermediate coders, remember that beginners can get into some serious trouble learning a programming language, a query language, and a markup language all at the same time. Perhaps these would be better for a second course.
you just don't want to use it.
the marginal cost of making a copy of software is near zero.
it would be support that could potentially become expensive, but there's no reason they couldn't offer the software license at low cost, and a separate AppleCare program for their commodity-x86 OS X customers, as long as they price them appropriately.
You can even install LAME as an iTunes import plugin. As for why it's necessary?
I wrote a script to convert a large quantity of files to low-bitrate vorbis (from both high-bitrate vorbis and mp3 sources) because I wanted to put a random selection of music on my Neuros' flash memory unit. I could fit much more by creating a directory full of low-bitrate vorbis files before sync'ing it.
You seem to have made the assumption that I would delete the original files. Not everyone manages their music in the same way.
(nevermind, of course, that bittorrent handles all of the file-splitting, integrity checking, and reassembly... and that mpeg4/3/2 and friends handle all of the compression)
Yes, of course -- there is a loss of quality. But the difference when going from LAME standard to Vorbis Q5, for example, is something more accurately described as "barely noticeable" or "reasonably insignificant".
Certainly, if you frequently transcode your files from one lossy format to another, you will begin to notice artifacts. But the losses from a single transcoding are so slight that it is quite often worth it for some added convenience.
nothing they do makes much sense.
I, for one, prefer to shift gears with my right hand.
or are you as short-sighted as the folks who brought this up?
(nevermind that google's not even hosting it, of course, and that even if they censor it tonight, the images will still be on the webserver next week)
only just barely.
It is true that Opera implemented tabbed browsing before Firefox (some might say that this is due to the fact that it was developed prior to Firefox), but that is an asterisk on a footnote in the history of tabbed user interfaces.
all of the desktop images have firefox in addition to IE. i don't think any of the mac images on campus include MSIE anymore.