ReligiousFlames

7 ms·

1. 61.▲
   by ReligiousFlames 9y ago

   That's all well-and-good for benchmarks that don't need to delete elements, but suboptimal for kernel data-structures that don't require O(1) find but are mostly round-robinned like multiple sockets. Using reallocated arrays
2. 62.▲
   by ReligiousFlames 9y ago

   I think it's poor methodology combined with a "dangerous" language: lack of unit-testing/TDD, low-level verbosity, lack of formal behavior prooofs, kitchen-sink features lumped into the kernel, constantly reinventing the
3. 63.▲
   by ReligiousFlames 9y ago

   There are numerous, tested macro libraries to prevent reinventing common data-structure/algorithm bugs. Here's one: https://github.com/troydhanson/uthash
4. 64.▲
   by ReligiousFlames 9y ago

   The great thing about battletested, JIT VMs like CLR/JVM/HiPE is that the user code can be compiled once and the providers can keep optimizing them in future versions and also with uptime. As long as memory usage, GC behavior and
5. 65.▲
   by ReligiousFlames 9y ago

   If people aren't exposed to enough languages to a level of competent understanding, if not mastery, a groupthink monoculture will inevitably develop where engineers only understand JS and Python, not C, Tcl, Clojure, Erlang, Brainfuck,