Even if it were technically feasible, it'd just add another possible point of failure. Trying to fix a problem in Voyager would be interesting if everything had to be relayed, and even more interesting if the relay itself had problems.
If the information Voyager gathers is really that useful, they'll find a way to keep in contact.
I've never seen more confusing syntax in my life (regarding this guy's AspectJ). This is worse than bf. It would've helped if the extra tokens like '*' were explained before use, but even then, none of this seems useful to me. This might add some functionality, but at the expense of actually being able to understand the code after the fact.
The entire wildcard thing looks like it could really create some problems. Who knows what that will expand to? You certainly can't tell by glancing at the code.
If you ask me, case mods like this are relatively simple. Most everything I've seen involves taking an existing case, buying a few extra parts (fans, lights, lcds, whatever), and then just mushing it all together. Anyone with coordination and time can manage to take a bunch of pre-existing parts and put them together in such a way that they could house a computer. Granted, I have seen a few impressive cases with this approach, they aren't exactly innovative or breathtaking.
The aluminum cube mentioned a day ago, however, was a case that was breathtaking. It's one thing to take a case and strip it down to what you need (or add things like lights/fans), and a completely different thing to build the case from scratch, using your own designs.
Which brings me to the question: when the hell are we going to see mainstream cases that don't resemble current towers? Are there cases that are, by default, modded in the fashion common nowadays (status lcds, excess fans, useless-yet-pretty lights)? I'd really like to see less case mods and more completely custom cases, but I don't think that would happen until the souped-up cases people do now are no longer seen as modded cases, and are instead seen as mainstream. I'm assuming the main reason people mod cases is for the "hey look at my nifty case" factor; if everyone had nifty cases, then hopefully more people would consider building a custom case from scratch in order to distinguish themselves.
Maybe then we'll finally see those dodecahedron cases that the G5 is rumored to reside in:D
This article appears to be aimed towards those who use languages because their job requires it. I don't see Java as an evolution of C++, just as I don't see something like Objective-C being an evolution of C. I don't think _we_ care what language we use, but business people do. Most geeks use what's right for the job, whether it be it perl, C, java, or bf. As usual, the people making these decisions are higher up, with no idea of what any of it means. They want to believe that they're supporting the latest technology, and therefore are more capable at doing whatever it is they're attempting to do.
All this replacing of language A with language B is pointless. In a sense, every single language is the same. They're all either compiled or interpreted into something the computer understands, and we, most likely, don't. The main differences are syntax and semantics; The logic behind everything is largely similar. And this brings us back to the CLR mentioned in the article: is it such a bad thing? Everything eventually boils down to the same sets of instructions, so why not completely seperate language from instruction? The syntax of language A might offer advantages over language B for some task, but the task can still be completed either way. It's just a matter of taste. Only where performance absolutely matters do the choices narrow; Outside of that, what gets chosen is what the developer is comfortable with.
It says the standard 4 FreeBSD ISOS, so I'm assuming you get the following on CD (version 4.5 of course):
4.x-install.iso - 4.x ISO 9660 bootable (El Torrito) CDROM image.
4.x-disc2.iso - Live filesystem "Fix it" CD and CVS repository.
4.x-disc3.iso - Extra packages for FreeBSD 4.x
4.x-disc4.iso - Extra packages for FreeBSD 4.x
This probably includes ports, tons of documentation, and everything else that you'd expect from FreeBSD.
The resolution of the 14" iBook is 1024*768 -- the same as the resolution of the 12.1". You're paying more for a bigger laptop with no other real advantage besides not having to squint as much.
I have a Geforce, and do the same thing (just don't tell anyone:D). In games such as Half-Life and Quake2 (both in ogl mode), I keep gl_ztrick set to 0, to purposely have objects fighting over each other after a certain distance. Sometimes, you can see an enemy flickering in front of and behind a wall, allowing you to know where he's hiding. I know it's kind of like cheating, but it does add a nice performance boost, also.
"As more and more devices connect to the Net -- computers, handhelds, set-top boxes, and, eventually, toasters and microwaves -- all will need unique identifiers." woohoo! now I can finally telnet to my neighbor's toaster and burn his toast!
Slashdot Mirror
Even if it were technically feasible, it'd just add another possible point of failure. Trying to fix a problem in Voyager would be interesting if everything had to be relayed, and even more interesting if the relay itself had problems. If the information Voyager gathers is really that useful, they'll find a way to keep in contact.
The entire wildcard thing looks like it could really create some problems. Who knows what that will expand to? You certainly can't tell by glancing at the code.
(At least this isn't a homemade BFG -- I'd be really scared then)
Then again, improper use of Q-tips could prevent unwanted hearing of country music...
The aluminum cube mentioned a day ago, however, was a case that was breathtaking. It's one thing to take a case and strip it down to what you need (or add things like lights/fans), and a completely different thing to build the case from scratch, using your own designs.
Which brings me to the question: when the hell are we going to see mainstream cases that don't resemble current towers? Are there cases that are, by default, modded in the fashion common nowadays (status lcds, excess fans, useless-yet-pretty lights)? I'd really like to see less case mods and more completely custom cases, but I don't think that would happen until the souped-up cases people do now are no longer seen as modded cases, and are instead seen as mainstream. I'm assuming the main reason people mod cases is for the "hey look at my nifty case" factor; if everyone had nifty cases, then hopefully more people would consider building a custom case from scratch in order to distinguish themselves.
Maybe then we'll finally see those dodecahedron cases that the G5 is rumored to reside in :D
This article appears to be aimed towards those who use languages because their job requires it. I don't see Java as an evolution of C++, just as I don't see something like Objective-C being an evolution of C. I don't think _we_ care what language we use, but business people do. Most geeks use what's right for the job, whether it be it perl, C, java, or bf. As usual, the people making these decisions are higher up, with no idea of what any of it means. They want to believe that they're supporting the latest technology, and therefore are more capable at doing whatever it is they're attempting to do.
All this replacing of language A with language B is pointless. In a sense, every single language is the same. They're all either compiled or interpreted into something the computer understands, and we, most likely, don't. The main differences are syntax and semantics; The logic behind everything is largely similar. And this brings us back to the CLR mentioned in the article: is it such a bad thing? Everything eventually boils down to the same sets of instructions, so why not completely seperate language from instruction? The syntax of language A might offer advantages over language B for some task, but the task can still be completed either way. It's just a matter of taste. Only where performance absolutely matters do the choices narrow; Outside of that, what gets chosen is what the developer is comfortable with.
Note the date of the article: January 11, 2001 2:41 PM PT
I'm sure TeX or LaTeX with a few custom macros could simplify the process a bit, as well as provide multiple output formats.
Personally, I use LaTeX for everything now; there's tons of packages available for whatever you might happen need to do.
It says the standard 4 FreeBSD ISOS, so I'm assuming you get the following on CD (version 4.5 of course):
4.x-install.iso - 4.x ISO 9660 bootable (El Torrito) CDROM image.
4.x-disc2.iso - Live filesystem "Fix it" CD and CVS repository.
4.x-disc3.iso - Extra packages for FreeBSD 4.x
4.x-disc4.iso - Extra packages for FreeBSD 4.x
This probably includes ports, tons of documentation, and everything else that you'd expect from FreeBSD.
The resolution of the 14" iBook is 1024*768 -- the same as the resolution of the 12.1". You're paying more for a bigger laptop with no other real advantage besides not having to squint as much.
Let's just hope kids don't start using NSYNC dolls as masturbation toys now D:
Although... hmm...
*fap* *fap* *fap*
Hi! How are you? I send you this merry christmas in order to have your advice. See you later. Thanks.
If it's offline, then why include a link to the (now defunct) website?
I have a Geforce, and do the same thing (just don't tell anyone :D). In games such as Half-Life and Quake2 (both in ogl mode), I keep gl_ztrick set to 0, to purposely have objects fighting over each other after a certain distance. Sometimes, you can see an enemy flickering in front of and behind a wall, allowing you to know where he's hiding. I know it's kind of like cheating, but it does add a nice performance boost, also.
"As more and more devices connect to the Net -- computers, handhelds, set-top boxes, and, eventually, toasters and microwaves -- all will need unique identifiers."
woohoo! now I can finally telnet to my neighbor's toaster and burn his toast!