Just find 10,000 instruciton pairs that can be reordered as they have no interdependancies, and reorder each of the pairs at random during the install phase. That gives you 2^10,000 unique executibles, but all the debugging symbols and so on will remain the same.
I guess that doesn't help you against stack-smashing and so on. But will allow you to fingerprint who leaked your binary onto bittorrent - which would be its eventual use.
If self-driving cars ceed control back to the real driver when things get "interesting", without all the conditiioning that driving countless kilometers will the driver still be able to react competently? Or will it be like throwing inexperenced learner-drivers into the deep end?
Driving is a skill, and like any skill it needs to be practiced often to stop going rusty...
... it is just that the phone networks don't want you to have them.
I have a 5", quad core, 2GB RAM, 32GB Flash smart phone from Chinavasion. It is much like a Samsung S4, and cost US$250. Unlocked as a standard feature, and with dual SIM, Took five days to from order to doorstep. Plugged in my work SIM and my own SIM and gave back a my work's S3.
Due to a genetic condition my 7 y.o. son has severe motor skills issues (unable to stand, or hold a paint brush or pencil), He also has profound intellectual disabilities, and is unable to speak. He can however get around his iPad like the best of them - browsing Elmo songs on his youTube favorites, watching home videos, playing "Old MacDonald" and ordering his favourite snacks for morning tea using assisted communication apps. The benefits of this technology for him and others with special needs amazing!
However, even though he can't use a fork or knife, he can still stack MegaBlocks and Duplo... but only because we invest our time by playing with him and supporting him..
It doesn't mean what you think- oo practical building can resist all earthquakes. The building standards are more about if a large earthquake occurs the building damage should be it limited to a small area. And it isn't about having a usable building after a quake - it is about not killing the people inside or around it.
Speaking from experience, just because a building stands up during a quake it doesn't mean that the building won't be structurally broken and require significant repairs or replacement before it can be used. The energy has to go somewhere!
I have often though about the universe being created from a simulation that is based on twos complement signed integers. At the start they are all assigned completely random bits.
During the initial damping down of the system to a steady state, there will be a little excess of negative numbers, as the mean of random n-bit number is always -0.5 (e.g. the range for 8-bit numbers is -128 to 127), and these is what are interact for the rest of the simulation..
It makes as much sense to me as any other theory of the origins of the big bang....
I'm sure a fair percentage of Slashdot readers would like nothing more than a nice quite room, limted exercise and regular meals. The only thing missing is a laptop, and good wifi github access.... and please firewall off Facebook and Twitter - pretty please.
I'll pass on that - the reply was to the question "Please demonstrate a basic sorting algorithm that a non-programmer can understand that doesn't perform terribly on large lists". Job done, I'm moving on.
But I agree, if any area of expertise didn't require a lot of learning to understand, then it would no longer be an area of expertise as most people could do it!
The big advantage of quicksort is that is able to quickly sort in place.
Now try to convey that with your piss-poor piles and cards examples.
Anything but mergesort (including bubbesort) looks contrived with physical objects.
Whoosh!
The cards are 'pointers' to the actual people - so now you have a list of people in order, without actually getting all the people to stand in lines and run around.
Re:Similar language, describing different things
on
Code Is Not Literature
·
· Score: 4, Informative
but for the majority of the population something like mergesort, quicksort, or heapsort is going to seem like voodoo no matter how elegantly it is coded.
Explaining quicksort to the layman.
Here's a 1000 names on little cards. Pick one at random and look at the name.
Sort the names into three piles - those that come earlier in the list, those that are the same as the name, and those that come later than the randomly selected name name.
Put the "earlier" pile to the left of the "same" pile, and then put the "later" pile to the right of these two.
Great? Done that?
Now repeat on the process on each "earlier" and "later" piles, Do this over and over again, giving you smaller and smaller piles. It doesn't really matter which pile you split first, just as long as you don't mix up the relative left/right ordering.
Eventually you will end up with lots of small piles of cards that contain all the entries of the same name.
And then, as if by Voodoo., all your names are now in order from left to right.
This can be parallelised - if you want, you can out-source some of the work to friends and family, to speed things up.
In other words, why weren't most of these improvements included back in 2011?
Developing hardware is a lot different than developing software. With software you can go - "oh that now works, lets add this" or "oh, that didn't work out - how about we take that out". With hardware you can't without going back to the start of the manufacturing process.
With hardware a large part of the exercise in risk management - adding one feature that you can't get production ready will kill the entire product. So most projects pick just one or two key areas to develop, the ones that will make the biggest advance on the roadmap, and leave the others well alone. Verifying and validating an entire CPU design is just too much work.
This always leaves low hanging fruit to be picked off in future updates and design refreshes.
1) The proactive, forward looking teams adopt it first, and have great success.
2) The "emerging trend followers" hop on board, and have reasonable results.
3) The rest of the industry follow and have mixed results, without it being any more successful than any other methodology.
Don't be blinded - initial results always look very promising.
Anybody around here remember Jackson Structured Programming The initial OOP wave? The whole CASE moevement? GUI application builders that were supposed to end the need for programmers?
The golden rule is that "whatever methodology technology you choose, half of adopters will always get sub-average results". The question you have to ask yourself Is are your team smarter than the average team?
Due to ROM and cost limitations the original Sinclair Scientific calulator only produced approximate answers, maybe to 3 or four digits. This was far more accurate than the answers given by a slide rule....
Slashdot Mirror
I wonder if they will sell them special space-rated coffee beans at highly enflated prices in order to move any profits back to tax havens?
(See http://www.ukuncut.org.uk/targ... if you miss the joke)
"A better coding for data error correction and redundancy than Reed-Solomon" - this is News for Nerds after all.
And why the "oooh - flappy birds on my phone might be faster" slant? I want a faster SAN!.
It isn't that hard.... there are plenty of low hanging fruit - the classic easy case is the NOPs that are used to align jump destinations. Just find :
[NON PC RELATIVE INSTRUCTION]
NOP
NOP
and replace it with
NOP
[NON PC RELATIVE INSTRUCTION]
NOP
You could even patch the PC relative offset if you wanted to...
Why bother with this at the compiler level?
Just find 10,000 instruciton pairs that can be reordered as they have no interdependancies, and reorder each of the pairs at random during the install phase. That gives you 2^10,000 unique executibles, but all the debugging symbols and so on will remain the same.
I guess that doesn't help you against stack-smashing and so on. But will allow you to fingerprint who leaked your binary onto bittorrent - which would be its eventual use.
If self-driving cars ceed control back to the real driver when things get "interesting", without all the conditiioning that driving countless kilometers will the driver still be able to react competently? Or will it be like throwing inexperenced learner-drivers into the deep end?
Driving is a skill, and like any skill it needs to be practiced often to stop going rusty...
... it is just that the phone networks don't want you to have them.
I have a 5", quad core, 2GB RAM, 32GB Flash smart phone from Chinavasion. It is much like a Samsung S4, and cost US$250. Unlocked as a standard feature, and with dual SIM, Took five days to from order to doorstep. Plugged in my work SIM and my own SIM and gave back a my work's S3.
A cheap 4" can be had for under $70.
Due to a genetic condition my 7 y.o. son has severe motor skills issues (unable to stand, or hold a paint brush or pencil), He also has profound intellectual disabilities, and is unable to speak. He can however get around his iPad like the best of them - browsing Elmo songs on his youTube favorites, watching home videos, playing "Old MacDonald" and ordering his favourite snacks for morning tea using assisted communication apps. The benefits of this technology for him and others with special needs amazing!
However, even though he can't use a fork or knife, he can still stack MegaBlocks and Duplo... but only because we invest our time by playing with him and supporting him..
It doesn't mean what you think- oo practical building can resist all earthquakes. The building standards are more about if a large earthquake occurs the building damage should be it limited to a small area. And it isn't about having a usable building after a quake - it is about not killing the people inside or around it.
Speaking from experience, just because a building stands up during a quake it doesn't mean that the building won't be structurally broken and require significant repairs or replacement before it can be used. The energy has to go somewhere!
My money is on something like what heppend to flght ZU 522 http://en.wikipedia.org/wiki/H...
...just supply a better quality, more desirable coffee? Oh no, that would be too hard!
DRM technology to the rescue,forcing users to buy crappy or overpriced coffee.
I have often though about the universe being created from a simulation that is based on twos complement signed integers. At the start they are all assigned completely random bits.
During the initial damping down of the system to a steady state, there will be a little excess of negative numbers, as the mean of random n-bit number is always -0.5 (e.g. the range for 8-bit numbers is -128 to 127), and these is what are interact for the rest of the simulation..
It makes as much sense to me as any other theory of the origins of the big bang....
I'm stuck at work... I'ld rather be home coding :-)
I'm sure a fair percentage of Slashdot readers would like nothing more than a nice quite room, limted exercise and regular meals. The only thing missing is a laptop, and good wifi github access. ... and please firewall off Facebook and Twitter - pretty please.
Ha! If 00000000 is good enough for Minuteman missiles then it is good enough for me!
i'm going to use '123456' from now on. If somebody is knocking doors with that password, odds are they will access else's account before mine.
I'll pass on that - the reply was to the question "Please demonstrate a basic sorting algorithm that a non-programmer can understand that doesn't perform terribly on large lists". Job done, I'm moving on.
But I agree, if any area of expertise didn't require a lot of learning to understand, then it would no longer be an area of expertise as most people could do it!
That is dumb.
The big advantage of quicksort is that is able to quickly sort in place.
Now try to convey that with your piss-poor piles and cards examples.
Anything but mergesort (including bubbesort) looks contrived with physical objects.
Whoosh!
The cards are 'pointers' to the actual people - so now you have a list of people in order, without actually getting all the people to stand in lines and run around.
but for the majority of the population something like mergesort, quicksort, or heapsort is going to seem like voodoo no matter how elegantly it is coded.
Explaining quicksort to the layman.
Here's a 1000 names on little cards. Pick one at random and look at the name.
Sort the names into three piles - those that come earlier in the list, those that are the same as the name, and those that come later than the randomly selected name name.
Put the "earlier" pile to the left of the "same" pile, and then put the "later" pile to the right of these two.
Great? Done that?
Now repeat on the process on each "earlier" and "later" piles, Do this over and over again, giving you smaller and smaller piles. It doesn't really matter which pile you split first, just as long as you don't mix up the relative left/right ordering.
Eventually you will end up with lots of small piles of cards that contain all the entries of the same name.
And then, as if by Voodoo., all your names are now in order from left to right.
This can be parallelised - if you want, you can out-source some of the work to friends and family, to speed things up.
In other words, why weren't most of these improvements included back in 2011?
Developing hardware is a lot different than developing software. With software you can go - "oh that now works, lets add this" or "oh, that didn't work out - how about we take that out". With hardware you can't without going back to the start of the manufacturing process.
With hardware a large part of the exercise in risk management - adding one feature that you can't get production ready will kill the entire product. So most projects pick just one or two key areas to develop, the ones that will make the biggest advance on the roadmap, and leave the others well alone. Verifying and validating an entire CPU design is just too much work.
This always leaves low hanging fruit to be picked off in future updates and design refreshes.
All distributions are assumed Gaussian untl proven otherwise, as they will be a sum of a large number of random events. :-)
1) The proactive, forward looking teams adopt it first, and have great success.
2) The "emerging trend followers" hop on board, and have reasonable results.
3) The rest of the industry follow and have mixed results, without it being any more successful than any other methodology.
Don't be blinded - initial results always look very promising.
Anybody around here remember Jackson Structured Programming The initial OOP wave? The whole CASE moevement? GUI application builders that were supposed to end the need for programmers?
The golden rule is that "whatever methodology technology you choose, half of adopters will always get sub-average results". The question you have to ask yourself Is are your team smarter than the average team?
Would you like to send anything back for me to put up on the site?
Lack of a SDRAM controller was why I sold off my DE0-nano...
Due to ROM and cost limitations the original Sinclair Scientific calulator only produced approximate answers, maybe to 3 or four digits.
This was far more accurate than the answers given by a slide rule....
For more info have a look at this page Reversing Sinclair's amazing 1974 calculator hack - half the ROM of the HP-35
It does in fact have 64Mb or SDRAM (8MB). I wrote a SDRAM controller for it, that also works on the Papilio Pro...
You missed out Saanlima's Pipistrello. A nice Spartan LX45 board, with PMODs, HDMI and other goodies.