Silly Burrito writes "Think Secret is reporting that Tiger will be out in April with an event on April 1st and it should be out in stores by April 15th. If this is true,
I can finally get both the Mini and a new Powerbook, as I've been waiting for Tiger to be released before I do so. Let's just hope that this isn't a bad April Fools Joke!
A inquiry directly related to the submission is quite on-topic.
Doesn't your code also skip the first element? (Also, it's less readable than the parent given the example is C++, and that style is a very common idiom)
It's interesting because Intel processors are the future of smart space heaters. Every other processor group seems to be aiming at decreasing power usage, while Intel just throws more at it. I suppose they're running out of ideas.
Nano-ITX motherboards are going to be fun. I'm planning on taking a Nano-ITX board and one of Toshiba's 1.8" hard drives and replacing the internals of a digital clock, complete with a new front display. Perfectly discrete server for any room.
And F-Zero has just that. From the GameSpy review:
But is the game too difficult for most? That's pretty debatable. I personally found the difficulty curve pretty harsh -- particularly on the harder difficulty settings -- but F-Zero has always been about the overall challenge.
I don't understand this reviewer at all. When the difficulty is set higher, the game actually gets harder! What a concept! This amazing technology should be implemented in as many games as possible.
I think gamers are just getting used to games that are nothing more than busy work and no challenge. Obviously, a few hours of NetHack could solve a lot of problems.
I'm in Rochester, which is close enough. The digital network is flaky. I haven't been able to place outbound calls, but I've been getting some inbound (which happen to ring, and lose the connection as I'm answering). I managed to use the analog network for outbound at least. It's all a bit screwy, though.
This updates a system framework, which is likely in use by multiple, running, applications. The safest way to ensure everything is operating as it should is to require a restart. Had this been an update of something else, like a user-level application or daemon, then the restart would not have been required.
You have to remember that this is an operating system for the masses and their desktops. I'm sure this update could've not required a restart, but what if something went wrong? Would your grandmother know how to make sure the current version of a shared library is loaded for her applications?
I was also a beta tester of this game. Personally, I think it's all a hoax. There no way a game could have a permanent physical effect on someTHIRTY-FOUR! FIFTY-TWO! DOWN! SET! HUT!bfhgda;lbkaj;
Some of the screenshots of course don't seem different at all, so I'm not sure why they posted them (the main desktop screenshot in particular, although a lot of it is "censored")...
You move your mouse to a corner of the screen, which handles some type of window.
After some delay, all windows not of that type are hidden. Windows of that type are zoomed out (shrunk) until all fit on the desktop.
Click on a window to zoom back onto it.
It's really an elegant solution to window clutter. It's either this or virtual desktops, and Apple probably would dislike virtual desktops due to the "where the hell did my windows go" factor. With Quartz, all the zooming should give the user usable visual feedback as to what's going on.
I've gathered some data and made graphs of Chimera versus Safari when dealing with tabs and windows. Memory usage and cumulative CPU time are measured, and compared.
'Camino' doesn't really roll off the tongue that well. I mean, what is it (other than a city in California). It sounds like someone rehired the pidgeons that were previously employed by Google in order to generate rankings. I've heard other candidates for the name were 'Mamioei', 'Piekay', and 'Yorekrasi'. 'Tokaak' was a close runner-up.
Well, 0.5 is full implementation of the Reality Distortion Field, while 0.7 is implementation of OpenGL 2.0 acceleration. (0.6 is where they fix the RDF before Steve throws a camera and/or 12" PowerBook at somebody.)
0.8 is scheduled to include complete integration of X11 applications with OS X, moving the X11 server running alongside Quartz, while 0.9 is more bug fixes.
Around 1.0, X11 gets merged into Emacs, which then becomes the premiere operating system in 2004, slowly phasing out OS X as we know it today. In other words, they will have reinvented Windows.
I'll admit, I don't know much about the details of shared library loading and reloading; That said, I doubt it's anywhere near as effective as Erlang's hot-swapping of running code.
For one, Erlang handles code replacement in the runtime -- no dependence on the underlying OS implementation. What happens when you try to reload a shared library with the same symbols? What if module A is in the middle of module B's routines, while you reload B's shared library? What if you just changed a data structure in a few modules and need a system-wide reload? I sure wouldn't want to have to handle synchronising that in C or C++.
The mechanisms to handle these situations are already present in Erlang; There's no need to reinvent the wheel here.
Hmmm.. I like the idea behind the "supervision tree". Why is that not possible to implement in other languages?
It may or may not be possible to implement, but chances are something like it isn't distributed with the language. The supervisor structure distributed with Erlang is well-tested, robust, and quite usable.
Is that similar to the implementation of concurrency in Ada?
I'm not familiar with concurrency in Ada. In Erlang, processes are extremely lightweight and communicate via message passing. The processes themselves are done in the runtime, so there are no limits imposed by the OS (besides system resources, of course). With a shared heap, even the memory requirements are extremely low (compared to Java or C, for instance).
Well, besides the obvious concurrency advantage (need 200000 processes? no problem!), there's things like hot swapping of code, behaviors for common design patterns (servers, event handling, supervisors), bundled database written in Erlang, and other things like that.
Writing a robust program in Erlang is extremely simple by using supervisors and following design principles like these. For example, my Erlang IRC bot is near impossible to completely crash. If the server connection dies, there's a supervisor that'll keep trying to get it back up; All the while the other processes of the bot have no idea there's no connection -- they don't need to know. If I've written a faulty module and the code misbehaves, only that single process is affected. If possible, a process that has crashed will be automatically restarted and operations resume as if nothing had happened.
Hot-swapping of code allows me to debug the bot without restarting it. If I discover a bug in the irc parsing routines, I simply fix it in the code, recompile, and reload the offending module -- while the bot is running. The new code replaces the old, and it just works.
There's plenty more, but I would suggest checking Erlang's website and reading the FAQ and examples. Oh, and here's a nifty benchmark:)
Yes! Of course it's necessary! After the four hours of Pre-Game, we can finally concentrate on the actual game. But not before. If there were no pre-game, there might as well be no game! What good is the game if you haven't been practicing wasting time before you can start wasting time for real? That's like driving without a license!
Now, after you've been practicing wasting time and calling unneccessary bets on the outcome of the game, you can actually watch it! Of course, the actual game is redundant, mindless, and about as fun to watch as drying paint, but that's what it means to be an American!
Then after you've gained 10 kg due to overeating (and lost 10% of brain mass due to watching the game), you can watch the Post-Game Wrap-up! This is what you've waited your entire life for! But of course, you first must see what dazed and confused person has just won Publishers Clearings House! Aren't you glad for them?!
The mystical Post-Game Wrap-up is where you get to watch the game all over again! Not the entire game, mind you, but all of the exciting parts where things happen! Like the time where some guy drops the ball, and then someone else grabs it! It's incredibly unpredictable, even the fifth time around.
Finally, after the Post-Game Wrap-up, you can relive it all next morning on the local news! What a deal!
Safari does use KHTML, but it does not use QT in the manner that you suggest. Safari does not use QT for the GUI. Because of QT's modular design, native Cocoa widgets were easily used in place of whatever KHTML previously used to render widgets on other platforms.
Actually, it appears Microsoft has their own version of the lameness filter. If you first enable the Safari Debug menu with defaults write com.apple.Safari IncludeDebugMenu 1 in Terminal.app, and then change the User Agent to MSIE 6.0, Hotmail will work fine.
Safari can definately handle Hotmail, but the UA checking is holding it back.
I'm a researcher in the neuromechanomy field, and I have found similar results in my studies. While I am not an expect in neuronomy, my research indicates that people get irritated when you place large pink sunglasses on them. I have found that requiring them to wear pink shoes also leads to irritability. Therefore, I have concluded that the color pink should be banned from all public places, much like smoking is beginning to be.
As a side-note, my neuromechanomy studies have led me to a potentially disastrous discovery: gravity is the leading cause of death. Preliminary studies involving rodents support my theory -- many died within minutes of being placed in a centrifuge. Therefore, I propose that mankind be fitted with antigravity suits, so that life will not be hindered by the harmful effects of gravity. It's amazing how long the human race has survived with a daily, constant exposure of this magnitude.
After an hour of strenuous testing, I have some hard data to back up sockit2me9000's informal benchmark. First a clean install of Mac OS X Jaguar 10.2 is performed on an 800MHz PowerBook G4 with 512MB of RAM. Boot time and iCal launch time is measured four times. For each trial, the system is booted cleanly. No userland applications are running at the time of iCal Bounce Measurement (ICBM).
Finally, the 10.2.3 update is installed, and the above measurements are repeated.
It is observed that the average boot time for 10.2 is 27.137 seconds, with an average ICBM of 1.932 bounces. On the other hand, 10.2.3 yields an average boot time of 23.948 seconds, with an average of 1.317 bounces. Clearly, 10.2.3 is faster in all cases.
This intensive analysis has led me to the only conclusion that may be derived from these results: there are no plastics that require waxing for the optimal frisbee density. Further analysis may be required in order to determine the optimal frisbee color, however.
Slashdot Mirror
Doesn't your code also skip the first element? (Also, it's less readable than the parent given the example is C++, and that style is a very common idiom)
It's interesting because Intel processors are the future of smart space heaters. Every other processor group seems to be aiming at decreasing power usage, while Intel just throws more at it. I suppose they're running out of ideas.
Nano-ITX motherboards are going to be fun. I'm planning on taking a Nano-ITX board and one of Toshiba's 1.8" hard drives and replacing the internals of a digital clock, complete with a new front display. Perfectly discrete server for any room.
I don't understand this reviewer at all. When the difficulty is set higher, the game actually gets harder! What a concept! This amazing technology should be implemented in as many games as possible.
I think gamers are just getting used to games that are nothing more than busy work and no challenge. Obviously, a few hours of NetHack could solve a lot of problems.
So we can give the barcodes barcodes, and the barcode's barcode a barcode? What about a barcode for the barcode's barcode's barcode?
I'm in Rochester, which is close enough. The digital network is flaky. I haven't been able to place outbound calls, but I've been getting some inbound (which happen to ring, and lose the connection as I'm answering). I managed to use the analog network for outbound at least. It's all a bit screwy, though.
This updates a system framework, which is likely in use by multiple, running, applications. The safest way to ensure everything is operating as it should is to require a restart. Had this been an update of something else, like a user-level application or daemon, then the restart would not have been required.
You have to remember that this is an operating system for the masses and their desktops. I'm sure this update could've not required a restart, but what if something went wrong? Would your grandmother know how to make sure the current version of a shared library is loaded for her applications?
I was also a beta tester of this game. Personally, I think it's all a hoax. There no way a game could have a permanent physical effect on someTHIRTY-FOUR! FIFTY-TWO! DOWN! SET! HUT!bfhgda;lbkaj;
It's really an elegant solution to window clutter. It's either this or virtual desktops, and Apple probably would dislike virtual desktops due to the "where the hell did my windows go" factor. With Quartz, all the zooming should give the user usable visual feedback as to what's going on.
Have a looksie.
'Camino' doesn't really roll off the tongue that well. I mean, what is it (other than a city in California). It sounds like someone rehired the pidgeons that were previously employed by Google in order to generate rankings. I've heard other candidates for the name were 'Mamioei', 'Piekay', and 'Yorekrasi'. 'Tokaak' was a close runner-up.
Well, 0.5 is full implementation of the Reality Distortion Field, while 0.7 is implementation of OpenGL 2.0 acceleration. (0.6 is where they fix the RDF before Steve throws a camera and/or 12" PowerBook at somebody.)
0.8 is scheduled to include complete integration of X11 applications with OS X, moving the X11 server running alongside Quartz, while 0.9 is more bug fixes.
Around 1.0, X11 gets merged into Emacs, which then becomes the premiere operating system in 2004, slowly phasing out OS X as we know it today. In other words, they will have reinvented Windows.
Sure you can, and I can go rewrite the Linux kernel in Haskell. There just aren't any other languages with these facilities.
For one, Erlang handles code replacement in the runtime -- no dependence on the underlying OS implementation. What happens when you try to reload a shared library with the same symbols? What if module A is in the middle of module B's routines, while you reload B's shared library? What if you just changed a data structure in a few modules and need a system-wide reload? I sure wouldn't want to have to handle synchronising that in C or C++.
The mechanisms to handle these situations are already present in Erlang; There's no need to reinvent the wheel here.
Writing a robust program in Erlang is extremely simple by using supervisors and following design principles like these. For example, my Erlang IRC bot is near impossible to completely crash. If the server connection dies, there's a supervisor that'll keep trying to get it back up; All the while the other processes of the bot have no idea there's no connection -- they don't need to know. If I've written a faulty module and the code misbehaves, only that single process is affected. If possible, a process that has crashed will be automatically restarted and operations resume as if nothing had happened.
Hot-swapping of code allows me to debug the bot without restarting it. If I discover a bug in the irc parsing routines, I simply fix it in the code, recompile, and reload the offending module -- while the bot is running. The new code replaces the old, and it just works.
There's plenty more, but I would suggest checking Erlang's website and reading the FAQ and examples. Oh, and here's a nifty benchmark :)
Now, after you've been practicing wasting time and calling unneccessary bets on the outcome of the game, you can actually watch it! Of course, the actual game is redundant, mindless, and about as fun to watch as drying paint, but that's what it means to be an American!
Then after you've gained 10 kg due to overeating (and lost 10% of brain mass due to watching the game), you can watch the Post-Game Wrap-up! This is what you've waited your entire life for! But of course, you first must see what dazed and confused person has just won Publishers Clearings House! Aren't you glad for them?! The mystical Post-Game Wrap-up is where you get to watch the game all over again! Not the entire game, mind you, but all of the exciting parts where things happen! Like the time where some guy drops the ball, and then someone else grabs it! It's incredibly unpredictable, even the fifth time around.
Finally, after the Post-Game Wrap-up, you can relive it all next morning on the local news! What a deal!
Safari does use KHTML, but it does not use QT in the manner that you suggest. Safari does not use QT for the GUI. Because of QT's modular design, native Cocoa widgets were easily used in place of whatever KHTML previously used to render widgets on other platforms.
Safari can definately handle Hotmail, but the UA checking is holding it back.
I'm a researcher in the neuromechanomy field, and I have found similar results in my studies. While I am not an expect in neuronomy, my research indicates that people get irritated when you place large pink sunglasses on them. I have found that requiring them to wear pink shoes also leads to irritability. Therefore, I have concluded that the color pink should be banned from all public places, much like smoking is beginning to be.
As a side-note, my neuromechanomy studies have led me to a potentially disastrous discovery: gravity is the leading cause of death. Preliminary studies involving rodents support my theory -- many died within minutes of being placed in a centrifuge. Therefore, I propose that mankind be fitted with antigravity suits, so that life will not be hindered by the harmful effects of gravity. It's amazing how long the human race has survived with a daily, constant exposure of this magnitude.
After an hour of strenuous testing, I have some hard data to back up sockit2me9000's informal benchmark. First a clean install of Mac OS X Jaguar 10.2 is performed on an 800MHz PowerBook G4 with 512MB of RAM. Boot time and iCal launch time is measured four times. For each trial, the system is booted cleanly. No userland applications are running at the time of iCal Bounce Measurement (ICBM).
Finally, the 10.2.3 update is installed, and the above measurements are repeated.
Data: (10.2)
Trial 1:
Boot time: 28.452 seconds
ICBM: 1.989 bounces
Trial 2:
Boot time: 26.985 seconds
ICBM: 1.687 bounces
Trial 3:
Boot time: 27.189 seconds
ICBM: 2.176 bounces
Trial 4:
Boot time: 25.923 seconds
ICBM: 1.878 bounces
Data: (10.2.3)
Trial 1:
Boot time: 22.785 seconds
ICBM: 1.373 bounces
Trial 2:
Boot time: 24.873 seconds
ICBM: 1.284 bounces
Trial 3:
Boot time: 22.291 seconds
ICBM: 1.262 bounces
Trial 4:
Boot time: 25.843 seconds
ICBM: 1.348 bounces
It is observed that the average boot time for 10.2 is 27.137 seconds, with an average ICBM of 1.932 bounces. On the other hand, 10.2.3 yields an average boot time of 23.948 seconds, with an average of 1.317 bounces. Clearly, 10.2.3 is faster in all cases.
This intensive analysis has led me to the only conclusion that may be derived from these results: there are no plastics that require waxing for the optimal frisbee density. Further analysis may be required in order to determine the optimal frisbee color, however.