You have to leverage your existing skill-based assets to synergize with strategic technical learning opportunities so that you are empowered to become the mobile information architect of the future.
Duh.
And case mods. Make sure you have lots of case mods. Those are cool. You can be a web typist in no time!
"Don't think for a second that Microsoft hasn't put back doored software onto your computer.. that's already been documented."
What a load of crap! Internet Explorer saves your URL/Searches! STOP THE PRESSES! Internet Explorer saves cookies and history! BREAKING NEWS! OMIGOD IT'S A CONSPIRACY! Whoa, Microsoft installed "secret" files! How evil! The system attribute has only been around since, uh, DOS 1.0 or something! What a fucking load of breathless alarmism!
Anybody who has used a Microsoft OS knows about this. Why don't you talk next about "stealth dot files!", or "why Linus Torvalds doesn't want you to cat files in/dev!" or "history file records your actions!"
"The goal of OpenGL should be to provide an excellent api for realtime 3d programming, not to mimic Direct3d. If any Direct3d programmer understands 3d concepts well enough, porting to OpenGL should present no difficulty whatsoever. And vice versa."
From what I understand the non-"immediate" mode of Direct3D is much higher level than what OpenGL provides in its current form. This IS important because not all game developers have the time or brains to hand craft an entire engine technology for each game like Carmack does. They have to rely on a prebuilt and high level library that makes their job easier (and rightly so). So OpenGL has to step up to the plate and also provide some high level functionality. This also has the upside of becoming hardware independent and more easily customizing the backend to the hardware (these shading languages, etc.).
Any way that was the perception I got last time I looked at Direct3D...which was a LONG time ago:)
(and now some random text to escape the slashdot lameness filter)
Re:Balancing Issues in NS
on
Gaming Goodness
·
· Score: 3, Informative
Not sure about the rushing...the team has to be pretty well organized to all rush, and in that case, perhaps they should win.
Anyway, NS is pretty well balanced at this point. There are some funky flaws where the Fade bile bomb doesn't do as much damage as advertised, and on ns_hera, seige turrets are mysteriously ineffective...but these are minor quirks. On the whole the game is well balanced at this point. Rushing will probably always be a problem in games where you have to start up from scratch.
I can just see a flood of misinformed slashdotters aware of NS for the whole of 3 minutes flooding the NS forums demanding the game be drastically changed. I don't know why this was posted to slashdot.
Re:I remember when it was the best...
on
Altavista Renewed
·
· Score: 2
Actually, I imagine companies may be a lot more inclined to develop proprietary drivers for systems under the BSD license because it is more lax with regards to "tainting" of derived works. But hey, if FreeBSD becomes a gaming platform, I'm all for that!
I'm talking about basically preloading/caching the binary image into a memory structure which is persisted in virtual memory if necessary...not necessarily the memory they use. Since the sole purpose of binaries is to run, the question I pose is why not keep binaries, instead of in the typical filesystem, in some sort of pre-digested form in durable memory (yes it is written back out to disk, but I would naively assume that this it is still faster to load out of virtual memory than to load for the first time from disk). I think basically what I'm suggesting is pre-emptively-memory-mapped binaries. To the average user, the concept of "binary" is meaningless. They know two things: 1) they install something 2) they click an icon and the program "appears". Where the binary resides on disk or where the memory goes when they are not using the program is not their concern. I wonder if this "preloading" is a win in any way (basically it would bypass the program loader and potentially linker...i'm not sure how much of an overhead this is). In fact, a large amount of their whole disk could simply be persisted application sessions (yes, here we would actually be storing app data, not just binary image). I think you'd have to formulate a coherent argument as to why to an average user this would NOT be a good thing. The only thing I can think of is that the user might still want to organize their files in a hierarchical file-system based manner - but guess what, this *itself* could be an application (like the Finder or Windows Explorere) that is simply persisted to disk:)
What IS preventing us from getting rid of the "quit" menu item? I mean, with today's amount of RAM, I think all of the binaries of a system can fit WELL within RAM+Pagefile. So why NOT have all programs "loaded at once"? In fact...if they are all "loaded at once", why do we even need to "load" them at all? When they are installed they should just be stuck into memory or virtual memory, and the first time you run the app it will page itself back in.
Perhaps it may not be entirely realistic at this point, but we should be asking these "why?" questions.
And not only that...it can assassinate US citizens. "Administration officials, intelligence operatives and military analysts...praised the CIA strikes as an innovative way to get the job done." You know that whole "pre-emptive strike" debate? Well it's over now. Everybody grab their sled because we're in for a nice ride down this slippery slope from moral highground! Weeeee!
Well, the computer is really there to do the users work, not vice versa.
From a user perspective, FTP, SMTP, POP/IMAP are all basically the same: how to pass a message from one person to another. FTP deals with messages called "files" between machines. Email deals with messages call "mail" between users.
Who's to say this can't be generalized into a generic message queue architecture over which both email and file transfers can occur? All you need is some generic headers a binary chunk. After that, who the hell cares if it is email or a file or anything else. Come to think of it, a generic message passing architecture like this could help distribute load, because just like email, where your message is really handed down through several servers, the ftp file could be "handed down" instead of passing in a direct client-server manner, hammering the FTP source.
Yeah, but without doing serious bug tracking yourself, it is sometimes hard to figure out which of any number of piece the bug belongs to (distro? package manager? C libraries? actual application? some dependency of the application?... etc.)
I can see how they might be concerned if a customer uses their product for a purpose they explicitly do not recommend. I'm sure they envision the headline: "Sub-par Dell server system ruins small business!"
Slashdot Mirror
You have to leverage your existing skill-based assets to synergize with strategic technical learning opportunities so that you are empowered to become the mobile information architect of the future.
Duh.
And case mods. Make sure you have lots of case mods. Those are cool. You can be a web typist in no time!
"Don't think for a second that Microsoft hasn't put back doored software onto your computer.. that's already been documented."
/dev!" or "history file records your actions!"
What a load of crap! Internet Explorer saves your URL/Searches! STOP THE PRESSES! Internet Explorer saves cookies and history! BREAKING NEWS! OMIGOD IT'S A CONSPIRACY! Whoa, Microsoft installed "secret" files! How evil! The system attribute has only been around since, uh, DOS 1.0 or something! What a fucking load of breathless alarmism!
Anybody who has used a Microsoft OS knows about this. Why don't you talk next about "stealth dot files!", or "why Linus Torvalds doesn't want you to cat files in
"The goal of OpenGL should be to provide an excellent api for realtime 3d programming, not to mimic Direct3d. If any Direct3d programmer understands 3d concepts well enough, porting to OpenGL should present no difficulty whatsoever. And vice versa."
:)
From what I understand the non-"immediate" mode of Direct3D is much higher level than what OpenGL provides in its current form. This IS important because not all game developers have the time or brains to hand craft an entire engine technology for each game like Carmack does. They have to rely on a prebuilt and high level library that makes their job easier (and rightly so). So OpenGL has to step up to the plate and also provide some high level functionality. This also has the upside of becoming hardware independent and more easily customizing the backend to the hardware (these shading languages, etc.).
Any way that was the perception I got last time I looked at Direct3D...which was a LONG time ago
"web typists"
classic. Does Sam's publish a "Learn Web Typing in 24 Hours for Fun and Profit!!"
Not everybody looks at the seperate sections.
I'm not even sure why they exist...is there a preference to put all section news in the main news?
...You want free advice?
Ugh...this might be ok for mature and stable software...but for new projects auditing like this would just kill them.
WINDMILLS DO NOT WORK THAT WAY!!
GOOD NIGHT!
- MORBO
(and now some random text to escape the slashdot lameness filter)
Not sure about the rushing...the team has to be pretty well organized to all rush, and in that case, perhaps they should win.
Anyway, NS is pretty well balanced at this point. There are some funky flaws where the Fade bile bomb doesn't do as much damage as advertised, and on ns_hera, seige turrets are mysteriously ineffective...but these are minor quirks. On the whole the game is well balanced at this point. Rushing will probably always be a problem in games where you have to start up from scratch.
I can just see a flood of misinformed slashdotters aware of NS for the whole of 3 minutes flooding the NS forums demanding the game be drastically changed. I don't know why this was posted to slashdot.
"look good and go down easy"
No wonder so many geeks are switching...
Right, so now governments have:
1) new non-lethal weapons
2) a "war on terrorism" that can be used to crack down on any dissent groups
What happens when non-voilent protest is impossible?
1) commoditize your hardware!
2) commoditize your software!
3) ???
4) $$$!
Actually, I imagine companies may be a lot more inclined to develop proprietary drivers for systems under the BSD license because it is more lax with regards to "tainting" of derived works. But hey, if FreeBSD becomes a gaming platform, I'm all for that!
I'm talking about basically preloading/caching the binary image into a memory structure which is persisted in virtual memory if necessary...not necessarily the memory they use. Since the sole purpose of binaries is to run, the question I pose is why not keep binaries, instead of in the typical filesystem, in some sort of pre-digested form in durable memory (yes it is written back out to disk, but I would naively assume that this it is still faster to load out of virtual memory than to load for the first time from disk). I think basically what I'm suggesting is pre-emptively-memory-mapped binaries. To the average user, the concept of "binary" is meaningless. They know two things: 1) they install something 2) they click an icon and the program "appears". Where the binary resides on disk or where the memory goes when they are not using the program is not their concern. I wonder if this "preloading" is a win in any way (basically it would bypass the program loader and potentially linker...i'm not sure how much of an overhead this is). In fact, a large amount of their whole disk could simply be persisted application sessions (yes, here we would actually be storing app data, not just binary image). I think you'd have to formulate a coherent argument as to why to an average user this would NOT be a good thing. The only thing I can think of is that the user might still want to organize their files in a hierarchical file-system based manner - but guess what, this *itself* could be an application (like the Finder or Windows Explorere) that is simply persisted to disk :)
What IS preventing us from getting rid of the "quit" menu item? I mean, with today's amount of RAM, I think all of the binaries of a system can fit WELL within RAM+Pagefile. So why NOT have all programs "loaded at once"? In fact...if they are all "loaded at once", why do we even need to "load" them at all? When they are installed they should just be stuck into memory or virtual memory, and the first time you run the app it will page itself back in.
Perhaps it may not be entirely realistic at this point, but we should be asking these "why?" questions.
"swift robber" or something
plus, has that dinosaur theme
"the CIA can assasinate with impunity"
And not only that...it can assassinate US citizens. "Administration officials, intelligence operatives and military analysts...praised the CIA strikes as an innovative way to get the job done." You know that whole "pre-emptive strike" debate? Well it's over now. Everybody grab their sled because we're in for a nice ride down this slippery slope from moral highground! Weeeee!
My favorit
My favorite bug is wh
My favorite bug is when mail cras
My favorite bug is when mail crashes whenever I tr
My favorite bug is when mail crashes whenever I try to sen
My favorite bug is when mail crashes whenever I try to send a message
Is there any speed increase for the second run of rm -r / ?
...isn't it difficult to code with tentacles?
Well, the computer is really there to do the users work, not vice versa.
From a user perspective, FTP, SMTP, POP/IMAP are all basically the same: how to pass a message from one person to another. FTP deals with messages called "files" between machines. Email deals with messages call "mail" between users.
Who's to say this can't be generalized into a generic message queue architecture over which both email and file transfers can occur? All you need is some generic headers a binary chunk. After that, who the hell cares if it is email or a file or anything else. Come to think of it, a generic message passing architecture like this could help distribute load, because just like email, where your message is really handed down through several servers, the ftp file could be "handed down" instead of passing in a direct client-server manner, hammering the FTP source.
And for the record Scully is NOT hot.
Yeah, but without doing serious bug tracking yourself, it is sometimes hard to figure out which of any number of piece the bug belongs to (distro? package manager? C libraries? actual application? some dependency of the application? ... etc.)
...or just asking?
I can see how they might be concerned if a customer uses their product for a purpose they explicitly do not recommend. I'm sure they envision the headline: "Sub-par Dell server system ruins small business!"
Demanding is one thing, asking is another.
Karma: Profligate. (go ahead and troll)