3 ms·
Ok, so CPython is broken by default and by design. Yes Sir, understood sir, no exceptions, sir!
by namKS 6y ago
Ok, so CPython is broken by default and by design. Yes Sir, understood sir, no exceptions, sir!
- phoe-krk 6y agoSure. Do you have any arguments why it isn't broken and go against the arguments linked in the related HN discussion? Is CPython in some way immune to overflows, use-after-free, double freeing, and so on? How much of CPython is actually implemented in C, and how much in itself and/or in Python?
- hmartins 6y agoWhy should we care about arguments in a random HN discussion? We should care about arguments from people who have done substantial work. Totals grouped by language (dominant language first): python: 578880 (54.33%) ansic: 475310 (44.61%) sh: 4073 (0.38%) cpp: 3847 (0.36%) asm: 1486 (0.14%) objc: 761 (0.07%) lisp: 502 (0.05%) pascal: 353 (0.03%) xml: 308 (0.03%) csh: 21 (0.00%) Most of pure Python is in the stdlib.
- phoe-krk 6y ago> We should care about arguments from people who have done substantial work. OK, we can drop the HN comments. Since Stefan Hajnoczi is a substantial QEMU contributor, how would you respond to the arguments linked in http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c-to-rust.html http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c...?
- anwkdjqd 6y agoSince the chief rust town crier arrived, even this comment is downvoted. No other language has such toxic people who don't do much actual work. Rust survives by cancel culture.
- ginsider_oaks 6y agois any rust code some way immune to unsafe blocks?
- wizzwizz4 6y agoThat's a little different. If you're running a C linter that statically guarantees safety, then it's comparable; otherwise, you're comparing mostly Safe Rust (with some Unsafe Rust in it) to Unsafe C. Safe Rust is automatically immune to lots of these issues. Unsafe Rust isn't, but all of C is unsafe (unless you're using a safety-enforcing linter that only gives you access to a subset of the language).