It seems to me like any potential for exploiting millisecond delays in transaction transmission will be consumed and defeated by the time it takes a human operator to interpret the information and hit the "confirm purchase/sale" button.
Did you even read the summary? Let me quote the relevant section:
The 'algos' that make autonomous trading decisions
The problem is the start-up cost. Buying the necessary hardware, obtaining the required data sources, developing the necessary analytical formulas and coding them efficiently costs a *lot* of money. So it's the free market of people who already have a lot of money and time, or simply an enormous amount of money.
Because the people currently providing these services didn't have to pay all the infrastructure and coding costs when they joined? Since when did "free market" mean you didn't have to spend money to join in?
Or how strictly does a typical private tracker enforce ratios for older, overseeded torrents?
Private trackers enforce a ratio for your cumulative downloads and uploads not on a individual torrent basis.
These corporate moneymongers are sad that they can only buy 3 boats this year instead of two
lolwut? Why would someone be sad that they could afford more boat than they originally expected?
>May be you are more lazy _THAN_ the guy that learn English as a second language.
And you must be lazier than the guy that _LEARNED_ English as a second language.
>If you don't even know these two, then you are not qualify to be on slashdot.
I guess you're even less _QUALIFIED_ to be on Slashdot.
Losing your job to Bender: technological progress.
If you lost your job to Bender it means you're even lazier then the guy who accept packages at the moon amusement park
Yes, because in this vast world there is only the singular good coder and everyone else is lousy or a student.
When the exact specs only exist on two manufacturer's machines, for example, and both only offer it with Windows installed, and jack the price $40 because of it, where is my choice?
I guess you just don't have one. Those computer manufacturers have no obligation to sell you a product.
No, he was saying that if you weren't a C++ programmer that you should leave the industry as if being able to program C++ and knowing pointers and memory management was some sort of godlike skill. The people who bluster on about how they know about memory management and pointers are usually the ones who write some of the leakiest code around.
But Amazon is reprinting these books they aren't providing digital copies. So, yes, they are probably going to charge something to cover the costs of printing.
Yes, but this frontend uses about 75 megs of RAM without anything running. When it's actually doing something it uses around 175 megs of RAM. The fact that Firefox can use more on start up with no tabs open is not a positive for Firefox.
I've seen such horrible Java programs from new programmers because they are never taught ANYTHING about memory management.
Well but that can be said of programs written in any language. It's not a language or frameworks fault if you can't write good code. There is nothing inherent to Java, C#, etc that mean that your program HAS to be bloated or use a lot of memory. Most of the time it happens for the same reason you see bloated and memory leaky C/C++ program: programmer inexperience or laziness.
"don't want to deal with them"?
In all programs, yes sometimes you don't want to deal with them when you can use a language feature to simplify things. Dealing with new/deletes, etc is both a tedious task and can be very error prone as one can see by the number of C++ programs that have memory leak issues. Now this isn't to say that there aren't cases where you have to do it because of critical performance reasons.
it's perfectly fine to optimize development time, but this trend of offloading excess work onto users platform is unacceptable.
It's unacceptable to use a built-in language feature, such as auto_ptr, to help to reduce the amount of memory leaks? Huh?
The rest of your post has no relevance at all to what I was talking about. I wasn't proclaiming that one shouldn't ever manage their memory manually or that you shouldn't care about performance or the quality of your code because hardware will get faster to make up for it. You seem to be ranting at someone else or else your turning my post into some sort of strawman.
Then use a framework, like Qt, that deals with all of that for you.
Or I can just use a built-in language feature like auto_ptr which takes away most of what you used to have to do manually.
Just because you don't need to mess around with pointers, that doesn't mean everyone doesn't need to.
Great. I never made any such claim. Are you arguing against someone else with that sentence?
Yes, but since every Java and
An authority is a person who can tell you more about something than you really care to know.
