Forgot your password?

Comment: Re:Huh? (Score 4, Interesting) 371

by smcdow (#44457841) Attached to: Using Java In Low Latency Environments

The article suggest that one solution is to simply not do GC until the end of the trading day. I have to admit that's a good pragmatic solution, certainly so for HF prop traders.

Not enough memory on your servers? Add more. Still not enough? Add even more. The cost would be a pittance for any prop trading company worth its salt.

Comment: embedding/extending (Score 1) 404

built-in support for concurrent programming for multicore computers, very friendly C programming interfaces for embedding and extending, a LLVM-based JIT compiler, a Clang-based module for embedding C/C++ codes in Dao, and a Clang-based tool for automatic binding generation from C/C++ header files

I don't know the first thing about Dao, but I'm always interested in any environment that makes embedding/extending easier. When you're working with a 15 year old code base, it's a lot cheaper to embed existing libraries into a new system than it is to re-write them. (Or, add new capabilities to a old system via extending).

Alas, there has never been a language where this capability doesn't end up being an absolute CM nightmare.

Comment: Re:School v. Reality (Score 1) 292

by smcdow (#42370319) Attached to: Real World Code Sucks

See, you want the ones that write quality code and test-drive the crap out of everything so they don't have to put in 15 hour days to make the latest milestone.

Yes, exactly. So that when the inevitable mid-project changes to requirements, scope, and/or milestones happen, they'll be better able to cope with throwing away all that up-front planning and preparation -- and start working 15 hour per day to meet the new deadlines.

Comment: Look, someone has to say it... (Score 3, Insightful) 510

by smcdow (#39383805) Attached to: Van Rossum: Python Not Too Slow

Integrated multi-language solutions are teh suck.

I know that Python is much better than a lot of other languages for integrating C/C++ code. But in the end, if you're doing production systems, you'll end up getting bitten by some unforeseen incompatibility caused by some upgrade somewhere.

It will happen.

Chemist who falls in acid is absorbed in work.