5 ms·
Java obviously, there are no security issues with java... No wait! Ruby, that should be perfect, can't cause buffer overflow there.... Ermm.. wait I got , wel
by mox1 13y ago
Java obviously, there are no security issues with java...
No wait! Ruby, that should be perfect, can't cause buffer overflow there....
Ermm.. wait I got , well use python!
- lispm 13y agoWhat do you think the Java runtime is written in? The Ruby runtime? The Python runtime? Hint: it starts with a C. If you build a house in a swamp, you are in trouble.
- mox1 13y agoI was making a joke.... If C is the wrong choice, what is the right choice?
- jmz92 13y agoIn a couple years or so, my bet would be on Rust.
- diminoten 13y ago> The Python runtime? Why, Python, of course![0] [0] - http://pypy.org/ http://pypy.org/ (I jest, your point is entirely valid)
- aryastark 13y agoWow, you're daft. Everything is, ultimately, getting turned into machine code. Not even Lisp Machines could get away from this fundamental fact: http://funcall.blogspot.com/2009/04/some-lisp-machine-minutia.html http://funcall.blogspot.com/2009/04/some-lisp-machine-minuti... > Bogus objects — properly tagged words with invalid addresses that pointed at uninitialized memory or into the middle of object of a different type — which would cause the GC to corrupt memory would be left in registers or on the stack. These sort of problems were everywhere in the microcode. Go build your cabin in the woods now.
- lispm 13y agoSure one can corrupt memory on a Lisp Machine. System software like the micro code or the garbage collector can contain bugs. Something like a buffer overflow was very very rare. This was not a systemic problem like it is in C.
- bjourne 13y agoJava has several runtimes. The most popular one is Hotspot and written in C++.
- betterunix 13y agoYou can write the Python runtime in something other than C: http://pypy.org/ http://pypy.org/ And there are Java compilers and runtimes written in Java, and Lisp compilers written in Lisp, etc.
- lmm 13y agoI can't speak for Ruby, but in both Java and Python I've never seen a bug this embarrassingly bad. I mean, this bug simply would not have happened in a language with a working boolean type, or with exceptions (I trust the ZeroMQ guy's judgement about as far as I can throw him).