Terrible idea for color-blind people. And I don't even mean severely color-blind, like when you can't distiguish red from green at all, but something more common and less severe, like deuteranomaly - where it's shades of these colors that are hard to distinguish.
Because the rainbow parenthesis alternate in frequency of brightness, its actually really easy to distinguish which is which, unless you're severely colour blind.
I can't tell some apart, but because they've got a different colour in-between, it makes it easier to jump between start and end of expressions. Being able to box blocks in my head faster.
That being said, I always have to tweak accessibility settings anyway. Change of font, change of size. Having to toggle off rainbow as well doesn't seem to really add to the large list of things.
The color blind would still see the parenthesis at least like they see them currently without the color coding though, given they are distinguishable from the background by lightness.
Realistically, you're probably going to want to let the user choose the colors used for their parenthesis, and once you have that set up it's pretty easy to include one or more colorblind-friendly color schemes.
Panic's "Nova" does this. It lets you pick your palette for the parenthesis from about 30 choices. It also adds vertical lines along the left edge to show indentation level and lets you choose from the same palettes. There's three at the bottom of both palette lists designed for protanopia/deuteranopia/tritanopia.
Those people are able to distinguish suggested colors - the example is using primary colors. And at worst, it would be the same as all parenthesis being the same color (black).
no, its not. first of all either I sense brightness differently, or I use it to compensate. so highlighting of any kind make the text a mix of brightnesses from dingy to glaring across the text.
since it take me effort to actually parse the colors, this is a constant distraction.
so I can read monochrome text just fine, but multi-colored text really slows me down.
Same. New to printing but haven't had a single failed print yet (only used PLA and PETG so far though), and the print quality is generally excellent. That said, it does not meet all the requirements of the OP.
I may be too picky, and on reflection I probably shouldn't be - it was just my first thought when I saw what the project actually is for the first time.
What I meant is the "Py" prefix is typically used for Python APIs/libraries, or Python bindings to libraries in other languages. Sometimes as a prefix for dev tool names like PyInstaller or PyEnv. It's just less often used for standalone apps, only to indicate the project was developed in Python.
It's pretty good! It did quite well when asked a variant of "when do the trains meet" problem, although it used different values for speed than what I told it to use (and what it actually used in textual response: 120km/h and 20km/h in video vs 80km/h and 60km/h in the prompt and textual response).
There was also Bada OS, Samsung's attempt to cut the dependency on Android. I was actually running a device with 1.0, and it was surprisingly usable. The investment in building a development community was also there. They released lots of documentation and the SDK. Sadly, they followed with a 2.0 that really wanted to feel like Android (but wasn't).
They obviously didn't want to put all their eggs into one basket and kept releasing Android phones in parallel. Eventually, Bada died a silent death, although some of it probably found its way to Tizen.
The author of this blog post is the developer of Reticulum, which is a complete network stack and full-fledged alternative to TCP/IP. (https://reticulum.network/). Reticulum is capable of operating over not just LoRa, but bluetooth low energy, standard WiFi, Packet Radio, and overlay networks like Tor and I2P.
Reticulum seems like a promising protocol but I doubt it can be used practically as a mesh over packet radio at low baud rates given its asymmetric encryption suite.
Constant key exchanges, message acknowledgements, and large payloads over standards like AX.25 or FT8 would quickly congest a given frequency using off-the-shelf analog equipment that requires audio mod/demod. But it would probably work fine for more traditional, client-server traffic or simplex traffic.
It seems much better suited to digital traffic in the 900mhz+ range a-la Meshtastic or Arednmesh.
