THE limiting factor is not storage space. It's the quality of the optics. At such small sizes, getting true flat-field optics is tough. Not impossible, but harder than shrinking a 1gig card...
And that's why sales guys take 10% commissions on REVENUE/INVOICE, and not PROFIT, since the Corp is always trying to squeeze out less PROFIT for the sales weasel.
So if I ever make a movie (gack!), I'll take my $100 up front, and 10% of total movie revenue. Like the smart actors...;-)
You've got an automated build process that spits out compilation errors at every bad line of code, an open source compiler, and open source apps. Either fix the apps, or fix gcc, but quit bitching that it's the "embrace-or-extend" because app writers support the most ubiquitous compiler for the OSS world. That's like bitching that Windows MFC apps only compile properly with MSVC++ 7.0 and not GCC. 99% of Windows developers aren't using GCC. You have no choice in the matter with MSFT and it's actions, but you can at least contribute to fix broken Open Source.
What I'm worried about is getting used to my flesh-safe saw, and then grabbing my roommates dad's old Wahl chainsaw or something, and getting careless...
Yeah, I can see disrespect start to creep in. Nothing breeds contempt like familiarity though... (I do some pretty dangerous pocket cuts in 4'x8' plywood sometimes...)
God, you can imagine trying to stop 400 tons with that little tractor rig? Visions of the tandem rig I saw last night tailgating a Civic 20' off his rear bumper at 70 mph.
IIRC, NASA has flown a few DoD payloads since Challenger. STS-32 was the first DoD payload I noted after Challenger, but I haven't reviewed every mission profile at nasa.gov.
From what *I* understand, there doesn't seem to be a lot of cutting edge military aerospace work that isn't going on in either California or Washington (boeing/lockheed). NASA has the whole hyperX project, and the military is looking more at space dominance than air dominance for the 21st century.
That ending. Pointless. Overdone, Over the Top, typical bad-boy gone-good gone-bad-because-of-evil-demon-father, gone-good-for-love-of-woman. Drivel. Strip off the last 20 minutes of the movie, and I'd agree with you.
I have removed IE from all my personal computers (not physically, but the only way to use it is from the Explorer address bar.
No, what really pisses me off is when people sit down and use my running copy of Mozilla (which has another shortcut called Internet Exlorer++ which fakes out most people, even has the circular blue E) they end up closing all my existing tabs.
I have to specifically warn them NOT to close my browser... weirdos. Good thing I'm getting a public kiosk computer for the dozens of people who come roaming through my house on a weekly basis.
A reactor, by definition, reacts to something, in this case, the impact of one neutron against another and a cascading effect of atoms splitting. It does not necessarily imply a sustained reaction.
In which case, an RTG is indeed a reactor, although nowhere near as energetic as the ones run by Exelon, for example. Naturally decaying radioactive material can cause a chain reaction, although it's almost never long-lived since the material density is almost never great enough to sustain it.
Ask the poor fool who died at Los Alamos in the 40's because he let two plutonium pit halves touch each other.
It's a semantic difference really... is all I'm saying.
Another reply has illustrated to your 14 year old mind that there was a vb before.net. And that VB was a pathetic piece of shit. It was great for building forms based GUIs, great for database access, with controls designed specifically for this. File parsing, complex data structures, PITA.
I can't count the number of times I've had to write a C++ COM Object to get around limitations in vb5/6. In point of fact, the automation aspects of VB5/6 are all that made it usuable/extensible. Without the fact that well over 90% of the useful work you can do in VB is implemented as COM objects, VB would be worthless.
While I agree with you in principle, if I had a project that was liable to encounter scope creep, I usually picked something else. Once I ended up with 20+ forms and database interaction or file parsing, I tended towards Java solutions or C++ with MFC. VB offered me no better.
Granted, I built quite a few applications in Access Forms (which is really VBA under the hood anyway) rather than with a full blown vb6 project.
I tend towards building web apps anyway. 95% of the shit I do is data entry and validation, and almost all of it is easily down via web and DHTML, which is where vbscript comes in. Other than being hamstrung by.ASP, vbscript has no limitations that javascript or perlscript do not also have.
Note, I've yet to touch.Net. Not entirely sure I want to walk that road...
Actually, the way I understand number portability is that the phone company *IS* given a range of numbers to manage, and that if you want true portability from one provider to another, you're paying a fee to the original provider, since you're still using *HIS* call routing mechanisms to forward your call to your new provider.
I have to agree. If all you are doing is talking to an Access or SQL database and building forms, VB is perfect. Anything outside this regime, and you spend more time reinventing the wheel. And if you don't have a database backing you up, you spend a LOT of time reimplementing basic data structures, like multi-dimensional arrays, hashmaps, lists, etc.
I like it because ADO and VbScript (ASP) allow me to create business applications quickly and reliably. But I hate it because I spend a lot of time reimplementing things, or working around a broken include system.
Not really. You could, in theory, implement an XML parser in nothing by SQL-92 stored procedures. It'd be nasty, evil-looking code, and probably slower than a 3-toed-sloth with broken toes, but it could be done.
<obl. Microsoft bash> Does anyone know if SQL Server's XML support is written this way? </bash>
I have to disagree here. If you've done your data model properly, and have your relationships set up right, retrieving nearly everything about your customer can be done in one query.
The fact that a SQL resultset might end up consuming MORE memory by far by redundant data in many columns than an XML resultset, that I'll give you.
What you need to do is go back to using Mailto: to sign up for mailing lists. then with this system, you're automatically whitelisted (since it's sender-user originating).
Now if only we could craft better emails with javascript (oh the horrors and exploits).
var newMail = new EMail(); newMail.subject = "subscribe mailinglist@domain.tld"; newmail.address = "majordomo.."; . . . newMail.Send();//opens email dialog and prompts user to send (to prevent websites from hijacking a whitelist entry).
Slashdot Mirror
Unless the post-war Iraq Democracy caused Peace In the Middle East.
But I *REALLY* don't envision that happening.
THE limiting factor is not storage space. It's the quality of the optics. At such small sizes, getting true flat-field optics is tough. Not impossible, but harder than shrinking a 1gig card...
And that's why sales guys take 10% commissions on REVENUE/INVOICE, and not PROFIT, since the Corp is always trying to squeeze out less PROFIT for the sales weasel.
;-)
So if I ever make a movie (gack!), I'll take my $100 up front, and 10% of total movie revenue. Like the smart actors...
Do you realize how silly you sound?
You've got an automated build process that spits out compilation errors at every bad line of code, an open source compiler, and open source apps. Either fix the apps, or fix gcc, but quit bitching that it's the "embrace-or-extend" because app writers support the most ubiquitous compiler for the OSS world. That's like bitching that Windows MFC apps only compile properly with MSVC++ 7.0 and not GCC. 99% of Windows developers aren't using GCC. You have no choice in the matter with MSFT and it's actions, but you can at least contribute to fix broken Open Source.
System.Windows.Forms?
I recommend these people try the HURD. I hear they need a bunch of wannabee uber-geeks to test their kernel...
Plus, you can bitch and moan all you want about it being the One True Gnu, and be right for a change.
no, but chainmail might.
What I'm worried about is getting used to my flesh-safe saw, and then grabbing my roommates dad's old Wahl chainsaw or something, and getting careless...
Yeah, I can see disrespect start to creep in. Nothing breeds contempt like familiarity though... (I do some pretty dangerous pocket cuts in 4'x8' plywood sometimes...)
God, you can imagine trying to stop 400 tons with that little tractor rig? Visions of the tandem rig I saw last night tailgating a Civic 20' off his rear bumper at 70 mph.
IIRC, NASA has flown a few DoD payloads since Challenger. STS-32 was the first DoD payload I noted after Challenger, but I haven't reviewed every mission profile at nasa.gov.
From what *I* understand, there doesn't seem to be a lot of cutting edge military aerospace work that isn't going on in either California or Washington (boeing/lockheed). NASA has the whole hyperX project, and the military is looking more at space dominance than air dominance for the 21st century.
In WWII, where there were no helicopters, and Vietnam, where helicopters had a nasty habit of getting shot down and soldiers ended up humping it.
OP: Funny yes. True? About as true as anything you else you read on the Internet in an unattributed manner.
I live in a frathouse for 30year old college dropouts. The computer is right next to the keg fridge. I think that's all I need to say about that. :-)
That ending. Pointless. Overdone, Over the Top, typical bad-boy gone-good gone-bad-because-of-evil-demon-father, gone-good-for-love-of-woman. Drivel. Strip off the last 20 minutes of the movie, and I'd agree with you.
Thanks. Now you've done it. You've destroyed two perfectly good sex-pots with your nitpicking... Thanks.
;-)
May you both rot in hell.
I have removed IE from all my personal computers (not physically, but the only way to use it is from the Explorer address bar.
No, what really pisses me off is when people sit down and use my running copy of Mozilla (which has another shortcut called Internet Exlorer++ which fakes out most people, even has the circular blue E) they end up closing all my existing tabs.
I have to specifically warn them NOT to close my browser... weirdos. Good thing I'm getting a public kiosk computer for the dozens of people who come roaming through my house on a weekly basis.
A reactor, by definition, reacts to something, in this case, the impact of one neutron against another and a cascading effect of atoms splitting. It does not necessarily imply a sustained reaction.
In which case, an RTG is indeed a reactor, although nowhere near as energetic as the ones run by Exelon, for example. Naturally decaying radioactive material can cause a chain reaction, although it's almost never long-lived since the material density is almost never great enough to sustain it.
Ask the poor fool who died at Los Alamos in the 40's because he let two plutonium pit halves touch each other.
It's a semantic difference really... is all I'm saying.
the screaming. And the dying. Those make noise too. At least while your compartment is still pressurized.
Another reply has illustrated to your 14 year old mind that there was a vb before .net. And that VB was a pathetic piece of shit. It was great for building forms based GUIs, great for database access, with controls designed specifically for this. File parsing, complex data structures, PITA.
I can't count the number of times I've had to write a C++ COM Object to get around limitations in vb5/6. In point of fact, the automation aspects of VB5/6 are all that made it usuable/extensible. Without the fact that well over 90% of the useful work you can do in VB is implemented as COM objects, VB would be worthless.
While I agree with you in principle, if I had a project that was liable to encounter scope creep, I usually picked something else. Once I ended up with 20+ forms and database interaction or file parsing, I tended towards Java solutions or C++ with MFC. VB offered me no better.
.ASP, vbscript has no limitations that javascript or perlscript do not also have.
.Net. Not entirely sure I want to walk that road...
Granted, I built quite a few applications in Access Forms (which is really VBA under the hood anyway) rather than with a full blown vb6 project.
I tend towards building web apps anyway. 95% of the shit I do is data entry and validation, and almost all of it is easily down via web and DHTML, which is where vbscript comes in. Other than being hamstrung by
Note, I've yet to touch
Actually, the way I understand number portability is that the phone company *IS* given a range of numbers to manage, and that if you want true portability from one provider to another, you're paying a fee to the original provider, since you're still using *HIS* call routing mechanisms to forward your call to your new provider.
Someone care to correct me?
No, but the FCC could but a bug in the FTC's ass, which, in point of fact, does have authority to regulate zee Intarweb.
I have to agree. If all you are doing is talking to an Access or SQL database and building forms, VB is perfect. Anything outside this regime, and you spend more time reinventing the wheel. And if you don't have a database backing you up, you spend a LOT of time reimplementing basic data structures, like multi-dimensional arrays, hashmaps, lists, etc.
I like it because ADO and VbScript (ASP) allow me to create business applications quickly and reliably. But I hate it because I spend a lot of time reimplementing things, or working around a broken include system.
Better than whitehouse.com.
Not really. You could, in theory, implement an XML parser in nothing by SQL-92 stored procedures. It'd be nasty, evil-looking code, and probably slower than a 3-toed-sloth with broken toes, but it could be done.
<obl. Microsoft bash>
Does anyone know if SQL Server's XML support is written this way?
</bash>
I have to disagree here. If you've done your data model properly, and have your relationships set up right, retrieving nearly everything about your customer can be done in one query.
The fact that a SQL resultset might end up consuming MORE memory by far by redundant data in many columns than an XML resultset, that I'll give you.
What you need to do is go back to using Mailto: to sign up for mailing lists. then with this system, you're automatically whitelisted (since it's sender-user originating).
//opens email dialog and prompts user to send (to prevent websites from hijacking a whitelist entry).
Now if only we could craft better emails with javascript (oh the horrors and exploits).
var newMail = new EMail();
newMail.subject = "subscribe mailinglist@domain.tld";
newmail.address = "majordomo..";
.
.
.
newMail.Send();
Surely this could be made exploit free?