The problem is since they switched to the new ajax interface they even fail at stuff from latin1 (at least if entered directly, a handfull of html entities for latin1 stuff work).
I don't think the issue with lots of windows on 9x was a multitasking issue per-se (afaict the issue would happen regardless of whether all the windows were created by the same app/thread or not) but an issue with win9x still relying on some 16-bit GDI stuff and running out of GDI resources.
I just don't get the point of activation in VLK editions. The BSA will rip a business to component atoms who is caught pirating, so activation doesn't ensure MS gets any more revenue than it does already in the business sector. MS learnt with XP that if they release a no activation required version for some subset of customers (in the XP case volume license ones) then it WILL get leaked and the pirates WILL use it to avoid activation. They can put a key on the WGA shitlist but not everyone installs WGA and they can only do that for keys they know are in widespread illicit use.
As I see it the main point of activation in windows vista/7 volume license editions is to make it harder/riskier (if MAK activations start getting used up unexpectedly quickly someone is going to start asking questions) for people to "borrow" thier employers key to use on thier private machine(s) and possiblly thier friends machines.
MS ported most of the important stuff (plug and play and support for a common driver model between the two lines to help hardware manufacturs transition) to the NT line with 2K but bottled out of pushing 2K to home/small buisness users and produced another version of the 9x line instead.
So when ME flopped it wasn't a huge deal, they just added a home edition to the next minor release of the NT line and scrapped 9x. While 2K/XP was slower than 9x it was a noticable improvement in terms of both stability and ability to handle lots of windows open at once.
Would retailers want to carry it anyway? It sounds like a returns nightmare when people realise after the fact that all they have is an expensive CDR and some artwork.
Probablly not that much harder, as I see it there are two main issues
1: getting bulbs the right colors for a good RGB mix. In particular you want quite high saturation colors (close to pure spectrals) which means more loss in the coloring. 2: you would have to design the control boards to be able to dim rather than just switch (using commercial stage dimmer packs would probablly be probibitively expensive).
that aren't really needed if you know what you're doing. Then either the majority of coders don't know what they are doing or even coders who do know what they are doing make mistakes occasionally (especially when tierd under pressure or similar).
The fact is problems related to manual memory managements and bounds checking are among the most common types of security alert. Can you name a large and popular peice of software written in C that has never had a buffer overflow.
operator abuse seems to be an integral part of C++ style. Hell even the standard library does it ( auto_ptr, streams and possiblly strings depending on your view on whether string concatenation is close enough to addition).
To understand whey lets consider why operators exist in the first place, "n=a+b+c+d+e" is a lot easier to read than "assign(n,add(a,add(b,add(c,add(d,e)))))". C++ doesn't let the coder create new operators (something mathematicians do on a regular basis) so the designer of a new type that could really do with a new operator is left with either using functions/methods (which leads to cluttered code in callers) or abusing an existing operator (which can lead to confusion).
Letting coders create there own operators would be a nice (though possiblly problematic) feature for a language.
It certainly is mathematics and it's not that hard to understand either. basically it is the mathematical equivilent of what a hard field tomograph does.
Consider a function of two values and consider those values to be 2D coordinates. Consider also that the function is zero outside of a defined area.
Now consider that there are an infiniate number infinitely long number of straight lines passing through that area and each can be defined by two parameters, an angle and an offset from the orgin in the direction perpendicular to the line.
Along each of those lines an integral can be calculated. those integrals form the radon transform of the function (with each integral being identified by the two parameters).
Not really that complicated, the trickiest bit is probablly deciding how best to approximate the line integrals from your limited number of data points.
Firstly your code can always throw any descendent of error or runtimeexception regardless of it's declared throws. How many times have you seen something like.
try {
some code } catch (someexception e) {
throw new RuntimeException(e); }
still I guess it's better than try {
some code } catch (someexception e) { }
P.S, there is actually a way mentioned in suns own documentation to throw any exception you wish regardless of your throws specifier.
It's more likely that programmers will just pass len to both parameters, defeating the point Which should be slapped down in code review.
As I see it the point of theese functions is to introduce a layer of sanity checking that is relatively independent of the main data/control flow and hence much easier to check correctness of come code review time.
How hard is it to automatically translate C code to, say, C++/CLI? It's certainly doable for C and I can't see any reason why it wouldn't be for C++ too (though writing a correct C++ compiler targetting anything is a PITA afaict)
One thing I do find interesting is their benchmark results. translating C to java using thier tool (which is probablly not optimal) brings a pretty substantial performance penalty but the penalty for converting to java is far lower than the penalty for converting to any of the other managed languages they support.
1: send C&D letters/takedown notices to any pirate sites that come up higher than the sites selling the book in the search results. 2: If at all possible (e.g. publisher contracts permit) make sure you offer an official ebook that is at least as good as and prefferablly better than what the pirates are offering (that means drm free and a good selection of formats). 3: search for reviews of your book and try and encourage them to link to a place it can actaully be purchased and/or post such a link in thier comments.
desks and computers and paperwork and power and internet are already largely paid for I dunno how it works in australia but my understanding is in the UK whenever a university takes a research contract as well as the money allocated for specific things the university always adds on an ammount of "overhead" to help cover the general overheads of running the university.
The trouble with CD-RW is the software. When burners first came down to consumer price points they tended to come with easy CD creater and directcd so you could use them like removable media. Then at some point virtually all the burner manufacturers switched to nero burning rom and usually did not bundle incd (nero's alternative to directcd). And even if they did bundle incd afaict directcd and incd were not compatible with each other.
With the bundled software being burner locked and many users being too tight to buy burning software at full price packet writing virtually dissapeared. Having to load special burning software every time you wanted to write something and having to periodically wipe and rewrite to clear wasted space is a PITA.
What they do however do (and did to an even greater extent a few years ago with the whole super-size thing) is push oversized portions of fries and pop (presumablly because both are cheap). Even in a medium big mac meal the fries and coca-cola account for more than half the total calories and in a large meal the fries alone are as high as the big-mac itself.
Then there are the milkshakes which are offered for a slight extra charge with the meals and really bump up the calorie count.........
A MiTM attack can't work unless the attacker has a valid cert, if they do, then what does it matter where you connect from? A MiTM attack on a https connection requires two things
1: the ability to actually insert themselves in the middle of your communications link 2: a ssl cert that the browser will accept for the domain you are trying to get to.
Unfortunately history has shown that getting the second of theese two requirements is far from impossible, so it makes sense to try and avoid situations that make the first of them easy.
So, how are they like floppies? They can be read and written directly from applications (in the same way as a hard drive or network driver) on the majority of pcs without needing any additonal software or hardware and they are small enough to easilly carry arround.
That combination of features is IMO what has allowed USB sticks to replace floppies where everything else failed to do so.
The superfloppies (zip, LS120, HIFD etc) remained niche products because of reliability issues and the fact that none of them could never get the drives widespread enough (yeah you could cart arround the drive and a CD of drivers for the drive but that kinda reduced the portability). CD-RW got the hardware widely distributed but unfortunately burner manufacturers stopped shipping directcd and in doing so largely killed off "packet writing".
While what you say is true, is also true that franchises make differences when it comes to locations, just look at the menues of McDonalds in different countries. Afaict mcdonalds gives far more freedom to it's international subsidaries than is given to franchises within a country.
I thought their usual backup was to go to the ISS in case of damage Afaict other than this hubble mission all the shuttle missions since columbia have been going to the ISS anyway. I think the plan is to stay docked with the ISS until just before the rescue mission arrives, then move everyone to the space station and dump the damaged orbiter so the rescue mission can dock.
but they can't because they are in the wrong orbit for that in order to service Hubble. Right, hubble and the ISS are in totally different orbits, moving from one to the other would take far more delta-v than is availible.
The reason a rescue mission is on standby is there are "higher amounts of space debris in Hubble's orbit". I doubt it. Afaict the shuttle on standby plan was being developed long before the "higher ammount of space debris" issue came up.
NASA is paranoid about a repeat of columbia. As such they have put in place an inspection routine for all shuttle missions and a plan for what to do if the inspection finds damage too big to safely land with.
For most missions they just plan to stay on the ISS until evacuation can be arranged but that isn't practical for a hubble servicing mission so a standby is needed.
My understanding was that 64-bit wine could only run 64 bit windows binaries. So if you wanted to run either 16-bit or 32-bit binaries you needed a 32-bit wine.
The problem is since they switched to the new ajax interface they even fail at stuff from latin1 (at least if entered directly, a handfull of html entities for latin1 stuff work).
I don't think the issue with lots of windows on 9x was a multitasking issue per-se (afaict the issue would happen regardless of whether all the windows were created by the same app/thread or not) but an issue with win9x still relying on some 16-bit GDI stuff and running out of GDI resources.
I just don't get the point of activation in VLK editions. The BSA will rip a business to component atoms who is caught pirating, so activation doesn't ensure MS gets any more revenue than it does already in the business sector.
MS learnt with XP that if they release a no activation required version for some subset of customers (in the XP case volume license ones) then it WILL get leaked and the pirates WILL use it to avoid activation. They can put a key on the WGA shitlist but not everyone installs WGA and they can only do that for keys they know are in widespread illicit use.
As I see it the main point of activation in windows vista/7 volume license editions is to make it harder/riskier (if MAK activations start getting used up unexpectedly quickly someone is going to start asking questions) for people to "borrow" thier employers key to use on thier private machine(s) and possiblly thier friends machines.
MS ported most of the important stuff (plug and play and support for a common driver model between the two lines to help hardware manufacturs transition) to the NT line with 2K but bottled out of pushing 2K to home/small buisness users and produced another version of the 9x line instead.
So when ME flopped it wasn't a huge deal, they just added a home edition to the next minor release of the NT line and scrapped 9x. While 2K/XP was slower than 9x it was a noticable improvement in terms of both stability and ability to handle lots of windows open at once.
Would retailers want to carry it anyway? It sounds like a returns nightmare when people realise after the fact that all they have is an expensive CDR and some artwork.
Probablly not that much harder, as I see it there are two main issues
1: getting bulbs the right colors for a good RGB mix. In particular you want quite high saturation colors (close to pure spectrals) which means more loss in the coloring.
2: you would have to design the control boards to be able to dim rather than just switch (using commercial stage dimmer packs would probablly be probibitively expensive).
On that note has anyone tried the option on google books to report unreadable pages and if so do they do anything about it?
that aren't really needed if you know what you're doing.
Then either the majority of coders don't know what they are doing or even coders who do know what they are doing make mistakes occasionally (especially when tierd under pressure or similar).
The fact is problems related to manual memory managements and bounds checking are among the most common types of security alert. Can you name a large and popular peice of software written in C that has never had a buffer overflow.
operator abuse seems to be an integral part of C++ style. Hell even the standard library does it ( auto_ptr, streams and possiblly strings depending on your view on whether string concatenation is close enough to addition).
To understand whey lets consider why operators exist in the first place, "n=a+b+c+d+e" is a lot easier to read than "assign(n,add(a,add(b,add(c,add(d,e)))))". C++ doesn't let the coder create new operators (something mathematicians do on a regular basis) so the designer of a new type that could really do with a new operator is left with either using functions/methods (which leads to cluttered code in callers) or abusing an existing operator (which can lead to confusion).
Letting coders create there own operators would be a nice (though possiblly problematic) feature for a language.
It certainly is mathematics and it's not that hard to understand either. basically it is the mathematical equivilent of what a hard field tomograph does.
Consider a function of two values and consider those values to be 2D coordinates. Consider also that the function is zero outside of a defined area.
Now consider that there are an infiniate number infinitely long number of straight lines passing through that area and each can be defined by two parameters, an angle and an offset from the orgin in the direction perpendicular to the line.
Along each of those lines an integral can be calculated. those integrals form the radon transform of the function (with each integral being identified by the two parameters).
Not really that complicated, the trickiest bit is probablly deciding how best to approximate the line integrals from your limited number of data points.
The seperate page post form allows direct submission (provided you aren't AC) but the inline ajax based box requires you to preview.
Especially with that shiny new patent.
Couldn't they just build and operate the scanner somewhere outside the patents coverage area?
and even exception definitions.
Only very weakly.
Firstly your code can always throw any descendent of error or runtimeexception regardless of it's declared throws. How many times have you seen something like.
try {
some code
} catch (someexception e) {
throw new RuntimeException(e);
}
still I guess it's better than
try {
some code
} catch (someexception e) { }
P.S, there is actually a way mentioned in suns own documentation to throw any exception you wish regardless of your throws specifier.
It's more likely that programmers will just pass len to both parameters, defeating the point
Which should be slapped down in code review.
As I see it the point of theese functions is to introduce a layer of sanity checking that is relatively independent of the main data/control flow and hence much easier to check correctness of come code review time.
How hard is it to automatically translate C code to, say, C++/CLI?
It's certainly doable for C and I can't see any reason why it wouldn't be for C++ too (though writing a correct C++ compiler targetting anything is a PITA afaict)
http://cluecc.sourceforge.net/
One thing I do find interesting is their benchmark results. translating C to java using thier tool (which is probablly not optimal) brings a pretty substantial performance penalty but the penalty for converting to java is far lower than the penalty for converting to any of the other managed languages they support.
Personally I'd take a few approaches in paralell
1: send C&D letters/takedown notices to any pirate sites that come up higher than the sites selling the book in the search results.
2: If at all possible (e.g. publisher contracts permit) make sure you offer an official ebook that is at least as good as and prefferablly better than what the pirates are offering (that means drm free and a good selection of formats).
3: search for reviews of your book and try and encourage them to link to a place it can actaully be purchased and/or post such a link in thier comments.
desks and computers and paperwork and power and internet are already largely paid for
I dunno how it works in australia but my understanding is in the UK whenever a university takes a research contract as well as the money allocated for specific things the university always adds on an ammount of "overhead" to help cover the general overheads of running the university.
The trouble with CD-RW is the software. When burners first came down to consumer price points they tended to come with easy CD creater and directcd so you could use them like removable media. Then at some point virtually all the burner manufacturers switched to nero burning rom and usually did not bundle incd (nero's alternative to directcd). And even if they did bundle incd afaict directcd and incd were not compatible with each other.
With the bundled software being burner locked and many users being too tight to buy burning software at full price packet writing virtually dissapeared. Having to load special burning software every time you wanted to write something and having to periodically wipe and rewrite to clear wasted space is a PITA.
What they do however do (and did to an even greater extent a few years ago with the whole super-size thing) is push oversized portions of fries and pop (presumablly because both are cheap). Even in a medium big mac meal the fries and coca-cola account for more than half the total calories and in a large meal the fries alone are as high as the big-mac itself.
Then there are the milkshakes which are offered for a slight extra charge with the meals and really bump up the calorie count.........
A MiTM attack can't work unless the attacker has a valid cert, if they do, then what does it matter where you connect from?
A MiTM attack on a https connection requires two things
1: the ability to actually insert themselves in the middle of your communications link
2: a ssl cert that the browser will accept for the domain you are trying to get to.
Unfortunately history has shown that getting the second of theese two requirements is far from impossible, so it makes sense to try and avoid situations that make the first of them easy.
So, how are they like floppies?
They can be read and written directly from applications (in the same way as a hard drive or network driver) on the majority of pcs without needing any additonal software or hardware and they are small enough to easilly carry arround.
That combination of features is IMO what has allowed USB sticks to replace floppies where everything else failed to do so.
The superfloppies (zip, LS120, HIFD etc) remained niche products because of reliability issues and the fact that none of them could never get the drives widespread enough (yeah you could cart arround the drive and a CD of drivers for the drive but that kinda reduced the portability). CD-RW got the hardware widely distributed but unfortunately burner manufacturers stopped shipping directcd and in doing so largely killed off "packet writing".
While what you say is true, is also true that franchises make differences when it comes to locations, just look at the menues of McDonalds in different countries.
Afaict mcdonalds gives far more freedom to it's international subsidaries than is given to franchises within a country.
I thought their usual backup was to go to the ISS in case of damage
Afaict other than this hubble mission all the shuttle missions since columbia have been going to the ISS anyway. I think the plan is to stay docked with the ISS until just before the rescue mission arrives, then move everyone to the space station and dump the damaged orbiter so the rescue mission can dock.
but they can't because they are in the wrong orbit for that in order to service Hubble.
Right, hubble and the ISS are in totally different orbits, moving from one to the other would take far more delta-v than is availible.
The reason a rescue mission is on standby is there are "higher amounts of space debris in Hubble's orbit".
I doubt it. Afaict the shuttle on standby plan was being developed long before the "higher ammount of space debris" issue came up.
NASA is paranoid about a repeat of columbia. As such they have put in place an inspection routine for all shuttle missions and a plan for what to do if the inspection finds damage too big to safely land with.
For most missions they just plan to stay on the ISS until evacuation can be arranged but that isn't practical for a hubble servicing mission so a standby is needed.
My understanding was that 64-bit wine could only run 64 bit windows binaries. So if you wanted to run either 16-bit or 32-bit binaries you needed a 32-bit wine.