Actually, no. If you click a link to a feed (starting with http) Safari does the "right thing." That is, it displays it with its feed format. It actually makes all of those little orange RSS buttons useful. In addition, "feed" is not an invented URI scheme. See here.
Oh come on, now don't be ridiculous. The majority of slowness in Java under OS X (though it looks great), isn't in their "basic graphical algorithms" (end programmer specific), it's in the tools which we are given to work with, i.e. the Swing API. Basic things like moving between text boxes, pulling down menus, and resizing windows are all up to Apple's implementation of the JVM. Although they're doing a fantastic job, it could still be improved a lot. This has nothing to do with the end programmer fixing up their own algorithms!
A big problem today is people learning the latest buzzword and perhaps the syntax/semantics behind it, but not knowing when to use it, or more importantly, when *not* to use it.
I had to buy Applying UML and Patterns by Craig Larman for a software engineering class last semester, and it's very good. Not only does he follow a case study through the whole book (a POS system), but he hacks down people for spending too much time on diagramming. He also suggests "UML Distilled" as a pure reference, mentioned several times in comments above.
Most importantly, the UML is just a display medium, not a process. Just saying "lets use the UML" isn't going to help anyone. Larman discusses the Unified Process (UP) in depth, which is all about short, time-boxed iterations which *do not slip*. In the UP you push features out of an iteration rather than have it go over deadline.
If you're considering using the UML at all, get this book. (not to mention it's a great software engineering text in general, teaching many fundamental patterns and principles including many from "Design Patterns" but with Java as an example language)
The effect of gravitational lensing depends on our alignment to the source. In a perfect or near perfect alignment (the case here), we see many rings and arcs. Slightly off we see arclets, followed by weak distortions. The closer to perfect alignment the better, as the magnification effect is stronger and rings, arcs, and mulitple images allow the calulation of mass and distance to both the source and the lensed matter.
Heh. Well if you're going to get technical, it's really OS X Server that is the 'true' decendant of Rhapsody.
Calling OS X "just NeXTSTEP with a face lift" really undermines all of the quality work that has gone into it, including Classic (the enviroment where all pre-OS X apps run), a full Java 2 implementation, and oh so much more (see Inside Mac OS X: System Overview for everything you ever wanted to know).
On the contrary, I found this piece to be very well balanced between the platforms.
..."To cast Microsoft and its head honcho Bill Gates as the Great Satan, or as the Sauron to Apple's brave little band of hobbits, is ridiculous. Both co-founders, Jobs and Gates, are much more alike than different"...
..."Ironically, in light of the bad blood that was to to come between the two companies, Microsoft's Excel (a GUI-based spreadsheet similar to its predecessor VisiCalc, but easier to use) gave the Mac much-needed viability at the time."...
..."Impelled by the popularity of its own Win-compatible versions of Word and Excel, and numerous other 3rd-party apps, Microsoft sold over 3 million copies of Win 3.0 in its first year of release, and Apple felt the chill. Win 3.1 (April '92) added scalable TrueType font support and better multimedia capabilities, and Apple was on the run. For the first time, Windows-equipped PCs were outselling Macs."...
..."[Apple's] doom seemed inevitable when, in August 1995, Microsoft unveiled their groundbreaking Windows 95 OS. Win 95, the first operating system to take full advantage of Intel's powerful 32-bit chips and a virtual clone of the Mac GUI, seemed to be the irresistible force destined to finally run Apple out of business once and for all."...
..."(which conflicts with the stories passed around the campfires of Apple fans, who like to portray Gates as a petty thief who snarled to his Windows team, "Make it look just like a Mac!")."...
And if the author were is an "obvious Mac lover" he *definitely* would not say:
..."The Rhapsody OS metamorphosed into the Apple OS X, incorporating elements of the previous OS 8 as well."...
as the Rhapsody OS metamorphosed into "Mac OS X" (Apple is the company), incorporating elements of *OS 9*. Having a broken link means nothing
Slashdot Mirror
Actually, no. If you click a link to a feed (starting with http) Safari does the "right thing." That is, it displays it with its feed format. It actually makes all of those little orange RSS buttons useful. In addition, "feed" is not an invented URI scheme. See here.
Oh come on, now don't be ridiculous. The majority of slowness in Java under OS X (though it looks great), isn't in their "basic graphical algorithms" (end programmer specific), it's in the tools which we are given to work with, i.e. the Swing API. Basic things like moving between text boxes, pulling down menus, and resizing windows are all up to Apple's implementation of the JVM. Although they're doing a fantastic job, it could still be improved a lot. This has nothing to do with the end programmer fixing up their own algorithms!
A big problem today is people learning the latest buzzword and perhaps the syntax/semantics behind it, but not knowing when to use it, or more importantly, when *not* to use it.
I had to buy Applying UML and Patterns by Craig Larman for a software engineering class last semester, and it's very good. Not only does he follow a case study through the whole book (a POS system), but he hacks down people for spending too much time on diagramming. He also suggests "UML Distilled" as a pure reference, mentioned several times in comments above.
Most importantly, the UML is just a display medium, not a process. Just saying "lets use the UML" isn't going to help anyone. Larman discusses the Unified Process (UP) in depth, which is all about short, time-boxed iterations which *do not slip*. In the UP you push features out of an iteration rather than have it go over deadline.
If you're considering using the UML at all, get this book. (not to mention it's a great software engineering text in general, teaching many fundamental patterns and principles including many from "Design Patterns" but with Java as an example language)
#appleinsider if you want to talk about it now
The effect of gravitational lensing depends on our alignment to the source. In a perfect or near perfect alignment (the case here), we see many rings and arcs. Slightly off we see arclets, followed by weak distortions. The closer to perfect alignment the better, as the magnification effect is stronger and rings, arcs, and mulitple images allow the calulation of mass and distance to both the source and the lensed matter.
You can find better explanations and animated examples by searching a bit on google.
Heh. Well if you're going to get technical, it's really OS X Server that is the 'true' decendant of Rhapsody.
Calling OS X "just NeXTSTEP with a face lift" really undermines all of the quality work that has gone into it, including Classic (the enviroment where all pre-OS X apps run), a full Java 2 implementation, and oh so much more (see Inside Mac OS X: System Overview for everything you ever wanted to know).
On the contrary, I found this piece to be very well balanced between the platforms.
And if the author were is an "obvious Mac lover" he *definitely* would not say:
as the Rhapsody OS metamorphosed into "Mac OS X" (Apple is the company), incorporating elements of *OS 9*. Having a broken link means nothing