What? Does the ECMA spec dictate the exact implementation of the RNG? If not, then it's not JavaScript that's broken, but the implementation(s) in question. Calling it "JavaScript's Broken RNG" is nonsense unless the language spec mandated or mandates a broken RNG.
MacKeeper's only reason for existence is people who don't know any better. It's malware, pure and simple. I really wish that decent sites would ban MacKeeper ads.
Tualatin Pentium IIIs ran circles around the early Pentium 4s
Yup, I remember that, and I was quite puzzled by it for a little while. I had a tricked-out dual-socket PIII system that was really hard to beat for a while.
A lot of CPU overhead? I use USB for realtime industrial communications and what you say is true only with completely braindead implementations (either host hardware or drivers for it). From what I can tell, a lot of Linux USB drivers, for both devices and hosts, are written by people who just don't dig asynchronous, realtime, low-overhead streaming of data. It's entirely a software problem, I'd say. Any reasonable USB host will support either DMA or shared memory, so byte pushing is free.
The effects are identical whether you are wrong or lie, so from the POV of the defendant it's a moot point. To them, it's all lies no matter whether they were motivated as such or not. Let's not belittle being wrong as "just" being wrong when people's livelihoods are at stake. Your way of thinking about it is a big contributor to the brokenness of the justice system.
OTOH, witnesses will lie with all the conviction they can muster without anyone having to instruct them, for they are unaware and in denial of the fallibility of their recollections. At the end, it's not the machine, but a human that lies.
the car is still in good enough shape to make the call'... that's a bullshit made up scenario to justify it
You're just silly now. Even in major airline accidents, where you have big debris fields, there is plenty of self-contained electronics units that survive almost unscathed. And we're talking of shit falling down and hitting the ground at hundreds of miles. In car accidents, most of the car's electronics are just fine. Most modern OnStar-like implementations have their own power source. They get information about the crash while the car has only begun the deceleration phase and hasn't been damaged yet. After storing the event, the module initiates the call. It has the capacity to act autonomously from that point onwards: you could remove the module and its antenna from the car and it'd still work.
You know what? I don't give a flying fuck about the privacy, or lack thereof, of people who commit hit-and-runs. And neither should you. The car did exactly what the society would like the modern car to do. If you pull a hit-and-run on me, I certainly want your car to fucking snitch on you. The car offers a viable technological solution to irresponsibility of drivers. I'm all for it.
I used to run PostgreSQL on a 486/66 linux-based server back in the day. Even then, when running with a PHP application the 256kbit/s link wasn't fast enough to expose any slowness in the database, the web server, or the application platform.
I do low-production-volume power converter designs every once in a while for instrumentation, and these things are all software controlled and any audible frequency components and sidebands are digitally modulated into white noise. You can literally attach a piezo buzzer across the primary inductor and all you'll hear is "ssssssh" of the noise. This is very much acceptable. Prior to that I was getting mentally sick from working with these things at my bench. I'd be hand-winding various inductors and tweaking things with no time to varnish the inductors - they'd be unbearably whiny in classic controller designs if they'd go into discontinuous/burst modes.
Purifying helium is not hard: everything else condenses out way before it does. You just blow "dirty" helium over a sufficiently cold heat exchanger, and everything other than helium will condense on the heat exchanger. See e.g. this excellent reference.
For most users, there is no warning. They absolutely can't recognize the behavior of their failing hard drive. My neighbors, two very wonderful ladies, have an iMac with a hard drive that has been failing and getting worse over the last year or so. They don't see a problem, while I cringe every time I visit them and hear the poor thing do a head cycle if they happen to be using it. The error counts are off the rails, I'm surprised it still works.
So, well, in practice, for 99% of the market, the progressive vs. instant failure distinction doesn't exist even when it comes to hard drive.
Back in the days of CP/M my dad splurged on a RAM disk. A 1 MByte RAM disk, no less, with a Ni-Cd battery backup on a daughtercard. The disk was visible to the OS as 4 256kB disks. It was sheer joy to work using that thing - think instant WordStar saves and menu switches (overlays had to load from disk!). When we moved to a PC/XT clone, I re-interfaced that disk and had "instant" boot-ups, much faster than even the half-height 20MB NEC hard drive would give. I'm awaiting for the future to catch up with the past where we'll be able to get rid of mechanical drives. It's about time. I got spoiled in my youth, you see.
Side note: This thing was a work of art, with properly engineered battery charger where each cell was individually charged using a flying capacitor kind of a set-up - the cells lasted for almost a decade.
Given that the de-icing fluid's performance is not perfect, I'd say that getting off the ground in icing conditions with a part of the wing untreated is like taking off with most of the redundancy gone. I'd be rattled by that too...
Frankly said, these cracks are inherent to this kind of through-hole board design. The pad is too small, and possibly the pin/lead hole is too small as well. The solder joint looks like leaded solder. Looks like a through-hole design done by a noob.
I'm not a pilot, but if you put me into a cockpit with screaming GPWS and no hints of overspeed, I would pull the stick and push the throttles to the stops. Once I could ascertain the airspeed, I would then let up on the throttle - if I wasn't a part of the debris field by then, of course...
I don't fly planes, but I'm an engineer that deals with process controls from time to time. When I see a message "F/CTL ALTN LAW (PROT LOST)", I know exactly what that means: push the stick too far or too fast, and you'll break/overstress something. Heck, you then look at page 2 and see precisely that, spelled out for these nitwits: "RUD WITH CARE ABV 160KT" - yeah, because you might break your fucking tail off. "AUTO_FLT AP OFF" is in fucking red!. Autopilot off, people - really, is that so hard to get?
For these who will now scream about "aviate [first], navigate, yada yada" - look, you fools, on modern jets the front ECAM pages are de-facto primary flight instruments. Ignore them at your own peril.
For the life of me I can't see why any pilot with a modicum of training on the type wouldn't know the importance of these messages, or the displays where they appear. Sometimes I think that we do pilot training on modern types somehow completely wrong.
Slashdot Mirror
Did you even read the submission? :)
What? Does the ECMA spec dictate the exact implementation of the RNG? If not, then it's not JavaScript that's broken, but the implementation(s) in question. Calling it "JavaScript's Broken RNG" is nonsense unless the language spec mandated or mandates a broken RNG.
MacKeeper's only reason for existence is people who don't know any better. It's malware, pure and simple. I really wish that decent sites would ban MacKeeper ads.
Would be nice, I guess?
Tualatin Pentium IIIs ran circles around the early Pentium 4s
Yup, I remember that, and I was quite puzzled by it for a little while. I had a tricked-out dual-socket PIII system that was really hard to beat for a while.
A lot of CPU overhead? I use USB for realtime industrial communications and what you say is true only with completely braindead implementations (either host hardware or drivers for it). From what I can tell, a lot of Linux USB drivers, for both devices and hosts, are written by people who just don't dig asynchronous, realtime, low-overhead streaming of data. It's entirely a software problem, I'd say. Any reasonable USB host will support either DMA or shared memory, so byte pushing is free.
USB is the proper interface. The driver for the SD card basically sucks.
How would you punish the computer?
You don't. You punish the corporation who screwed up the software.
It's just being wrong.
The effects are identical whether you are wrong or lie, so from the POV of the defendant it's a moot point. To them, it's all lies no matter whether they were motivated as such or not. Let's not belittle being wrong as "just" being wrong when people's livelihoods are at stake. Your way of thinking about it is a big contributor to the brokenness of the justice system.
Your car's systems can be instructed to lie
OTOH, witnesses will lie with all the conviction they can muster without anyone having to instruct them, for they are unaware and in denial of the fallibility of their recollections. At the end, it's not the machine, but a human that lies.
the car is still in good enough shape to make the call'... that's a bullshit made up scenario to justify it
You're just silly now. Even in major airline accidents, where you have big debris fields, there is plenty of self-contained electronics units that survive almost unscathed. And we're talking of shit falling down and hitting the ground at hundreds of miles. In car accidents, most of the car's electronics are just fine. Most modern OnStar-like implementations have their own power source. They get information about the crash while the car has only begun the deceleration phase and hasn't been damaged yet. After storing the event, the module initiates the call. It has the capacity to act autonomously from that point onwards: you could remove the module and its antenna from the car and it'd still work.
You know what? I don't give a flying fuck about the privacy, or lack thereof, of people who commit hit-and-runs. And neither should you. The car did exactly what the society would like the modern car to do. If you pull a hit-and-run on me, I certainly want your car to fucking snitch on you. The car offers a viable technological solution to irresponsibility of drivers. I'm all for it.
I used to run PostgreSQL on a 486/66 linux-based server back in the day. Even then, when running with a PHP application the 256kbit/s link wasn't fast enough to expose any slowness in the database, the web server, or the application platform.
That one must have been entered into their system without proper metadata, my search, sorted according to price, didn't return it :(
A Faraday Cage does not need to be grounded. There's no such thing as "ground" at 2.4GHz anyway.
I do low-production-volume power converter designs every once in a while for instrumentation, and these things are all software controlled and any audible frequency components and sidebands are digitally modulated into white noise. You can literally attach a piezo buzzer across the primary inductor and all you'll hear is "ssssssh" of the noise. This is very much acceptable. Prior to that I was getting mentally sick from working with these things at my bench. I'd be hand-winding various inductors and tweaking things with no time to varnish the inductors - they'd be unbearably whiny in classic controller designs if they'd go into discontinuous/burst modes.
Purifying helium is not hard: everything else condenses out way before it does. You just blow "dirty" helium over a sufficiently cold heat exchanger, and everything other than helium will condense on the heat exchanger. See e.g. this excellent reference.
$377, and that's from OWC, not exactly the cheapest outfit out there. The cheapest 1TB SSD currently runs for $323...
For most users, there is no warning. They absolutely can't recognize the behavior of their failing hard drive. My neighbors, two very wonderful ladies, have an iMac with a hard drive that has been failing and getting worse over the last year or so. They don't see a problem, while I cringe every time I visit them and hear the poor thing do a head cycle if they happen to be using it. The error counts are off the rails, I'm surprised it still works.
So, well, in practice, for 99% of the market, the progressive vs. instant failure distinction doesn't exist even when it comes to hard drive.
Back in the days of CP/M my dad splurged on a RAM disk. A 1 MByte RAM disk, no less, with a Ni-Cd battery backup on a daughtercard. The disk was visible to the OS as 4 256kB disks. It was sheer joy to work using that thing - think instant WordStar saves and menu switches (overlays had to load from disk!). When we moved to a PC/XT clone, I re-interfaced that disk and had "instant" boot-ups, much faster than even the half-height 20MB NEC hard drive would give. I'm awaiting for the future to catch up with the past where we'll be able to get rid of mechanical drives. It's about time. I got spoiled in my youth, you see.
Side note: This thing was a work of art, with properly engineered battery charger where each cell was individually charged using a flying capacitor kind of a set-up - the cells lasted for almost a decade.
Given that the de-icing fluid's performance is not perfect, I'd say that getting off the ground in icing conditions with a part of the wing untreated is like taking off with most of the redundancy gone. I'd be rattled by that too...
Frankly said, these cracks are inherent to this kind of through-hole board design. The pad is too small, and possibly the pin/lead hole is too small as well. The solder joint looks like leaded solder. Looks like a through-hole design done by a noob.
I'm not a pilot, but if you put me into a cockpit with screaming GPWS and no hints of overspeed, I would pull the stick and push the throttles to the stops. Once I could ascertain the airspeed, I would then let up on the throttle - if I wasn't a part of the debris field by then, of course...
The thing is: they acted instinctively based on some basic flight-or-flight instinct, not on their flight training... :(
I don't fly planes, but I'm an engineer that deals with process controls from time to time. When I see a message "F/CTL ALTN LAW (PROT LOST)", I know exactly what that means: push the stick too far or too fast, and you'll break/overstress something. Heck, you then look at page 2 and see precisely that, spelled out for these nitwits: "RUD WITH CARE ABV 160KT" - yeah, because you might break your fucking tail off. "AUTO_FLT AP OFF" is in fucking red!. Autopilot off, people - really, is that so hard to get?
For these who will now scream about "aviate [first], navigate, yada yada" - look, you fools, on modern jets the front ECAM pages are de-facto primary flight instruments . Ignore them at your own peril.
For the life of me I can't see why any pilot with a modicum of training on the type wouldn't know the importance of these messages, or the displays where they appear. Sometimes I think that we do pilot training on modern types somehow completely wrong.