Carbon dioxide is heavier than air. Right. Except did someone forget about gas laws from chemistry... you know, DIFFUSION? If what they claimed were true, we'd all be choking and drowning in a carbon-dioxide, sulphur-dioxide, water-vapor-laden miasma. Fortunately for us, all those gases are disperesed evenly throughout the atmosphere, thus allowing us to BREATH, dumbass.
If they can't even get that part right, what makes you think the rest of it has any validity. Oh wait, it doesn't! It's full of conjecture and generalizations of the kinds worse than you claim climatologists make! Emporer has no clothes indeed.
How is a fill-in-the-blank-free diet homeopathy?
on
Bad Science Awards
·
· Score: 1
There is a bit of proof for macro too...
on
Bad Science Awards
·
· Score: 1
... I can't find the fucking reference.
Anyway, its about some kind of squirrel or rodent in Australia, and that the specices was originally one (from mito-DNA evidence), but now one population has differently shaped tails, different feeding patterns, and they can no longer interbreed. They are consider seperate species in their genus. The populations got seperated during a food shortage across some gorge, which widened through erosion over the course of like a few thousand years, and now they can't access each other.
Maybe it isn't Australia, and that's why I can't find the reference. Arrgh.
Right... and the question is... for what purpose.
on
Bad Science Awards
·
· Score: 1
Seriously. Seems to me that kind of thinking is what a sore loser crybaby would come up with...
Hey, if you want intelligent creators:
on
Bad Science Awards
·
· Score: 1
You'll need a whole HELL of a lot of class time:
1) Christian 'Genesis' / Sumerian creation myth 2) Chinese creation myth 3) Norse creation myth 4) Egyptian creation myth 5) Simulation ala 13th floor / eXistenZ 6) Simulation ala Matrix or Metamorphasis of the P I 7) Benevolant aliens 8) Aliens using us for food or labor 9) Our own species which used very advanced technology to ensure it's own existence by going back in time...
I could go own. Lots of well thought out theories. Oh wait, you just meant parts of #1. Well, that's not very fair is it?
Evolution is the best answer we have that doesn't make a whole lot of assumptions or is based on verbal lore. I think we should focus most of our class time on that. When something else comes up that seems to be a better explanation that is both testable, demonstratable, and useful, I'd gladly replace evolution.
It's not managing the tape library that makes Veritas special. It's being able to keep point-in-time images of running machines handy, and not having to worry about managing duplicity. That's the _hard_ part. I mean, volume management is great, but you only have to worry about that on the server. Vertias's multitudes of client agents is magical.
bittorrent could use an API wherein you can suggest it to fetch certain pieces, or determine whether pieces have been verified yet. That's half the battle (aside from figuring out how to effectively USE the API)
Try creating an inventory tracking system, PERIOD. Lots of stuff you use has barcodes. You could scan things "in" and "out" to try to keep track of stuff. So you scan it in when you take it out of your bag from the store, and scan it "out" when you open the package or use somethin' up, or maybe loan it someone.
Of course, it lacks wifi, so you'd have to probably code an app that queues up the operations (scan-in, then out, then in again should be collapsed to one scan-in)
Unfortunately, you're probably better off maintaining your own database of info for each product. This isn't such a big deal, cuz you're going to want to attach your own notes and stuff to each item.
javascript's type resolution is definition based this means the execution environment determines the behavior of namespace/module resolution issues (by dynamically loading code from external files or whatever as required with some intrinsic)
This way you can break your project into independant modules, implement test harnesses, etc.
javascript allows you to scope and prototype objects and defintions. You provide namespace scoping by using nested definitions. And prototypes (i.e. classes, not clonable objects) are created using the prototype keyword. Also check this out: http://www.crockford.com/javascript/private. html
The tools are there. Unfortunately, you won't find many guides anywhere about how to use these properties to write maintainable code or work it in a collaborative environment. Discussions about closures and anonymous functions is also few and far between. But you will find endless discussion about detecting the DOM of various web-browsers (sigh).
I'm 100% serious. All this Copeland guy does is plug his rubyforge site or InfoEther.
Do you actually do any work on Ruby or do you just spend your time trolling message boards and mailing lists?
PS, I know where you live and work. Ever been to the theatre at Worldgate? I bet you have. You don't want some albino storming into your life and fucking up your shit.
The operating system means nothing. Of course, all games have a target audience. Right now, Linux is not deployed widely enough to be worried about. Of course, nothing is preventing from being used (many games get linux compatibility, through ports or emulators). It's a platform. Period.
but thats because its typical Linux shite: terrible documentation, terrible presentation, stupid bugs and complete lack of attention to detail.
But the thing about the re-link is still important; this way you only dlopen one file at startup that does everything, and you still haven't touched any of the other plugins.
- Force all plugins and extensions to implement an interface that self describes the modules... perhaps a special ELF segment naming the interface functions.
- Have a script that uses ld to link a special dynamic link library made up of all the individual plugin's initialization functions. (Since the names have to be unique, it'd need to examine the ELF segments in each DLL for the requisite functions to link, and to create the initialization order, serialiazing the function names to a text file)
- When GIMP loads, rather than scanning each plugin directly, it'd open the plugin-cache.so, then call a built-in function that reads the plugin-cache text file. It'd call each of the listed functions in turn from the plugin cache, and populate it's menus and toolbars with stubs that actually demand-load the plugins.
You'd probably need a system-wide and ~/.gimp specific plugin-cache.so/.txt.
The exception would be any plugins that directly render to the GIMP's UI or that require acquiring resources before the GIMP does.
1) Most prosumer/professional digital cameras, scanners, and frame grabbers have at least 10-bit, and sometimes 12-bit channels. These are usually cast into 16-bit values in various compatible file formats (i.e. TIFF).
2) More importantly, it is critical that any blending or intensity mapping operations are computed (and have intermediate results stored) in 16-bit to avoid unnecessary banding and clipping. You cast down to 8-bit when exporting to an 8-bit-only file format. Otherwise it's better to keep the precision around to avoid artifacts.
Slashdot Mirror
Carbon dioxide is heavier than air. Right.
Except did someone forget about gas laws from chemistry... you know, DIFFUSION?
If what they claimed were true, we'd all be choking and drowning in a carbon-dioxide, sulphur-dioxide, water-vapor-laden miasma. Fortunately for us, all those gases are disperesed evenly throughout the atmosphere, thus allowing us to BREATH, dumbass.
If they can't even get that part right, what makes you think the rest of it has any validity. Oh wait, it doesn't! It's full of conjecture and generalizations of the kinds worse than you claim climatologists make! Emporer has no clothes indeed.
... I can't find the fucking reference.
Anyway, its about some kind of squirrel or rodent in Australia, and that the specices was originally one (from mito-DNA evidence), but now one population has differently shaped tails, different feeding patterns, and they can no longer interbreed.
They are consider seperate species in their genus.
The populations got seperated during a food shortage across some gorge, which widened through erosion over the course of like a few thousand years, and now they can't access each other.
Maybe it isn't Australia, and that's why I can't find the reference. Arrgh.
Seriously. Seems to me that kind of thinking is what a sore loser crybaby would come up with...
You'll need a whole HELL of a lot of class time:
1) Christian 'Genesis' / Sumerian creation myth
2) Chinese creation myth
3) Norse creation myth
4) Egyptian creation myth
5) Simulation ala 13th floor / eXistenZ
6) Simulation ala Matrix or Metamorphasis of the P I
7) Benevolant aliens
8) Aliens using us for food or labor
9) Our own species which used very advanced technology to ensure it's own existence by going back in time...
I could go own. Lots of well thought out theories.
Oh wait, you just meant parts of #1. Well, that's not very fair is it?
Evolution is the best answer we have that doesn't make a whole lot of assumptions or is based on verbal lore. I think we should focus most of our class time on that.
When something else comes up that seems to be a better explanation that is both testable, demonstratable, and useful, I'd gladly replace evolution.
It's not managing the tape library that makes Veritas special. It's being able to keep point-in-time images of running machines handy, and not having to worry about managing duplicity.
That's the _hard_ part. I mean, volume management is great, but you only have to worry about that on the server. Vertias's multitudes of client agents is magical.
Anything else will make sendmail look slow.
He's a good programmer, but so are a lot of other people who aren't whiny jerks, and have to have everything done their way.
... thanks to you? ^_^
bittorrent could use an API wherein you can suggest it to fetch certain pieces, or determine whether pieces have been verified yet. That's half the battle (aside from figuring out how to effectively USE the API)
I'm sure you can think of other recent examples.
and I'm surprised no one has linked to the NYUD Coral cache of the slowed-down website yet... -_-
Apple outsourced most of the hardware and firmware design, (aside from the iTunes components) and they don't even manufacture them.
see here
and here.
It wasn't even Apple's idea to unify the player and the store.
As time progresses, Apple will become more of a software company and a brand. That may not be a bad thing, but credit where credit is due: Apple knows how to _identify_ a good product.
Try creating an inventory tracking system, PERIOD. Lots of stuff you use has barcodes. You could scan things "in" and "out" to try to keep track of stuff. So you scan it in when you take it out of your bag from the store, and scan it "out" when you open the package or use somethin' up, or maybe loan it someone.
Of course, it lacks wifi, so you'd have to probably code an app that queues up the operations (scan-in, then out, then in again should be collapsed to one scan-in)
Unfortunately, you're probably better off maintaining your own database of info for each product. This isn't such a big deal, cuz you're going to want to attach your own notes and stuff to each item.
javascript's type resolution is definition based
. html
this means the execution environment determines the behavior of namespace/module resolution issues (by dynamically loading code from external files or whatever as required with some intrinsic)
This way you can break your project into independant modules, implement test harnesses, etc.
javascript allows you to scope and prototype objects and defintions.
You provide namespace scoping by using nested definitions. And prototypes (i.e. classes, not clonable objects) are created using the prototype keyword.
Also check this out:
http://www.crockford.com/javascript/private
The tools are there. Unfortunately, you won't find many guides anywhere about how to use these properties to write maintainable code or work it in a collaborative environment. Discussions about closures and anonymous functions is also few and far between. But you will find endless discussion about detecting the DOM of various web-browsers (sigh).
It kept me from falling asleep many a day in high school. Curse the unavailability of scalar variables... and only 6 precious, precious lists.
I'm 100% serious. All this Copeland guy does is plug his rubyforge site or InfoEther.
Do you actually do any work on Ruby or do you just spend your time trolling message boards and mailing lists?
PS, I know where you live and work. Ever been to the theatre at Worldgate? I bet you have. You don't want some albino storming into your life and fucking up your shit.
Why the fuck do you have to plug Ruby every chance you get?
I love it but, Jesus Christ, you've got a problem.
But then, isn't HAVING FUN the reason why you play, not wanking off to pixel shaders?
The operating system means nothing.
Of course, all games have a target audience. Right now, Linux is not deployed widely enough to be worried about.
Of course, nothing is preventing from being used (many games get linux compatibility, through ports or emulators).
It's a platform.
Period.
but thats because its typical Linux shite: terrible documentation, terrible presentation, stupid bugs and complete lack of attention to detail.
Like what?
http://www.pacificneotek.com/linkProducts.htm
But the thing about the re-link is still important; this way you only dlopen one file at startup that does everything, and you still haven't touched any of the other plugins.
- Force all plugins and extensions to implement an interface that self describes the modules... perhaps a special ELF segment naming the interface functions.
- Have a script that uses ld to link a special dynamic link library made up of all the individual plugin's initialization functions. (Since the names have to be unique, it'd need to examine the ELF segments in each DLL for the requisite functions to link, and to create the initialization order, serialiazing the function names to a text file)
- When GIMP loads, rather than scanning each plugin directly, it'd open the plugin-cache.so, then call a built-in function that reads the plugin-cache text file. It'd call each of the listed functions in turn from the plugin cache, and populate it's menus and toolbars with stubs that actually demand-load the plugins.
You'd probably need a system-wide and ~/.gimp specific plugin-cache.so/.txt.
The exception would be any plugins that directly render to the GIMP's UI or that require acquiring resources before the GIMP does.
1) Most prosumer/professional digital cameras, scanners, and frame grabbers have at least 10-bit, and sometimes 12-bit channels. These are usually cast into 16-bit values in various compatible file formats (i.e. TIFF).
2) More importantly, it is critical that any blending or intensity mapping operations are computed (and have intermediate results stored) in 16-bit to avoid unnecessary banding and clipping. You cast down to 8-bit when exporting to an 8-bit-only file format. Otherwise it's better to keep the precision around to avoid artifacts.