cb321

69 ms·

661.
by cb321 5y ago
> since the number of bits needed to represent n values grows logarithmically with n What you say only applies to sorting n unique/distinct keys. With no prohibition on duplicate keys, n & w vary quite independently. In
662.
by cb321 5y ago
I use Nim, C, Python/Cython, Shell, etc., etc. After a short while Nim felt to be the fastest/most fluid development time frame of the whole bunch - while also having a strong static typing style..I find it a very "get to th
663.
by cb321 5y ago
Perhaps. The https://en.wikipedia.org/wiki/Buckingham_%CF%80_theorem and Lord Rayleigh's refined ideas on units of measure predated Russell's work. These ideas also include at least 1 abstract-to-specialize
664.
by cb321 5y ago
Dimensional analysis of units is absolutely a special case (I said "primordial example") of type systems. Proof: "constrained operations" and "notional objects" are very limited/somewhat concrete - "a
665.
by cb321 5y ago
If by "type systems/checking" one refers to constraints on "valid operations in context" like comparisons, subtractions, additions (or maybe in a prog.lang context assignment to lexically static identifiers) then ph
666.
by cb321 5y ago
@brabel - The Nim compiler actually builds a relatively large `system` package every time. (They are also working on speeding up compiles.) So, compile time does not scale as badly as you think. E.g., you might have to 50..100x the &quot
667.
by cb321 5y ago
That is a nice story about open source to the sad but not so bitter sounding (BOO-YAH!) end. I am not a user (or even Gnome user), but FWIW, I looked and Adrian's eog_window_cmd_copy_image is still there almost 11 years later, only ren
668.
by cb321 5y ago
That made me crack up. Thanks for the morning smile. Priority variation is one thing, but boy oh boy..add lack of self-awareness and you have a pickle of a problem.
669.
by cb321 5y ago
There is definitely a terminology problem. "Automatic memory management" is a more precise term than "garbage collection". It refers to the more user visible trait, and pairs better with the antonym of "manual mem
670.
by cb321 5y ago
I do not know about Zig, but Nim is used in production at multiple companies - biotech, cryptocurrencies, finance, had an attempted commercial video game app, etc., etc. See here [1] for example. [1] https://github.com/nim-
671.
by cb321 5y ago
TinyC/tcc [1] still is a single-pass compiler and can go all the way to ELF files (or directly running via tcc -run) in a few milliseconds - sometimes an order of magnitude faster than the minimal start-up time of an interpreter like P
672.
by cb321 5y ago
You should take a closer look at Nim. I suspect it probably has all that you want, but said features may not be "by default/well advertised" (yet). Alternatively, you should be more specific about what you think it lacks.
673.
by cb321 5y ago
When you have a standardized problem setting like the implicit loop in awk, n alternative to a whole new programming language is a simple < 100 lines of code program generator [1]. This design lets you retain easy access to large sets of
674.
by cb321 5y ago
You could add Nim [1] to that list. Many people say it has "the ergonomics of Python but the strong static typing of C++/Rust." [1] https://nim-lang.org
675.
by cb321 5y ago
"An Efficient Representation for Sparse Sets" by Preston Briggs & Linda Torczon dates from Rice in 1993 covers the case where the index can be a direct map (for small key universes - like, say, the range of `char` or `short`,
676.
by cb321 5y ago
gcc has had code coverage/gcov since before llvm/clang existed. My guess is that the format is different enough from clang's that libfuzzer may need some love to do dual formats (unless it already can - I have not checked).
677.
by cb321 5y ago
Nim has very easy ways to get full C performance in pure Nim with a trivial FFI to just call C and is both higher level than Go and lower level at the same time because of that. Simple analogies often fail to describe. :-( { This is not in
678.
by cb321 5y ago
Ah, yes. Following in the delightful tradition of Flatland [1]. Rudy Rucker's Geometry, Relativity and the Fourth Dimension (1977) may be a fun read {perhaps less fanciful than Potato Chip World} for those interested. [1] https:&#x2
679.
by cb321 5y ago
Sorry. In my kernel build script I patch _STK_LIM in include/uapi/linux/resource.h and MAX_ARG_PAGES in include/linux/binfmts.h to boost my command line lengths. There was a short time when Rob Pike had some patch
680.
by cb321 5y ago
This has some Zsh-isms but should get you going, assuming it is even reproducible across machines. $ cd cligen-github-root/examples # default system nim.cfg $ nim c -d:danger --gc:arc -d:useMalloc --passC:-flto --passL:-f
681.
by cb321 5y ago
Nim code also tends to run faster than Go code (in my experience).
682.
by cb321 5y ago
First, I like that you said "multicores" and not "multithreads". Default-sharing of all memory is overrated. Sometimes it is useful/necessary, but people reach for threads too readily, IMO. For multiprocessing (
683.
by cb321 5y ago
Nim has extremely low compilation times...order 200 millisec with the TinyCC/tcc backend and order 800 millisec with gcc (both for the zero length empty module). Less trivial projects (say transitively importing 25 modules) are more l
684.
by cb321 5y ago
That's also a good one! ..Basically a sub-example of "phase velocity" mentioned in the greatgrandparent. Imagining oneself as an active participant in The Wave seems like it would boost saliency a lot. I'll try that on
685.
by cb321 5y ago
I think this is more that "more features" = "more marketable" which impacts far more than just "unix tools" or even just software. Also, simplifiation does not never happen. E.g., I have a near trivial impl
686.
by cb321 5y ago
Another fun example besides projections like laser pointers or the spot of a searchlight on the clouds is the junction between blades of scissors. Almost all the examples one sees of this relate to synchronization defined entities not bein
687.
by cb321 6y ago
Nim, D, or possibly Python with Cython/Pythran/Nuitka/etc. acceleration (maaaaybe Go). These all have shallow learning curves and easy FFIs to C. That allows you can do easy things first and worry about hard things later&#x
688.
by cb321 6y ago
The general structure of the quip/aphorism/joke/snark pre-dates the industrial revolution dating back (at least!) to Edmund Burke's [1] "Those who don't know history are doomed to repeat it." [1] https:&#
689.
by cb321 6y ago
The linked video seems mostly about UI usage, and one rarely sees nice live action UI demos for machines that (mostly) no longer exist. They should do a sequel that shows these other very powerful system features you mention. One practical
690.
by cb321 6y ago
An attempt in Nim [1]. Something like 7 minutes, but yeah..this is even more crazy dependent upon dev familiarity with the target language/stdlib and their IDE/editor (aka unscientific) than the usual attempted measurements. [1]

More ›