Now wait just a damn minute. Are you trying to tell us that it's stupid and completely irresponsible to grow monsoon crops in an arid desert environment, and then bitch when there isn't enough water to go around?
In fact, launchd was a godsend in the early OS X days. Instead of a mishmash of INIT and Classic MacOS nonsense (/Library/StartupItems), you ended up with one system that could handle per-user agents as well as system daemons, process monitoring and respawning, jobs defined in the same property list format everything else in the system is, and a scriptable interface (launchctl) for simple administration.
Then they open sourced it. And nobody decided to use it, even though it has been bulletproof for 10 years now.
The House doesn't operate under rules that prevent singular persons from bringing things to the floor like the Senate does. A bill gets written by a member, and gets referred to the proper committee. If the committee votes in favor, it goes before the full House for debate and voting.
There is no filibuster, nor super-majority cloture vote as in the Senate. House rules go back to Thomas Jefferson, and have been changed very little. The Senate was modeled after Parliamentary procedure, thus has some odd things such as cloture votes to end debate, which is the primary mechanic used for obstruction - you need 60 votes to close debate so that you can see if there are 51 votes to pass the bill.
Either way, the second part of your statement is absolutely correct. Even if this thing comes out of the house, and by some oddity of politics or monied influence gets through a cloture vote and passes the Senate, it's highly unlikely that the President would put his name to this piece of trash on parchment. Don't know if he's straight-up veto though - he'd probably want a piece of the monetary influence after he's out of office too. Maybe a pocket veto.
The US Navy operates a bit differently from commercial power; they have the freedom to not give a crap about being cost-effective. When it's time to refuel a nuclear submarine, they cut the entire reactor core out of the side of it and drop a new one in. The old core goes away to be disposed, and the submarine goes back out to sea.
It's amazing the safety record you can have if you just throw away the whole thing and start over every time you need to refuel.
mdsolar may be anti-nuclear power, but that doesn't make the story any less alarming. One of the leaders in nuclear generating technology is essentially bankrupt.
Sounds like an argument for IPSec for anything that matters - as long as you're Doing It Right you get message integrity and authenticity. That's the whole point.
Now, if someone's cracked IKEv2, SHA, or AES all bets are off.
It's been used for decades everywhere except the PC and it's server variants. It's no more a risk than current patching that requires a reboot, except that you don't have the downtime of a reboot.
A bad patch is a bad patch. Have backups, have redundancy.
On OS X the reboot is for user convenience. If you use the command line software update tools, you can install them as you wish, and not reboot. Then you can restart services with launchctl or reload patched kexts and save yourself a reboot. Does this take a lot of extra time and testing? Sure - thus the reboot.
The problem with the way DSL worked with so called "naked" service is that you were still relying on the shit infrastructure that the local telco had there. 8000 feet away from the DSLAM, on a trunk that has 90% utilization making for a shitload of crosstalk interference? Too bad. All the "choices" could still only deliver the same shitty 512k service because the equipment just couldn't do better without someone putting more lines on poles.
The 1-series and 3-series did have both 2-door and 4-door versions, and this was confusing in respect to where they were going with their numbering schemes.
Thus, the 2-series and 4-series were born as the 2-door versions of the 1-series and 3-series, respectively.
Want 4 doors? Get an odd-numbered first digit. 2 doors? Even.
What's really funny, is that if they would have marketed it as a 3.5GB card, and then people started to figure out that there was really 4GB of RAM on there, they probably would have gotten better sales of the part through the hardware hack community trying to figure out how to "unlock" it.
The other effect is that Nvidia gets a nice fat punitive settlement levied against them, which acts as a deterrent from doing this crap again. I think that's the point.
You just gave a nice list of reasons why Apple might want to hire some competent battery engineers.
1. Absent internal knowledge 2. Current products have far lower energy density than other possible batteries 3. All gains currently employed are from software, and that's grown to maturity with diminishing returns setting in.
Yeah, I can't possibly think why they would want to hire some Ph. Ds that know battery technology and start working their own hardware.
Pretty much every car uses fuel injection now, because it is vastly superior in every meaningful way. Carburetors persisted for a while in motorcycle engines, but fuel injection is taking over that market too.
Even corporate dinosaurs that have legacy mainframe operations that go back decades are moving to VM clustering because of the inherent advantages. When I worked for one of these dinosaurs last year, I was walking through the mainframe operations group and someone had a thing printed on the side of her cube extolling that it would take 400 x86 servers to equal their S390. Someone from the VM engineering team had taken a sharpie to it and crossed out the "400 x86 servers" and written on "10 VMware hosts".
It seems that a lot of "big iron" people don't even recognize the existence of the inherent scalability advantages that VMs provide, even though their mainframes have been doing the same thing for decades.
Yeah, the x86 stack doesn't need that kind of reliability, because of the inexpensiveness of the hardware. If you need that kind of uptime, you buy 3 and put them behind a load balancing scheme. You end up with more capacity, the same reliability, and still less expense. Especially in the world of virtualized server instances.
Slashdot Mirror
Please explain how "development remains a walled garden" for OS X.
We'll give you all the time you need, which is forever, because it totally isn't.
Now wait just a damn minute. Are you trying to tell us that it's stupid and completely irresponsible to grow monsoon crops in an arid desert environment, and then bitch when there isn't enough water to go around?
Instead of going to Dell, why not use Amazon EC2? Probably do it way cheaper and you could set it up in a couple hours.
In fact, launchd was a godsend in the early OS X days. Instead of a mishmash of INIT and Classic MacOS nonsense (/Library/StartupItems), you ended up with one system that could handle per-user agents as well as system daemons, process monitoring and respawning, jobs defined in the same property list format everything else in the system is, and a scriptable interface (launchctl) for simple administration.
Then they open sourced it. And nobody decided to use it, even though it has been bulletproof for 10 years now.
The House doesn't operate under rules that prevent singular persons from bringing things to the floor like the Senate does. A bill gets written by a member, and gets referred to the proper committee. If the committee votes in favor, it goes before the full House for debate and voting.
There is no filibuster, nor super-majority cloture vote as in the Senate. House rules go back to Thomas Jefferson, and have been changed very little. The Senate was modeled after Parliamentary procedure, thus has some odd things such as cloture votes to end debate, which is the primary mechanic used for obstruction - you need 60 votes to close debate so that you can see if there are 51 votes to pass the bill.
Either way, the second part of your statement is absolutely correct. Even if this thing comes out of the house, and by some oddity of politics or monied influence gets through a cloture vote and passes the Senate, it's highly unlikely that the President would put his name to this piece of trash on parchment. Don't know if he's straight-up veto though - he'd probably want a piece of the monetary influence after he's out of office too. Maybe a pocket veto.
The US Navy operates a bit differently from commercial power; they have the freedom to not give a crap about being cost-effective. When it's time to refuel a nuclear submarine, they cut the entire reactor core out of the side of it and drop a new one in. The old core goes away to be disposed, and the submarine goes back out to sea.
It's amazing the safety record you can have if you just throw away the whole thing and start over every time you need to refuel.
mdsolar may be anti-nuclear power, but that doesn't make the story any less alarming. One of the leaders in nuclear generating technology is essentially bankrupt.
Sounds like an argument for IPSec for anything that matters - as long as you're Doing It Right you get message integrity and authenticity. That's the whole point.
Now, if someone's cracked IKEv2, SHA, or AES all bets are off.
It's been used for decades everywhere except the PC and it's server variants. It's no more a risk than current patching that requires a reboot, except that you don't have the downtime of a reboot.
A bad patch is a bad patch. Have backups, have redundancy.
On OS X the reboot is for user convenience. If you use the command line software update tools, you can install them as you wish, and not reboot. Then you can restart services with launchctl or reload patched kexts and save yourself a reboot. Does this take a lot of extra time and testing? Sure - thus the reboot.
Climb the steps! Climb the steps of Mount Seleya!
No, anyone that contradicts Fox News is a Socialist / Communist. Get your extreme ends of the spectrum correct.
The problem with the way DSL worked with so called "naked" service is that you were still relying on the shit infrastructure that the local telco had there. 8000 feet away from the DSLAM, on a trunk that has 90% utilization making for a shitload of crosstalk interference? Too bad. All the "choices" could still only deliver the same shitty 512k service because the equipment just couldn't do better without someone putting more lines on poles.
The 1-series and 3-series did have both 2-door and 4-door versions, and this was confusing in respect to where they were going with their numbering schemes.
Thus, the 2-series and 4-series were born as the 2-door versions of the 1-series and 3-series, respectively.
Want 4 doors? Get an odd-numbered first digit. 2 doors? Even.
Oh wow, I could be e-Popular for about 20 seconds on the Internet?!
I better go spend my life looking for something that may not exist!
What's really funny, is that if they would have marketed it as a 3.5GB card, and then people started to figure out that there was really 4GB of RAM on there, they probably would have gotten better sales of the part through the hardware hack community trying to figure out how to "unlock" it.
it's the same clock. The problem is bus width. 7/8ths of the memory is on an 7x wider bus than that last 1/8th. Thus, the performance loss.
No, just the throughput which is a function of clock * bus width.
You can have all the clock rate in the world, but still get shit performance on a 32-bit bus, which is exactly the problem.
The other effect is that Nvidia gets a nice fat punitive settlement levied against them, which acts as a deterrent from doing this crap again. I think that's the point.
You just gave a nice list of reasons why Apple might want to hire some competent battery engineers.
1. Absent internal knowledge
2. Current products have far lower energy density than other possible batteries
3. All gains currently employed are from software, and that's grown to maturity with diminishing returns setting in.
Yeah, I can't possibly think why they would want to hire some Ph. Ds that know battery technology and start working their own hardware.
Pretty much every car uses fuel injection now, because it is vastly superior in every meaningful way. Carburetors persisted for a while in motorcycle engines, but fuel injection is taking over that market too.
Even corporate dinosaurs that have legacy mainframe operations that go back decades are moving to VM clustering because of the inherent advantages. When I worked for one of these dinosaurs last year, I was walking through the mainframe operations group and someone had a thing printed on the side of her cube extolling that it would take 400 x86 servers to equal their S390. Someone from the VM engineering team had taken a sharpie to it and crossed out the "400 x86 servers" and written on "10 VMware hosts".
It seems that a lot of "big iron" people don't even recognize the existence of the inherent scalability advantages that VMs provide, even though their mainframes have been doing the same thing for decades.
and by "sold" you actually mean "given to with a fat stack of cash". IBM is paying GlobalFoundries to take the semiconductor fab business from IBM.
Yeah, the x86 stack doesn't need that kind of reliability, because of the inexpensiveness of the hardware. If you need that kind of uptime, you buy 3 and put them behind a load balancing scheme. You end up with more capacity, the same reliability, and still less expense. Especially in the world of virtualized server instances.
Thank Jeebus we have those boiling oceans to make clouds then, or we'd never get any precipitation.
Clearly, YOU do not know how evaporation works.