I love pixel art, used Win 98 as my first OS and still find them ugly as hell. The colors are sad, the perspective is off, and on the first image[1], only 2 icons out of 6 make any sense to me (the trash and the folder). On the second image[2] I understand the wheelchair and the notepad but that's it. These icons aren't inherently easier to understand.
I abandoned newsboat the day it introduced the first Rust dependency and switched to the Android app Feeder.
Some just prefer simple and minimalist software for their daily life, and there's no place for the Rust ecosystem there. For this reason projects like dwm, st, dmenu, bspwm, sxcs, sxhkd, nsxiv, xmenu, xplugd, fzy, nnn, xbanish, scdoc and many others will never be rewritten in Rust or adopted by users who strive for simplicity rather than colorful terminal output. memory safety is just not worth it.
Judging by this list [0] even Python or Go have more chances to align with the philosophy that encourages building simple yet functional things. And I hope this trend of fresh starts continues.
Not sure I'm getting your point. Somehow Rust forces you to have colorful terminal output? Rust is high overhead? You can't strive for simplicity and write in Rust?
Sure it's a bit silly to rewrite a nice simple tool for because it's the new fad. However if writing a new simple tool I'd certainly consider Rust.
How is Rust incompatible with aligning with the philosophy that encourages building simple yet functional things?
> How is Rust incompatible with aligning with the philosophy that encourages building simple yet functional things?
I would say it attracts different kind of developers that in turn make respective design choices, and I believe Rust, its syntax, package management ecosystem and community reflect that. Can you write simple system tools in JavaScript or brainfuck (not trying to compare here)? Sure, but the thinking process, design decisions, approaches would be drastically different compared to what I'd consider good and elegant code.
ANSI C is probably the best balance you can get between product complexity, coding complexity and usability of the output (which again, has to be simple: writing something like Kubernetes in C is probably not the best idea, hence it was implemented in a more suitable language). Though there are some very good and complex products, like the Linux kernel, Redis or Varnish. All of them are very modular, as complex products should be.
Just by having a musl library and tcc [0] you can get a lot done. I'd prefer that over complexity that Rust toolchain involves and crates ecosystem mess.
Another one here. Loved my Macbook Pro 2013, then the O/S turned to crap, gave it to my wife. Currently using a Carbon X1 and it's wonderful. Amazing battery life, Fedora 28, touchpad small but nipple is brilliant on the train when i'm cheek-to-jowl with the guy next to me who's also on a laptop. Wouldn't go back to a new Macbook, but I do miss the 2013 as it was delivered to me before the O/S was ruined.
Yeah, I do. Just wanted to try it a couple of years ago. Honestly -- not worth it (on Linux HiDPI is not there where I wanted it to be, plus with my love of bitmap fonts, it can be hard), especially in a heavily shortcut-powered WM (I use Fluxbox and bspwm occasionally). But that's just me.
My next workhorse will still be X1 nextgen, but with regular 1080p resolution and matte screen. Much much better. Like my Zenbook at home -- which is ideal for me, but less powerful for work-related tasks.
Or not the victim. Combine it with the girl with the dragon tattoo story, and it may become scary how helpless the victim could be under difficult circumstances with no piece of real evidence aka auto-marked as fake.
I show it to my wife (who's just 5 years younger), and she's like: "No.".