NetBeans is a similar product to JBuilder (in fact, they're competing and Sun's giving it away with less strings than Inprise). Under the IBM JDK at least, the NetBeans app seems to be as snappy as any other RAD i've seen. The reason for the failures of applications like IDE/RAD builders and office suites in the past have been that the JVMs were just too damn slow. That's a little different now.
NVidia chose to not release details of the chip and recieve the same benefits of Open Source work like Matrox (and soon ATI) now enjoy. The drivers, while still are a developer release, seem to be faster in at least the Quake3 context than the Windows ICD for the same card. This is through those inefficient layers DRI removes. In theory, the GLX team could do the same thing for NVidia- if they would release register level specs for the chip like Matrox and ATI already have...
OpenGL's rendering model is going to make it "slow" except on the fastest machines- even if you lowered the quality. It's why they're not making it for LinuxPPC or AlphaLinux- yet.
Which chipset do you have?
ATI? In progress. NVidia? Provided- though slow. DRI promises to be a winner there. Matrox? Still a developer's release- but with persistance, a G200 or G400 is likely to be one of your better choices. S3 Rumor has it there's work started on it. SiS Data available, but work's waiting on someone to start it...
As a developer for the Windows platform over 8 years running, I can attest to them pulling BOTH stunts. There's things like Win32s/Win32c/Win32 and then there's things like Win16/Win32.
A prime example of the "dropped it" for something needlessly incompatible play they've done is the transition to the Win32 API from the "Win16" one. (By the way, it's also the best example of API cruft that MS is very guilty of...).
Win32s- produced to try to convince developers to write apps that would be moderately easy to port to NT from Win16. Comprises a small, twisted subset of Win32 with bizarre memory rules, etc. Has "Universal" thunks- of which, they're incompatible with everything else. Dropped like a hot potato when it was obvious that it was highly unstable and they had something "better" in hand (Windows 95 (a.k.a. "Chicago)).
Win32- The API for Windows NT. Highly complex, supports only bits and pieces of the Win16 API, making it incompatible with a lot of the earlier Windows apps- at a time where they were touting it's "compatibility". Has "generic" thunks- which Win32c supports with a translation layer that converts the generic thunk to it's native "flat" one. GDI calls work differently on Win32 than on any other platform.
Win32c- The Win95 Win32 API. Another subset of the "full" Win32 API. Incompatible with the full one in some cases (API calls do different things in identical cases.) Has "flat" thunks as it's primary thunking layer for 16-bit to 32-bit coding- this is incompatible with the Win32 API. In order to use thunks that work on both platforms, you're going to have to sacrifice some performance going through a translation layer that converts generic thunk code to flat thunk calls on the fly. MS is actively trying to kill off this API as they did with Win32s.
That's just one little example given as a capsule summary. I won't even go into the details of the TAPI, WinG, and other fiascos in this vein that MS has pulled in the past.
They're very guilty of both things.
That sounds like a variation on the "holostore"...
on
A 140GB CD-ROM?
·
· Score: 1
That tech from Keele University that you mention sounds suspiciously like a variation on a theme to holographic storage, known colloquially as a "holostore". MIT came up with the initial idea back in the 50's but couldn't get it to something commercializable. Periodically, you get someone that comes up with a new twist on the idea that brings it closer to reality each time- but they fail to make it happen for some reason or another.
Maybe they have it right this time- it'd be cool to have that sort of storage at reasonable price points.
I think Bill Beaty put it best on his page on the subject of Columbine. It's only a matter of time; and these morons are insuring it's going to happen with all this profiling BS- all we need right now is a witchhunt.
Hey, let's "profile" the problem people so we can single them out for "help". We all know what kinds of "help" they're going to get- and it's liable to help things right along to the holocaust and the poor bastards won't know what caused it or what hit them.
It's about time that we, the country as a whole, pull our collective heads out of the sand (or is that out of our rectums??) before it's too late and we experience something far, far more horrific than Columbine.
I think Bill Beaty put it best on his page on the subject of Columbine. It's only a matter of time; and these morons are insuring it's going to happen with all this profiling BS- all we need right now is a witchhunt.
Hey, let's "profile" the problem people so we can single them out for "help". We all know what kinds of "help" they're going to get- and it's liable to help things right along to the holocaust and the poor bastards won't know what caused it or what hit them.
It's about time that we, the country as a whole, pull our collective heads out of the sand (or is that out of our rectums??) before it's too late and we experience something far, far more horrific than Columbine.
I point you to a link to an article written by one of the more prominent people in the Ameteur Science community, Bill Beaty.
In it, he describes the very real dangers perpetuating the status quo. At the Columbine tragedy, they found a couple of devices that the boys had made up- but failed to effectively use (namely they malfunctioned). These devices should send shudders up your spine- they were fuel-air explosives. Had the boys been a little less inept at the manufacture of their bombs, there would have been a worse tragedy, there'd been just about nobody to survive the resultant holocaust.
It's time that we as a country and as a people quit deluding ourselves about everything being "okay" and that profiling the "problem" children will fix everything. It's a damned cop-out band-aid, that. There's something fundamentally dead-wrong with the whole system; it needs fixing now before something even more horrific that Columbine happens. And believe me when I say that it will if something else doesn't change soon. The social barriers to erasing yourself and taking a lot if not all the school with you in the process just got effectively removed by what transpired at Columbine; it's only a matter of time before someone clever comes up with a reliable device such as the ones used at Columbine. How many do they think they'll find with this "profiling"- and how many will slip by them? What will the ones that slip by them do?
Chernobyl released over one million times the background radiation into the environment- in forms that would be devastating to the whole world. The trees in the area soaked up a lot of the more vile isotopes released- but will not be able to do so again (they've already soaked up all they can...) The radiation levels at the reactor's location and the surrounding area were so high that you'd recieve your lifetime safe radiation dose in 90 seconds. Dozens being killed? Try in the tens of thousands in the area (unless it's in a truly isolated region...). Try in the millions of people adversely affected worldwide. They were truly lucky at Chernobyl the last time- what about the next "oops"?
Yes, through normal operation, a nuclear fission plant is cleaner and "safer" than a coal or gas fired plant. However, despite saftey regs, they are far more complex (in design and operation) and therefore at least slightly more likely to go prang and in a bad way at that. The catestrophic failure modes on many of the designs (esp. the ones over in the former Eastern Bloc countries) can be quite a bad thing for anyone around the things- so it's quite undesireable to have them about; no matter what you say to the contrary.
Cluebert is satirically challenged. Frankly speaking, the "satire" there leaves a little to be desired- nobody but the most extreme conservative (read: lunatic fringe) even come close to thinking or comporting themselves that way.
I've been about since it was born- before that I was a frequenter of Chips and Dips (it's predecessor!) and this joker doesn't speak for me.
While I'm a Linux coder/admin, the place I work for has standardized on Outlook/Exchange for their e-mail; this is a frigging nightmare for us to have to endure (Thank the Lord I've got daily backed up CVS repositories for our code- it's the only thing that saved places like Dell when they got ravaged by Melissa (MS lost months of work in some cases- Dell lost only a day's worth of work.)). All of you might think a catastrophe or even a scare caused by something like this would wise them up- you're dead wrong. The management types (the clueful and the PHB variety) don't usually think the same way you do and they won't automatically make the connection to blame the true cause, MS- so don't cop the attitude that you're ok and everyone else can just go to Hell in a handbasket because they basically did it to themselves (Yes, I know that it is these people's fault- but the best solution is to prevent the catastrophe and show them via this problem the error of their ways!).
Almost everything that has shown on this site belonged here. Not everyone here is a Linuxhead- it's wrong to assume that this is the case. If someone wants primarily Linux-only news, might I suggest LWN or Linux Today instead of/. You'll be a hell of a lot happer, believe me.
Spinning off the "offending" division doesn't absolve a company of it's liability in many cases- GW2K's still liable for the breach since it was performed while they were running it officially.
And as such, varies from ORB to ORB. In the case of our application that I'm working on for work, the ORB, TAO, is fast (In fact, it's one of the fastest ORBs around and is one of the only real-time, embeddable ones...). The only complaint is that it eats something like 2Mb in the system while operating- but once fielded, it's just there, each app gains from it.
Because that same company manages security (Or, at least they USED to...) at numerous installations that are of import National Security wise. Places like Sandia National Labs, Los Alamos, etc.
Wackenhut's a large, nationwide security organization, not unlike Pinkerton in size.
Contact DELL for that- of course, they're going to tell you that Linux isn't supported on that notebook. The VGA BIOS is not supposed to be the one saving states of the card- the save-to-disk is doing that one (and since that notebook was designed with Windows98/NT, and not VESA mode framebuffer, the code to preserve all of that may not be there in the notebook's BIOS.).
The GLX group has had docs in hand since September. It takes a little to get the ball initially rolling and the bulk of the coders are working on G200/G400 stability and speed for a point release before moving onto the DRI version of the same. We're waiting for the initial work on the DMA portion of the engine to be completed before moving on to the pixel bashing work. That phase should be starting shortly.
I thought they still kept the specs to themselves and business partners that signed one of their silly NDAs... When did that change and where can I snag the specs docs?
With industrial strenghth ORBs like ACE and MICO out that run and well at that under NT- do we need another "standard" that MS propagates? Will they keep it open or as they extend it to their own ends, will they pervert it so that you really have to use MS tools to do SOAP development right?
Seems that I happen to have the sitch here. He's been working it all his life and I've been around him for 25 years of my life.
And it's debatable- you just can't tell what some of this stuff will do when it's concentrated inside of a faraday cage (after all, that is what the cabin of a plane IS...). I've seen some pretty damn wierd stuff that shouldn't happen under those conditions. Are you sure that it's because of cell phone providers getting bolixed up? The regs are FAA regs, not FCC for starters. Also, do you know anything at all about cell phone frequencies and propagation? Those towers get their range because of the antennas they have- HIGHLY directional antennas. They have a largely horizontal lobe pattern from the towers; this means that you'd have to be at a couple thousand feet for this to be the case. Also, standard cell phones use 800MHz- the plane's a faraday cage for that frequency (PCS phones are another matter, but use even lower power and closer patterning (usually 1-2 miles) which changes the story.). Simply put, I'd find the statement that the cells would be jammed/confused by airborne phones as they most likely won't ever get to the towers because of conditions.
Takeoff and landing are the most dangerous times during a normal flight- no real room for any errors.
Everything should be fine if everything is properly shielded- but as you know, something might miss inspection, say a small break, etc. in the shielding on the cables, etc. Micropower RF, like that from computers and especially mobile phones is known to fubar a LOT of things on the plane. I'd rather you didn't run the things when you're not supposed to because a fscked up avionics system can kill you and everyone around you. It's for your saftey that they do this.
Oh, and by the way, your phone's going to be at an altiude through most of your flight that the phone will not work. And I've sat on the tarmac for more than 30 minutes and the captain let cell phone users turn their phones on while we were waiting for clearance for takeoff.
Slashdot Mirror
If it's the case, take the tripe somewhere else- it's not anymore welcome here than it's welcome on (AB)USENET.
NetBeans is a similar product to JBuilder (in fact, they're competing and Sun's giving it away with less strings than Inprise). Under the IBM JDK at least, the NetBeans app seems to be as snappy as any other RAD i've seen. The reason for the failures of applications like IDE/RAD builders and office suites in the past have been that the JVMs were just too damn slow. That's a little different now.
NVidia chose to not release details of the chip and recieve the same benefits of Open Source work like Matrox (and soon ATI) now enjoy. The drivers, while still are a developer release, seem to be faster in at least the Quake3 context than the Windows ICD for the same card. This is through those inefficient layers DRI removes. In theory, the GLX team could do the same thing for NVidia- if they would release register level specs for the chip like Matrox and ATI already have...
OpenGL's rendering model is going to make it "slow" except on the fastest machines- even if you lowered the quality. It's why they're not making it for LinuxPPC or AlphaLinux- yet.
Which chipset do you have?
ATI? In progress.
NVidia? Provided- though slow. DRI promises to be a winner there.
Matrox? Still a developer's release- but with persistance, a G200 or G400 is likely to be one of your better choices.
S3 Rumor has it there's work started on it.
SiS Data available, but work's waiting on someone to start it...
As a developer for the Windows platform over 8 years running, I can attest to them pulling BOTH stunts. There's things like Win32s/Win32c/Win32 and then there's things like Win16/Win32.
A prime example of the "dropped it" for something needlessly incompatible play they've done is the transition to the Win32 API from the "Win16" one. (By the way, it's also the best example of API cruft that MS is very guilty of...).
Win32s- produced to try to convince developers to write apps that would be moderately easy to port to NT from Win16. Comprises a small, twisted subset of Win32 with bizarre memory rules, etc. Has "Universal" thunks- of which, they're incompatible with everything else. Dropped like a hot potato when it was obvious that it was highly unstable and they had something "better" in hand (Windows 95 (a.k.a. "Chicago)).
Win32- The API for Windows NT. Highly complex, supports only bits and pieces of the Win16 API, making it incompatible with a lot of the earlier Windows apps- at a time where they were touting it's "compatibility". Has "generic" thunks- which Win32c supports with a translation layer that converts the generic thunk to it's native "flat" one. GDI calls work differently on Win32 than on any other platform.
Win32c- The Win95 Win32 API. Another subset of the "full" Win32 API. Incompatible with the full one in some cases (API calls do different things in identical cases.)
Has "flat" thunks as it's primary thunking layer for 16-bit to 32-bit coding- this is incompatible with the Win32 API. In order to use thunks that work on both platforms, you're going to have to sacrifice some performance going through a translation layer that converts generic thunk code to flat thunk calls on the fly. MS is actively trying to kill off this API as they did with Win32s.
That's just one little example given as a capsule summary. I won't even go into the details of the TAPI, WinG, and other fiascos in this vein that MS has pulled in the past.
They're very guilty of both things.
That tech from Keele University that you mention sounds suspiciously like a variation on a theme to holographic storage, known colloquially as a "holostore". MIT came up with the initial idea back in the 50's but couldn't get it to something commercializable. Periodically, you get someone that comes up with a new twist on the idea that brings it closer to reality each time- but they fail to make it happen for some reason or another.
Maybe they have it right this time- it'd be cool to have that sort of storage at reasonable price points.
I think Bill Beaty put it best on his page on the subject of Columbine. It's only a matter of time; and these morons are insuring it's going to happen with all this profiling BS- all we need right now is a witchhunt.
Hey, let's "profile" the problem people so we can single them out for "help". We all know what kinds of "help" they're going to get- and it's liable to help things right along to the holocaust and the poor bastards won't know what caused it or what hit them.
It's about time that we, the country as a whole, pull our collective heads out of the sand (or is that out of our rectums??) before it's too late and we experience something far, far more horrific than Columbine.
I think Bill Beaty put it best on his page on the subject of Columbine. It's only a matter of time; and these morons are insuring it's going to happen with all this profiling BS- all we need right now is a witchhunt.
Hey, let's "profile" the problem people so we can single them out for "help". We all know what kinds of "help" they're going to get- and it's liable to help things right along to the holocaust and the poor bastards won't know what caused it or what hit them.
It's about time that we, the country as a whole, pull our collective heads out of the sand (or is that out of our rectums??) before it's too late and we experience something far, far more horrific than Columbine.
I point you to a link to an article written by one of the more prominent people in the Ameteur Science community, Bill Beaty.
In it, he describes the very real dangers perpetuating the status quo. At the Columbine tragedy, they found a couple of devices that the boys had made up- but failed to effectively use (namely they malfunctioned). These devices should send shudders up your spine- they were fuel-air explosives. Had the boys been a little less inept at the manufacture of their bombs, there would have been a worse tragedy, there'd been just about nobody to survive the resultant holocaust .
It's time that we as a country and as a people quit deluding ourselves about everything being "okay" and that profiling the "problem" children will fix everything. It's a damned cop-out band-aid, that. There's something fundamentally dead-wrong with the whole system; it needs fixing now before something even more horrific that Columbine happens. And believe me when I say that it will if something else doesn't change soon. The social barriers to erasing yourself and taking a lot if not all the school with you in the process just got effectively removed by what transpired at Columbine; it's only a matter of time before someone clever comes up with a reliable device such as the ones used at Columbine. How many do they think they'll find with this "profiling"- and how many will slip by them? What will the ones that slip by them do?
Fix the damn problem, not the symptoms!
Chernobyl released over one million times the background radiation into the environment- in forms that would be devastating to the whole world. The trees in the area soaked up a lot of the more vile isotopes released- but will not be able to do so again (they've already soaked up all they can...) The radiation levels at the reactor's location and the surrounding area were so high that you'd recieve your lifetime safe radiation dose in 90 seconds . Dozens being killed? Try in the tens of thousands in the area (unless it's in a truly isolated region...). Try in the millions of people adversely affected worldwide. They were truly lucky at Chernobyl the last time- what about the next "oops"?
Yes, through normal operation, a nuclear fission plant is cleaner and "safer" than a coal or gas fired plant. However, despite saftey regs, they are far more complex (in design and operation) and therefore at least slightly more likely to go prang and in a bad way at that. The catestrophic failure modes on many of the designs (esp. the ones over in the former Eastern Bloc countries) can be quite a bad thing for anyone around the things- so it's quite undesireable to have them about; no matter what you say to the contrary.
'nuff said...
Cluebert is satirically challenged. Frankly speaking, the "satire" there leaves a little to be desired- nobody but the most extreme conservative (read: lunatic fringe) even come close to thinking or comporting themselves that way.
I've been about since it was born- before that I was a frequenter of Chips and Dips (it's predecessor!) and this joker doesn't speak for me.
/. You'll be a hell of a lot happer, believe me.
While I'm a Linux coder/admin, the place I work for has standardized on Outlook/Exchange for their e-mail; this is a frigging nightmare for us to have to endure (Thank the Lord I've got daily backed up CVS repositories for our code- it's the only thing that saved places like Dell when they got ravaged by Melissa (MS lost months of work in some cases- Dell lost only a day's worth of work.)). All of you might think a catastrophe or even a scare caused by something like this would wise them up- you're dead wrong. The management types (the clueful and the PHB variety) don't usually think the same way you do and they won't automatically make the connection to blame the true cause, MS- so don't cop the attitude that you're ok and everyone else can just go to Hell in a handbasket because they basically did it to themselves (Yes, I know that it is these people's fault- but the best solution is to prevent the catastrophe and show them via this problem the error of their ways!).
Almost everything that has shown on this site belonged here. Not everyone here is a Linuxhead- it's wrong to assume that this is the case. If someone wants primarily Linux-only news, might I suggest LWN or Linux Today instead of
And I responded "N/A (Riiiiight....)" to the question. I'm a little concerned about that- seems at least someone there doesn't "get it".
This is an excellent idea!
And there is no Findings of Fact up on their site. Guess we all jumped the gun a bit, eh?
Spinning off the "offending" division doesn't absolve a company of it's liability in many cases- GW2K's still liable for the breach since it was performed while they were running it officially.
And as such, varies from ORB to ORB. In the case of our application that I'm working on for work, the ORB, TAO, is fast (In fact, it's one of the fastest ORBs around and is one of the only real-time, embeddable ones...). The only complaint is that it eats something like 2Mb in the system while operating- but once fielded, it's just there, each app gains from it.
Because that same company manages security (Or, at least they USED to...) at numerous installations that are of import National Security wise. Places like Sandia National Labs, Los Alamos, etc.
Wackenhut's a large, nationwide security organization, not unlike Pinkerton in size.
...not the VGA BIOS...
Contact DELL for that- of course, they're going to tell you that Linux isn't supported on that notebook. The VGA BIOS is not supposed to be the one saving states of the card- the save-to-disk is doing that one (and since that notebook was designed with Windows98/NT, and not VESA mode framebuffer, the code to preserve all of that may not be there in the notebook's BIOS.).
The GLX group has had docs in hand since September. It takes a little to get the ball initially rolling and the bulk of the coders are working on G200/G400 stability and speed for a point release before moving onto the DRI version of the same. We're waiting for the initial work on the DMA portion of the engine to be completed before moving on to the pixel bashing work. That phase should be starting shortly.
I thought they still kept the specs to themselves and business partners that signed one of their silly NDAs... When did that change and where can I snag the specs docs?
With industrial strenghth ORBs like ACE and MICO out that run and well at that under NT- do we need another "standard" that MS propagates? Will they keep it open or as they extend it to their own ends, will they pervert it so that you really have to use MS tools to do SOAP development right?
MS just doesn't get it do they?
Seems that I happen to have the sitch here. He's been working it all his life and I've been around him for 25 years of my life.
And it's debatable- you just can't tell what some of this stuff will do when it's concentrated inside of a faraday cage (after all, that is what the cabin of a plane IS...). I've seen some pretty damn wierd stuff that shouldn't happen under those conditions. Are you sure that it's because of cell phone providers getting bolixed up? The regs are FAA regs, not FCC for starters. Also, do you know anything at all about cell phone frequencies and propagation? Those towers get their range because of the antennas they have- HIGHLY directional antennas. They have a largely horizontal lobe pattern from the towers; this means that you'd have to be at a couple thousand feet for this to be the case. Also, standard cell phones use 800MHz- the plane's a faraday cage for that frequency (PCS phones are another matter, but use even lower power and closer patterning (usually 1-2 miles) which changes the story.). Simply put, I'd find the statement that the cells would be jammed/confused by airborne phones as they most likely won't ever get to the towers because of conditions.
Takeoff and landing are the most dangerous times during a normal flight- no real room for any errors.
Everything should be fine if everything is properly shielded- but as you know, something might miss inspection, say a small break, etc. in the shielding on the cables, etc. Micropower RF, like that from computers and especially mobile phones is known to fubar a LOT of things on the plane. I'd rather you didn't run the things when you're not supposed to because a fscked up avionics system can kill you and everyone around you. It's for your saftey that they do this.
Oh, and by the way, your phone's going to be at an altiude through most of your flight that the phone will not work. And I've sat on the tarmac for more than 30 minutes and the captain let cell phone users turn their phones on while we were waiting for clearance for takeoff.