Well, they need some hardware to run Powerpoint on.
"A PowerPoint Ranger is a military member who relies heavily on presentation software to the point of excess. Some junior officers spend the majority of their time preparing PowerPoint slides.[10] Because of its usefulness for presenting mission briefings, it has become part of the culture of the military,[9][11] but is regarded as a poor decision-making tool.[12] As a result some generals, such as Brigadier-General Herbert McMaster, have banned the use of PowerPoint in their operations.[10] In September 2010, Colonel Lawrence Sellin was fired from his post at the ISAF for publishing a piece critical of the over-dependence of military staffs on the presentation method and bloated bureaucracy.[13]
According to Jim Nelson, who served as a civilian translator with the Russian and American peacekeepers in Bosnia in 1996, one of the Russians said, "If we ever had a war, while you are working on your PowerPoint, we would be killing you.""
Well, I haven't used Oz in a while, but my first exposure consisted some conference slides, and it was quite overwhelming as it involved a CSP without even properly clarify the syntax. And in Prolog CSP frameworks "#" means constraint equality. (CSP got "mainstream" with Prolog first.)
On the other hand I agree that Emacs feels ass-backwards.
"Another annoying thing is that Oz only runs in 32 bit so far."
When I tried it around 1.5 year ago, the database libraries were quite buggy (they borrowed them from tcl IIRC). So I don't think it can be considered a production ready language.
If I remember correctly, "#" is for constraint statisfaction problems (delayed goal), and I think that operator shouldn't be taught to an Oz newbie, as Constraint Logic Programming is a paradigm onto itself (and not just paradigm, as in thinking pattern, but it involves quite a lot of complex algorithm that run in the background (demons), and non-sequantial execution).
Last time I installed Oz, it came with Emacs bundled by default.
I think Scala is mostly used by Lambda-the-ultimate fabboys, who just fall in love with everything if it has anonymous functions and continuations, and don't really give a shit about productivity, developer training, good documentation, good tool support or performance.
I bought the MIT book about Oz, and it was really fun. (Read only 3 chapters) However I can't imagine learning it from PowerPoint slides. (Especially if you got shown a constraint statisfaction problem right-away.) By the way it seems less weird for me than Haskell or Common Lisp. * (I'm just fiddled with them, don't know them at any usable level.)
I think when you understand the canonic representation of program structures, and how the flow of control goes, it does seem quite sensible.
On the other hand when I tried Scala, the type system always got in the way. The guys in the forum were really helpful, but they referred to things that wasn't in the documentation/ was hard to find in the documentation. (It was pretty badly organized.) It was too much time to statisfy the compiler, and I didn't see the gain in code roboustness. I started to really appreciate Java's half-baked generics. (Where usually you don't actually need to use generics due to type erasure, but if you do, the IDE will offer better auto-completition.)
Your instruments won't work any worse, as the frequancy will not be less precise. The only change is that extra cycles won't be compensated for at the end of the day. And that's only intresting for clocks.
Try Tremolous. It's an opensource RTS/FPS blend, and installing a dedicated server doesn't seem hard. (Although there are plenty hosted by others.) It's got a pretty good community. It's the only FPS I played in the last 2 years, and I don't miss the canned railshooter experience. (I usually play the 1.2 gpp beta on the official servers, that's where most of the folks are.)
Also, there's a quite a bit of emphasis on teamplay. Lone wolfs don't win the match.
"Header inclusion is really a very simple affair - all the #include directive does is paste the contents of the file in place. Everything else falls out of that. Forward declarations may seem archaic, but they allow you to be explicit about depending on skeletal declarations rather than full definitions (although this can admittedly get kludgy in some circumstances, e.g. typedefs), and they allow you to have a sort of cheat sheet of declarations that is separate from the implementation."
What I meant, when to extern and when not to. I once struggled to convert extern functions to class methods. I can't cite the example, but it was plenty confusing for me.
And besides the language itself, the another problem is the standard library: it has so few things. Not even a proper String class that abstracts away character encoding, no standard way to create GUIs, parse XMLs. I had to do some small project in c++ recently, and I had to hunt for opensource libraries that do these, but unfortunately, the XML library used UTF-8, the GUI used UTF-16, and the free fonts I have found didn't support latin2 characters. Just finding an iconv, that runs on windows took 3 hours.
Slashdot Mirror
"Oh that's how we think in the UNITED STATES, so obviously that's the dumbest possible mindset."
He's the living proof.
Look on the good side: you get dog-poo free cities.
Advocacy Group Decries PETA's Inhumane Treatment Of Women
http://www.youtube.com/watch?v=q2z2lTUR5Ao
" 'If we considered them living beings, we would deal with them differently.'"
Plants are living things too. Should we ban the sale of them.
On other news, San Francisco pet owner ate his cat.
"because other companies felt the need to release "new major versions" to be perceived by the clueless public as releasing an update as often."
And they are right. Here in Slashdot a lot of people used to say that Java is dead and Ruby/Python is the way of the future.
Well, they need some hardware to run Powerpoint on.
"A PowerPoint Ranger is a military member who relies heavily on presentation software to the point of excess. Some junior officers spend the majority of their time preparing PowerPoint slides.[10] Because of its usefulness for presenting mission briefings, it has become part of the culture of the military,[9][11] but is regarded as a poor decision-making tool.[12] As a result some generals, such as Brigadier-General Herbert McMaster, have banned the use of PowerPoint in their operations.[10] In September 2010, Colonel Lawrence Sellin was fired from his post at the ISAF for publishing a piece critical of the over-dependence of military staffs on the presentation method and bloated bureaucracy.[13]
According to Jim Nelson, who served as a civilian translator with the Russian and American peacekeepers in Bosnia in 1996, one of the Russians said, "If we ever had a war, while you are working on your PowerPoint, we would be killing you.""
http://en.wikipedia.org/wiki/Death_by_PowerPoint
http://voristrip.tumblr.com/post/230887512/death-by-powerpoint
Just kill the jews and gypsies and everything will be fine. Also, eat less meat.
Adolf
Well, I haven't used Oz in a while, but my first exposure consisted some conference slides, and it was quite overwhelming as it involved a CSP without even properly clarify the syntax. And in Prolog CSP frameworks "#" means constraint equality. (CSP got "mainstream" with Prolog first.)
On the other hand I agree that Emacs feels ass-backwards.
"Another annoying thing is that Oz only runs in 32 bit so far."
When I tried it around 1.5 year ago, the database libraries were quite buggy (they borrowed them from tcl IIRC). So I don't think it can be considered a production ready language.
If I remember correctly, "#" is for constraint statisfaction problems (delayed goal), and I think that operator shouldn't be taught to an Oz newbie, as Constraint Logic Programming is a paradigm onto itself (and not just paradigm, as in thinking pattern, but it involves quite a lot of complex algorithm that run in the background (demons), and non-sequantial execution).
Last time I installed Oz, it came with Emacs bundled by default.
I mean this book:
http://www.info.ucl.ac.be/~pvr/book.html
Now abolish software patents, because it's mathematics applied to a different medium. (Other than the human mind.)
I think Scala is mostly used by Lambda-the-ultimate fabboys, who just fall in love with everything if it has anonymous functions and continuations, and don't really give a shit about productivity, developer training, good documentation, good tool support or performance.
I bought the MIT book about Oz, and it was really fun. (Read only 3 chapters) However I can't imagine learning it from PowerPoint slides. (Especially if you got shown a constraint statisfaction problem right-away.) By the way it seems less weird for me than Haskell or Common Lisp. * (I'm just fiddled with them, don't know them at any usable level.)
I think when you understand the canonic representation of program structures, and how the flow of control goes, it does seem quite sensible.
On the other hand when I tried Scala, the type system always got in the way. The guys in the forum were really helpful, but they referred to things that wasn't in the documentation/ was hard to find in the documentation. (It was pretty badly organized.) It was too much time to statisfy the compiler, and I didn't see the gain in code roboustness. I started to really appreciate Java's half-baked generics. (Where usually you don't actually need to use generics due to type erasure, but if you do, the IDE will offer better auto-completition.)
You're right. Now turn off your computer!
if I asked her to make me a sammich.
Or run Folding@Home and help cure cancer.
Your instruments won't work any worse, as the frequancy will not be less precise. The only change is that extra cycles won't be compensated for at the end of the day. And that's only intresting for clocks.
"tl;dr version: big, useless clock."
But pyramids are so 4000 BC.
"I actually had high hopes for Google Health"
Don't worry! Facebook has created a better one! You can also friend the prostitute you've got the STDs from.
Whoosh, English is his Achilles heal.
Try Tremolous. It's an opensource RTS/FPS blend, and installing a dedicated server doesn't seem hard. (Although there are plenty hosted by others.) It's got a pretty good community. It's the only FPS I played in the last 2 years, and I don't miss the canned railshooter experience. (I usually play the 1.2 gpp beta on the official servers, that's where most of the folks are.)
Also, there's a quite a bit of emphasis on teamplay. Lone wolfs don't win the match.
"Header inclusion is really a very simple affair - all the #include directive does is paste the contents of the file in place. Everything else falls out of that. Forward declarations may seem archaic, but they allow you to be explicit about depending on skeletal declarations rather than full definitions (although this can admittedly get kludgy in some circumstances, e.g. typedefs), and they allow you to have a sort of cheat sheet of declarations that is separate from the implementation."
What I meant, when to extern and when not to. I once struggled to convert extern functions to class methods. I can't cite the example, but it was plenty confusing for me.
And besides the language itself, the another problem is the standard library: it has so few things. Not even a proper String class that abstracts away character encoding, no standard way to create GUIs, parse XMLs. I had to do some small project in c++ recently, and I had to hunt for opensource libraries that do these, but unfortunately, the XML library used UTF-8, the GUI used UTF-16, and the free fonts I have found didn't support latin2 characters. Just finding an iconv, that runs on windows took 3 hours.
"University level computer science is about Design, not Implementation."
No, that's Software Engineering. No let the flamewar begin.
Oh, boy, you're so wrong.