I guess the illustrations for the article were made with ai - they are all different styles visually. I like it allmost all the way through, gives a nice fuzzy ai edge to the feel, until 55% done then it starts to feel too weird.
it's also possible to get a little better results by cheating a little bit with the error distribution, Ulichneys ξ1 and ξ2 as in "Simple gradient-based error-diffusion method" Journal of Electronic Imaging jul/aug 2016.
Interestingly that reflects Airbus vs Boeing cockpit philosophies.
In the early 1980s Airbus adopted Dark Cockpit where the default state of all annunciator lights is off. If one illuminates then it indicates something worthy of attention. The colour of illumination indicates functional state; blue is good, amber is malfunctional.
I assume that's for indicators of abnormal, but safe, state. One example could be the undercarriage being down, a situation that would usually not be expected, but when you're in the process of landing doesn't warrant attracting your attention as an error state.
In particular, the elixir_ale library is a very pleasant interface to various bits of hardware you might want to interact with at the GPIO/i2c/etc level.
It'd be interesting to explore something similar to the bitstring[1] library for Ocaml. Where should one start if exploring syntax extensions for Rust. I haven't looked into rust in a while now so i'm not sure how far one can get with macros these days.
clearly the author is not hip to The Human Evasion by Celia Green. Those guys were just all OK with choosing a slightly different reality, because the mainstream reality tunnel is also equally flawed, and less interesting
Human beings live in a state of mind called 'sanity'
on a small planet in space. They are not quite sure
whether the space around them is infinite or not (either
way it is unthinkable). If they think about time, they
find it inconceivable that it had a beginning. It is
also inconceivable that it did not have a beginning.
Thoughts of this kind are not disturbing to 'sanity',
which is obviously a remarkable phenomenon and deserving
more recognition.
well, emacs, or terminal usage in general on a mac with the control key not on edge of keyboard is extremely unergonomic. So yay to control in the right place.
I'm with you; you're talking to a more than twenty-five year user of Emacs here. I do try, however, to be no less circumspect of my own actions than I am of others'.
Is saving my pinkie from cramping worth losing the ability to type on anyone else's keyboard? I'd say so, but there is a cost.
Sure it takes a while to load and there's bloat, but the bloat is everywhere now.
On the bad site of the JVM and assorted Java tools is that they are second class citizens of the unix world. The command arguments are all messed up, much like a windows tool ported to unix, and the interaction with the rest of the unix stack like sockets, files are all solipsistic and off, which leaves an ill stink on everything touched by it.
One of the things I find funny with java is the once upon a time much touted security model, fast forward a couple of years and the event of android - using the unix security model and none of the java stuff.
Well, except for the type safety of Java, only allow native code to be compiled to shared objects for implementing Java native methods and exposing all OS APIs outside what is required for graphics and real time audio via JNI.
If it wasn't for the pressure of game developers, the NDK wouldn't even exist.
Remember Brillo? It was supposed to be like Android, but using C++ frameworks instead, as presented at Linux Embedded 2015 conference.
Guess what, when it got recently re-branded as Android Things, it switched to the Java Frameworks instead and it doesn't even allow for the NDK, with the user space device drivers being written in Java.
