4 ms·
a) Clever. b) Cringe! I really like Ruby as a language, but the ecosystem is just not up to snuff, which is why I've gone back to Python. The docs are complete
by jey 17y ago
a) Clever.
b) Cringe!
I really like Ruby as a language, but the ecosystem is just not up to snuff, which is why I've gone back to Python. The docs are complete, the standard implementation is rock solid and only getting better (cf. unladen-swallow), and I can interface with C stuff easily (cf. Cython). I'm looking forward to Ruby maturing.
- tptacek 17y agoWe push Ruby harder than most people ever push Python and I'm just not seeing the maturity problems you're alluding to. Maybe you could be more specific? We've got Ruby talking to chipsets, controlling WinDBG, debugging processes on Win32, Linux, and OSX, controlling DynamoRIO, running god knows how many different network protocols, calling into Java, routing raw packets with pcap, debugging J2EE container VMs, and fuzzing libraries written in C and C++. (By the way, don't waste time with the Python C interface. Use ctypes. Ruby calls it Ruby/DL or "ffi".)
- gte910h 17y agoDon't waste time with ctypes, use weave or sip or swig :OP
- tptacek 17y agoI'd rather eat a bug than ever use SWIG again.
- mst 17y agoSeconded. And I'm perfectly comfortable using XS to bolt perl and C together. That may be a function of my having spent enough times in the guts of the perl VM to already know exactly what I want and not want anything getting in the way while I'm implementing that, mind.
- gte910h 17y agoOh me too, I much prefer SIP and weave.
- devinj 17y agoOr Cython. That one is nice.
- deleted 17y ago[deleted]