does denmark have any ties to other countries grids that use less renewables and if so does it end up effectively using them as batteries in much the same way that customers with net metering use thier countries grid as a battery?
but yes you bring up the biggest problem with renewables (other than dam based hydro), they generate when they wan't to generate not when the grid needs them to generate, as such they can reduce demand on conventional plants but they cannot easilly replace them.
Pumped storage could be used but iirc its frightfully expensive to install and its inefficiancy eats up a lot of the profits that could be made from time shifting the supply of electricity.
sooner or later countries are going to have to bite the bullet and start building efficiant (fast breeders and similar) nuclear power stations to take over the bulk of the demand.
No corporation can force me to give them my DNA. Sure they can, just get thier staff to point loaded rifles at you and i'm sure you'll comply. The only thing there is to stop them doing so is the government.
No corporation can jail me. once again the only reason corps don't imprison anyone is trouble from the govemenment
No corporation can force me to give them money. ditto
I retain my freedom to travel, speak, act, and so on outside the domain of the corporation with complete impunity, regardless of what they might want to do. so when the roads cartel of america that forms after the privitisation of the road network bans you from using thier roads you think there will be anything you can do about it?
it may be worth it for difficult to deploy applications but it will never be as responsive as a PC and will be totally useless if lots of people wan't heavy processing.
for the computer labs imaging combined with an auto deploment tool like the one from zenworks is probablly the best method.
For amdin staff just make an image with everything they need and depending on the severity of the problem either swap out the system drive (or reimage immedidiately if you can get the image size down to something where this is tolerable) or reimage them the following night depending on the severity of the problem.
I'd imagine one big reason for having pilots is in case you are forced to divert to somewhere that doesn't have the infrastructure for an automated landing.
you left out 02 and 3 in your list of real mobile networks.
i know the big 4 networks all have very good coverage nowadays.
3 are an interesting one. they are 3G only and they are still trying to grow thier buisness so they are cheap. I dunno what thier coverage is like though.
you contact people who know your distro but get no response. You contact the upstream of the peice of software in question and get back a canned "upgrade to x.y your distros version is ancient" response. So you don't have much choice but to move to the upstream version of the software.
If a software team can't make thier own stable releases decently stable and avoid breaking stuff too often there is something wrong with them!
foof and fdiv were particularlly nasty ones. foof because it meant a bad app could crash your system hard even if it had no special privilages. fdiv because it silently currupted results rather than simply causing a crash.
it's not like they're going to get an influx of problems to deal with because people sent their MacBook Pros to Krazy Klints Krazy Thermal Paste Removers, and had issues I can see at least three reasons
1: apple has long worked on the principle that some stuff on the lower end machines shouldn't be easilly upgraded (ibook hard drive for example). That way they sell more high end machines (powermacs and whatever there replacements will be) and more new low end machines (as people go in for replacements rather than upgrades).
2: like it or not people do destroy stuff themselves or get it destroyed by dodgy third partys and then try to pass it off as just failed to the manufacturer. Sometimes they get away with it.
We've actually done studies in this country that show people will sometimes resign themselves to a so-so tv show if the remote control is missing rather than get up and change channels until they find something better. it probably doesn't help that some kit is a real pita to operate without the remote.
our digital terrestrial (i'm in the uk) box for example has on the front only 3 buttons and a card slot. Sure you can get to any channel if your determined but its an absoloute pain to do so compared with using the remote ( with the front panel you have to go through the channels one by one in order waiting for each one to load before moving on, with the remote you can also bring up a menu or type in a channel number, this makes a big difference when most of the channels suck).
and its almost certain that it has several major kernel exploits unpatched.
its not long period running without updates thats the issue, its having to take down a macrokernel because something needs to be swapped out (e.g. for a security patch). There are ways to work arround this with linux (if its a module just unload it and replace it otherwise write a module to do in memory patching) but they are far from gauranteed to work (in particular i belive the module interface is rather picky about compiler versions matching)
However, some mistakes cannot be recovered from - for example, if you click the "yes" button on the "would you like to install this malware" dialogue. In this case you might be able to use journalling features of the filesystem to undo the damage, but if you've done other things since then you probably couldn't selectively roll back the filesystem changes associated with the malware without rolling back everything else too. you roll back the changes but keep the unrolled back state accessible to recover data from?
the problem is theres no usable security data on any filesystem other than one thats designed to fit with your operating systems security model. So granting access to users is something that must be decided by the OS at mount time.
windows takes the approach of "fat volumes are wide open to all users (a pretty major security hole really)" linux takes the opposite approach of "you can't write a non-native filesystem unless root lets you".
The truth is that according to Newton's law of universal gravitation, the hammer and the feather fall to the ground at different rates. the truth is that newtons laws are just approximations of reality that happen to give good enough results in most situations.
just how many significant figures are newtons "laws" known to be correct to in situations like that? i bet its nowhere near enough to answer the question of which will hit first.
whats worse is you simply can't know whats flowing over those sftp links. Is it porn or is it work he did last night and forgot to put on his flash stick?
The lowest levels of employees can often be cut off from the outside world entirely but once you get beyond that to people who actually have to solve problems and create things or are expected to work from home and therefore need outside communication for work (e.g. to obtain datasheets, request samples, look for other people who have hit similar problems etc) you don't have much choice but to put some trust in them.
I'm sure the Open Source community could throw together something writing the software is easy.
whats hard is writing the rulesets. screw up with your interpretations of the tax law and your customers (and possiblly you depending on just how enforceable that no-liability clause really turns out to be in your country) could get in serious trouble.
I'd imagine with commercial tax software you are mainly paying for two things 1: lawyer time to write/check the rulesets 2: insurance in case they screw up writing the rulesets
the correct thing would of course be for the government to provide the tax rules in an unambiguous machine parseable format. but there are sufficiant vested interests that its unlikely that will happen in most countries.
The number of pixel defects is proportional to the area of the display and density of pixels.
on the other hand the greater the pixel density the less noticable dead pixels will be.
when we reach 300dpi or so i suspect most people will stop caring about dead pixels as they will be invisible anyway. Unfortunately this will require a paradigm shift in software development. Traditionally UI elements have been measured in pixels because the pixel size has been what limits how small you can make stuff and keep it readable, high DPI will change that big time and once again apple will probablly lead that revoloution (remember the talk of changing webkit so 1 css pixel=2x2 real pixels a while back?) just like they did with dual link DVI.
that may work for video (assuming the hardware could do the decompression or the video was relatively low quality, e.g. 640*480*32*30=294,912,000bps=within normal firewire's abilities just about) and for your GUI desktop but for gaming i doubt firewire would be sufficiant. even firewire 800 (which is still pretty rare) is slower than standard PCI!
point is unless you are doing fairly low load operations only you really don't save anything by piping graphics card level commands over the bus rather than pumping a framebuffer over the bus. Youd need a specialist bus either way.
imagine what the shitstorm is going to be like when people realise they're messing with TV! i remember sky here in the uk introduced macrovison when they introduced sky digital but there was so much bad press (and remember sky have to compete with cablecos etc) that they turned it off for thier normal channels (they still use it on pay per view i belive).
however say 1% of your workforce are people who actually need to use formulae to express what thier doing (IE are mathematicians or true engineers of some sort) and the facilities for doing so in oo.o are considered inadequate.
you either have to deploy ms office everywhere or live with the huge pain of multiple almost but not quite compatible office suites. Much the same thing happens with different versions of office itself in fact.
Slashdot Mirror
does denmark have any ties to other countries grids that use less renewables and if so does it end up effectively using them as batteries in much the same way that customers with net metering use thier countries grid as a battery?
but yes you bring up the biggest problem with renewables (other than dam based hydro), they generate when they wan't to generate not when the grid needs them to generate, as such they can reduce demand on conventional plants but they cannot easilly replace them.
Pumped storage could be used but iirc its frightfully expensive to install and its inefficiancy eats up a lot of the profits that could be made from time shifting the supply of electricity.
sooner or later countries are going to have to bite the bullet and start building efficiant (fast breeders and similar) nuclear power stations to take over the bulk of the demand.
imo porting windows-mac universal binary should be easier than porting windows-mac powerpc without using an intel mac.
If you port windows->intel mac->powerpc mac then you can seperate out troubleshooting the mac issues from troubleshooting the endian issues.
well if they seized the assets then they could opensource them if continued availibility was a concern.
No corporation can force me to give them my DNA.
Sure they can, just get thier staff to point loaded rifles at you and i'm sure you'll comply. The only thing there is to stop them doing so is the government.
No corporation can jail me.
once again the only reason corps don't imprison anyone is trouble from the govemenment
No corporation can force me to give them money.
ditto
I retain my freedom to travel, speak, act, and so on outside the domain of the corporation with complete impunity, regardless of what they might want to do.
so when the roads cartel of america that forms after the privitisation of the road network bans you from using thier roads you think there will be anything you can do about it?
it may be worth it for difficult to deploy applications but it will never be as responsive as a PC and will be totally useless if lots of people wan't heavy processing.
for the computer labs imaging combined with an auto deploment tool like the one from zenworks is probablly the best method.
For amdin staff just make an image with everything they need and depending on the severity of the problem either swap out the system drive (or reimage immedidiately if you can get the image size down to something where this is tolerable) or reimage them the following night depending on the severity of the problem.
is whitelisting and thats generally unfeasible.
once someone has a link to a friendly box on the outside there isn't much you can do to stop them bouncing off it to any site they like.
I'd imagine one big reason for having pilots is in case you are forced to divert to somewhere that doesn't have the infrastructure for an automated landing.
you left out 02 and 3 in your list of real mobile networks.
i know the big 4 networks all have very good coverage nowadays.
3 are an interesting one. they are 3G only and they are still trying to grow thier buisness so they are cheap. I dunno what thier coverage is like though.
was that they were afraid of getting thier windows trademark invalidated as part of the case.
ofc MS then used the other tactic rich multinationals use on less rich multinationals. They hit them with lawsuits in other countries.
I'm pretty sure i've seen both lego and duplo bricks with printed smiley faces. I don't know when they were introduced though.
right then a feature you require doesn't work.
you contact people who know your distro but get no response. You contact the upstream of the peice of software in question and get back a canned "upgrade to x.y your distros version is ancient" response. So you don't have much choice but to move to the upstream version of the software.
If a software team can't make thier own stable releases decently stable and avoid breaking stuff too often there is something wrong with them!
foof and fdiv were particularlly nasty ones. foof because it meant a bad app could crash your system hard even if it had no special privilages. fdiv because it silently currupted results rather than simply causing a crash.
are any of the core solo/duo ones that bad?
it's not like they're going to get an influx of problems to deal with because people sent their MacBook Pros to Krazy Klints Krazy Thermal Paste Removers, and had issues
I can see at least three reasons
1: apple has long worked on the principle that some stuff on the lower end machines shouldn't be easilly upgraded (ibook hard drive for example). That way they sell more high end machines (powermacs and whatever there replacements will be) and more new low end machines (as people go in for replacements rather than upgrades).
2: like it or not people do destroy stuff themselves or get it destroyed by dodgy third partys and then try to pass it off as just failed to the manufacturer. Sometimes they get away with it.
3: more money for offical service centers.
We've actually done studies in this country that show people will sometimes resign themselves to a so-so tv show if the remote control is missing rather than get up and change channels until they find something better.
it probably doesn't help that some kit is a real pita to operate without the remote.
our digital terrestrial (i'm in the uk) box for example has on the front only 3 buttons and a card slot. Sure you can get to any channel if your determined but its an absoloute pain to do so compared with using the remote ( with the front panel you have to go through the channels one by one in order waiting for each one to load before moving on, with the remote you can also bring up a menu or type in a channel number, this makes a big difference when most of the channels suck).
and its almost certain that it has several major kernel exploits unpatched.
its not long period running without updates thats the issue, its having to take down a macrokernel because something needs to be swapped out (e.g. for a security patch). There are ways to work arround this with linux (if its a module just unload it and replace it otherwise write a module to do in memory patching) but they are far from gauranteed to work (in particular i belive the module interface is rather picky about compiler versions matching)
However, some mistakes cannot be recovered from - for example, if you click the "yes" button on the "would you like to install this malware" dialogue. In this case you might be able to use journalling features of the filesystem to undo the damage, but if you've done other things since then you probably couldn't selectively roll back the filesystem changes associated with the malware without rolling back everything else too.
you roll back the changes but keep the unrolled back state accessible to recover data from?
the problem is theres no usable security data on any filesystem other than one thats designed to fit with your operating systems security model. So granting access to users is something that must be decided by the OS at mount time.
windows takes the approach of "fat volumes are wide open to all users (a pretty major security hole really)" linux takes the opposite approach of "you can't write a non-native filesystem unless root lets you".
The truth is that according to Newton's law of universal gravitation, the hammer and the feather fall to the ground at different rates.
the truth is that newtons laws are just approximations of reality that happen to give good enough results in most situations.
just how many significant figures are newtons "laws" known to be correct to in situations like that? i bet its nowhere near enough to answer the question of which will hit first.
whats worse is you simply can't know whats flowing over those sftp links. Is it porn or is it work he did last night and forgot to put on his flash stick?
The lowest levels of employees can often be cut off from the outside world entirely but once you get beyond that to people who actually have to solve problems and create things or are expected to work from home and therefore need outside communication for work (e.g. to obtain datasheets, request samples, look for other people who have hit similar problems etc) you don't have much choice but to put some trust in them.
I'm sure the Open Source community could throw together something
writing the software is easy.
whats hard is writing the rulesets. screw up with your interpretations of the tax law and your customers (and possiblly you depending on just how enforceable that no-liability clause really turns out to be in your country) could get in serious trouble.
I'd imagine with commercial tax software you are mainly paying for two things
1: lawyer time to write/check the rulesets
2: insurance in case they screw up writing the rulesets
the correct thing would of course be for the government to provide the tax rules in an unambiguous machine parseable format. but there are sufficiant vested interests that its unlikely that will happen in most countries.
The number of pixel defects is proportional to the area of the display and density of pixels.
on the other hand the greater the pixel density the less noticable dead pixels will be.
when we reach 300dpi or so i suspect most people will stop caring about dead pixels as they will be invisible anyway. Unfortunately this will require a paradigm shift in software development. Traditionally UI elements have been measured in pixels because the pixel size has been what limits how small you can make stuff and keep it readable, high DPI will change that big time and once again apple will probablly lead that revoloution (remember the talk of changing webkit so 1 css pixel=2x2 real pixels a while back?) just like they did with dual link DVI.
that may work for video (assuming the hardware could do the decompression or the video was relatively low quality, e.g. 640*480*32*30=294,912,000bps=within normal firewire's abilities just about) and for your GUI desktop but for gaming i doubt firewire would be sufficiant. even firewire 800 (which is still pretty rare) is slower than standard PCI!
point is unless you are doing fairly low load operations only you really don't save anything by piping graphics card level commands over the bus rather than pumping a framebuffer over the bus. Youd need a specialist bus either way.
imagine what the shitstorm is going to be like when people realise they're messing with TV!
i remember sky here in the uk introduced macrovison when they introduced sky digital but there was so much bad press (and remember sky have to compete with cablecos etc) that they turned it off for thier normal channels (they still use it on pay per view i belive).
however say 1% of your workforce are people who actually need to use formulae to express what thier doing (IE are mathematicians or true engineers of some sort) and the facilities for doing so in oo.o are considered inadequate.
you either have to deploy ms office everywhere or live with the huge pain of multiple almost but not quite compatible office suites. Much the same thing happens with different versions of office itself in fact.
if you can so so then its a good idea to develop on a dual CPU box. That way you will catch bugs much much earlier.