950 karma · joined May 25, 2010
I'm going to ask for a citation on this one.
I remember a similar incident at KRX in 2009, and it resulted in a criminal investigation [1], so that ought to be illegal.
[1] http://www.traderdaily.com/07/koreas-elw-players-get-hfc-wak...
High chance the story will be quickly forgotten and the account will be re-used.
http://www.businessinsider.com.au/isaac-newton-and-the-south...
Even C++ programmers, at least the ones that had good fortune to have time away from C++, agree that C++ gotchas are unforgivable.
But in general, C++ and JS communities have the biggest cases of Stockholm Syndrome I've seen.
Disclaimer: I'm a recovering C++ programmer.
It's not how auto trading works. Traded instrument ranges are preset before the algo is started. I've never heard of an algo that tries to pick stocks to trade dynamically based on a name, it would be astoundingly risky.
I've noticed that the "People you may know" section started to contain faceless placeholder entries with emails from my address book (though, I'm not sure if/when I've given the iOS app the address book access).
If you've ever worked with legacy systems older than 10 years, you'd notice that they become a victim of their own "success". You can't throw away features added over years, because a lot of users depend on it, and if you tried to rewrite it, you'd have to rewrite bug-to-bug.
I worked on such systems, and I did try rewriting, and gave up because of sheer volume of work and the knowledge of institutional lore that was required to do it. On the other hand I'm currently embarking on our startup's "rewrite" and things are much much easier, because the feature set is small and I can freely throw away stuff that didn't work.
See also, http://en.wikipedia.org/wiki/Gall's_law
Really?
I thought their SDK circa 2007 (especially the emulator) and API docs were terrible, and Symbian C++ was a real pain to work with. Also, segregation between regular developers and Nokia partners (who paid to have access to extra private APIs) put unnecessary barriers to development.
I won't miss it.
It's OK here, but may bite you with a different function.
1. There was no out of the box support of my particular NVidia video card, so I've had to build the driver from source and fiddle with my system to install it.
2. I've had userspace processes freeze on network activities and become impossible to kill, because of a kernel deadlock in my wireless driver.
3. Proper smooth fonts required work at the time (freetype did not ship with good subpixel hinting).
4. Proprietary media codecs did not work out of the box and required a third-party repositories.
5. The whole KDE four-point-not-really-zero debacle.
A minimalistic XMonad+Vim+terminal setup was decent and worked for me, but eventually I got sick of desktop Linux and moved to OSX.
I realise that many things have been fixed in the meantime, but it was not a flawless experience back then. If I was to give desktop Linux another shot today, I'd be cautiously optimistic, but not expect a miracle.
It handles all the plumbing for you with monkey-patching I/O calls. No annotations necessary, you just write linear code.
[1] http://www.amazon.com/Predictably-Irrational-Revised-Expande...
http://ccodearchive.net/list.html
https://github.com/rustyrussell/ccan
And GMP for arbitrary precision math (integers and floating point numbers).
https://www.braintreepayments.com/braintrust/gotchas-irritan...
This seem far fetched, not sure what thought process would lead anyone to come to this conclusion. Even if you have a million users, you have ~8MB worth of passwords. I'd imagine even developers who are not competent in cryptography realise that.