Uhhh... Chernobyl dissipated all the heat in its reactors in real time while running... That's the whole point of a nuclear reactor. The issue comes when cooling is shut off to the reactors, and the heat is allowed to build up.
With fission (at least with 50s designs), that's a major problem, because you can't just turn it off. With fusion, it's not a problem at all, because you simply stop providing fuel to the reaction and it'll shut down immediately. Getting fusion reactions *not* to shut down is the problem being faced at the moment.
OpenGL has a bunch of implicit locks and blocking operations that do not need to be blocking. For example, if you have a font atlas, and you know that for frame 1, you only need to be able to access the glyphs for 'a', 'n' and 'd', but for frame 2, you know you'll also need 'y', 'u' and 'o', frame 2's texture upload would block any draw calls from accessing the texture (or it would block until those draw calls had completed). There is no way to avoid this in OpenGL, even if you yourself have knowledge that you are not going to modify anything that the shader will read.
Believe it or not, the world of graphics hardware and APIs has moved on substantially since 1999. What was a good API design then, is now far from it. These days, you can get an order of magnitude speed improvement from two major API changes from the current OpenGL one: 1) Drop the state machine, and require states to be specified (and hence verified, and compiled) up front, rather than via a series of changes during drawing. 2) Drop the inbuilt thread safety, and require the users of the API to implement correct thread safety themselves.
These two changes together make a very very significant difference to the performance you can get out of a CPU/GPU pair. There's a very good reason why Microsoft went that way with D3D, Apple went that way with Metal, AMD went that way with Mantle, and now Kronos is going that way with Vulkan.
The use for this is clearly not for you but for the car. Once the car is self driving, this will allow it to run off down the street, find a charging station, and plug itself in while it waits for you to need it again.
Sorry, I think I failed at expressing my point. My point was that once you're wearing shorts, (T-)shirt, and not much else, you can't reasonably take anything off without (rightly) incurring HR's wrath.
If HR are being wrathful to you for not wearing a suit jacket, then clearly that's over-zealous. If HR are being wrathful to you for not wearing clothes at all... that's probably not so much of an issue. The temperature however... is.
No, fraid not. In case you haven't noticed, the dress code in the IT industry is already very informal. There's still plenty of us who want it cooler than 72F.
Or, better yet, set the HVAC to 68F, and let people control how open the vent is.
The multiple computers in their room will happily warm the place up to well above 68 (and in fact, probably to the 80 that the most warm loving person likes), meanwhile, those who like it cool, can quite happily get on with their job.
No, it's because I'm from a country where 30C is an exceptional temperature (if it's ever reached).
I'm comfortable anywhere between 15C and 20C, because that's a fairly normal outdoor temperature where I'm from (though outliers could be anywhere from -20C to 35C).
Actually, regular coffee-machine discussions in our office suggest that I'm not an outlier for men at all. I'm on the low end for sure, but not outside one standard deviation below average for sure.
It's not really old data, it's just that the modern author hasn't considered the practicalities of the situation.
Offices *still* have 40 year old men (and 20 year old ones, and 50 year old ones) in them, it just happens they have a bunch of women too. Those men can not remove clothes to become cooler without incurring the wrath of HR (quite rightly). Those women can add clothes to solve being too cold. Simply averaging the temperature people want the office to be set to does not make everyone comfortable, it just makes a bunch of mean sweaty and sleepy, with no way to correct for it.
The thing is, those tiny little 4 bangers turn out not to be any more efficient than the decently sized ones (though substantially better than most V6/V8s).
All that changes is that the guy driving the little 1.1l 4 banger floors it all the time, because he needs all its got all the time; while the guy driving the 1.8T just uses a tiny bit of what's available.
Typical shotgun spread is around 0.5" per yard. Some are as low as 0.3" per yard. So the spread at 200ft is going to be around 20" across. A drone is also about 20" across. So if the shot was good, it's highly likely that almost all of the pellets would hit the drone.
I do think there are important differences with computers though
Computers can potentially be much more efficient and accurate in their slaughter. Such machines may be used in ways not unlike hitler used gas chambers (wooo, godwin there we go).
With current technology, computers can't make morality judgements like humans can, they can't think "you know what, my general just ordered a genocide, I'm not going to take part".
With current technology, computers are much worse at distinguishing friend, foe or civilian. We ban land mines for exactly this reason - they don't distinguish who they're blowing up.
There's probably more reasons that they differ, but I can't be arsed thinking them up just now.
Current charge times make "recharge when the driver stops for breaks" impossible.
Not really, no. Current charge rates mean you can get about 100 miles of range in 20 minutes on a standard DC charger. If you're a tesla owner that's more like 200 miles of range in 20 minutes.
Big rigs typically get in the range of 8-10mpg, so they're roughly 4 times less efficient than cars. That implies that you could get about 50 miles for 20 minutes of charging on a tech similar to tesla's. Big rig drivers are required to take 10 hours of break in every 21. That 10 hours is enough to add 1500 miles of range, 11 hours is enough to drive roughly 770 miles.
It seems like even with Tesla's current DC charging tech there's *more* than enough ability to charge a big rig for all its current driving time.
But anyone sane on the planet would rather have them sit a car in a large, private, open space and demonstrate that they can control all of the controls without endangering anyone's life, especially people who didn't sign up to have their life endangered and were just driving down a public road.
Uhhhh? Do you somehow think that making a function private in the source code means that it's impossible to jump to that location at runtime? That's really not how it works.
Prison is meant to be reserved for separating people from society who are dangerous until they're not dangerous any more.
The correct sentence for copyright infringement (which does not demonstrate that the perpetrator is a danger to others), is to 1) pay back the person who was wronged (though that's a civil matter), and 2) a fine or community service of some sort.
Slashdot Mirror
Uhhh... Chernobyl dissipated all the heat in its reactors in real time while running... That's the whole point of a nuclear reactor. The issue comes when cooling is shut off to the reactors, and the heat is allowed to build up.
With fission (at least with 50s designs), that's a major problem, because you can't just turn it off.
With fusion, it's not a problem at all, because you simply stop providing fuel to the reaction and it'll shut down immediately. Getting fusion reactions *not* to shut down is the problem being faced at the moment.
OpenGL has a bunch of implicit locks and blocking operations that do not need to be blocking. For example, if you have a font atlas, and you know that for frame 1, you only need to be able to access the glyphs for 'a', 'n' and 'd', but for frame 2, you know you'll also need 'y', 'u' and 'o', frame 2's texture upload would block any draw calls from accessing the texture (or it would block until those draw calls had completed). There is no way to avoid this in OpenGL, even if you yourself have knowledge that you are not going to modify anything that the shader will read.
Believe it or not, the world of graphics hardware and APIs has moved on substantially since 1999. What was a good API design then, is now far from it. These days, you can get an order of magnitude speed improvement from two major API changes from the current OpenGL one:
1) Drop the state machine, and require states to be specified (and hence verified, and compiled) up front, rather than via a series of changes during drawing.
2) Drop the inbuilt thread safety, and require the users of the API to implement correct thread safety themselves.
These two changes together make a very very significant difference to the performance you can get out of a CPU/GPU pair. There's a very good reason why Microsoft went that way with D3D, Apple went that way with Metal, AMD went that way with Mantle, and now Kronos is going that way with Vulkan.
Because that would be entrapment.
But a baseball and a rock are both much heavier than a paint ball.
I know the fahrenheit scale makes it somewhat hard to tell, but last I checked, 72F was significantly above the freezing point of water.
The use for this is clearly not for you but for the car. Once the car is self driving, this will allow it to run off down the street, find a charging station, and plug itself in while it waits for you to need it again.
Sorry, I think I failed at expressing my point. My point was that once you're wearing shorts, (T-)shirt, and not much else, you can't reasonably take anything off without (rightly) incurring HR's wrath.
If HR are being wrathful to you for not wearing a suit jacket, then clearly that's over-zealous. If HR are being wrathful to you for not wearing clothes at all... that's probably not so much of an issue. The temperature however... is.
No, fraid not. In case you haven't noticed, the dress code in the IT industry is already very informal. There's still plenty of us who want it cooler than 72F.
Or, better yet, set the HVAC to 68F, and let people control how open the vent is.
The multiple computers in their room will happily warm the place up to well above 68 (and in fact, probably to the 80 that the most warm loving person likes), meanwhile, those who like it cool, can quite happily get on with their job.
No, it's because I'm from a country where 30C is an exceptional temperature (if it's ever reached).
I'm comfortable anywhere between 15C and 20C, because that's a fairly normal outdoor temperature where I'm from (though outliers could be anywhere from -20C to 35C).
Actually, regular coffee-machine discussions in our office suggest that I'm not an outlier for men at all. I'm on the low end for sure, but not outside one standard deviation below average for sure.
Speaking as a man... 21C is too warm for me. 24C will have me sitting there dripping sweat even if naked.
It's not really old data, it's just that the modern author hasn't considered the practicalities of the situation.
Offices *still* have 40 year old men (and 20 year old ones, and 50 year old ones) in them, it just happens they have a bunch of women too. Those men can not remove clothes to become cooler without incurring the wrath of HR (quite rightly). Those women can add clothes to solve being too cold. Simply averaging the temperature people want the office to be set to does not make everyone comfortable, it just makes a bunch of mean sweaty and sleepy, with no way to correct for it.
The thing is, those tiny little 4 bangers turn out not to be any more efficient than the decently sized ones (though substantially better than most V6/V8s).
All that changes is that the guy driving the little 1.1l 4 banger floors it all the time, because he needs all its got all the time; while the guy driving the 1.8T just uses a tiny bit of what's available.
Typical shotgun spread is around 0.5" per yard. Some are as low as 0.3" per yard. So the spread at 200ft is going to be around 20" across. A drone is also about 20" across. So if the shot was good, it's highly likely that almost all of the pellets would hit the drone.
I do think there are important differences with computers though
Computers can potentially be much more efficient and accurate in their slaughter. Such machines may be used in ways not unlike hitler used gas chambers (wooo, godwin there we go).
With current technology, computers can't make morality judgements like humans can, they can't think "you know what, my general just ordered a genocide, I'm not going to take part".
With current technology, computers are much worse at distinguishing friend, foe or civilian. We ban land mines for exactly this reason - they don't distinguish who they're blowing up.
There's probably more reasons that they differ, but I can't be arsed thinking them up just now.
Current charge times make "recharge when the driver stops for breaks" impossible.
Not really, no. Current charge rates mean you can get about 100 miles of range in 20 minutes on a standard DC charger. If you're a tesla owner that's more like 200 miles of range in 20 minutes.
Big rigs typically get in the range of 8-10mpg, so they're roughly 4 times less efficient than cars. That implies that you could get about 50 miles for 20 minutes of charging on a tech similar to tesla's. Big rig drivers are required to take 10 hours of break in every 21. That 10 hours is enough to add 1500 miles of range, 11 hours is enough to drive roughly 770 miles.
It seems like even with Tesla's current DC charging tech there's *more* than enough ability to charge a big rig for all its current driving time.
That depends entirely on whether the item was designed to withstand people attacking it.
A bomb shelter is defective if someone drops a bomb on it (at the designed distance and explosive power) and it collapses.
A skyscraper is defective if it was designed to withstand a plane impact and it does not.
A car is defective if it was designed to withstand people trying to hack it, and it doesn't.
A car's design is defective if it was not designed to withstand people trying to hack it.
So you're saying it had a defect (the ability to exploit it), but it wasn't defective?
In general, companies don't tend to know about significant defects when they actually ship the item. That doesn't mean that they're not defects.
But anyone sane on the planet would rather have them sit a car in a large, private, open space and demonstrate that they can control all of the controls without endangering anyone's life, especially people who didn't sign up to have their life endangered and were just driving down a public road.
Uhhhh? Do you somehow think that making a function private in the source code means that it's impossible to jump to that location at runtime? That's really not how it works.
Prison is meant to be reserved for separating people from society who are dangerous until they're not dangerous any more.
The correct sentence for copyright infringement (which does not demonstrate that the perpetrator is a danger to others), is to 1) pay back the person who was wronged (though that's a civil matter), and 2) a fine or community service of some sort.
Are you saying that you don't need to eat food roughly every 4 waking hours?
Yes, yes it does.