Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)HS
Posts
0
Comments
196
Joined
2 yr. ago

  • I think that analogy oversimplifies according to the assumption that one is inherently better than the other. OP's point here is that it isn't all better at all.

    I think a more accurate analogy would be that the OP is screaming that horse trails, ranches, and farms are being shut down because they don't accommodate cars.

  • The longer I use Linux, the harder it becomes to see where windows users are coming from. Its gotten to the point where seeing people use windows in public feels incomprehensible to me, like watching people go to work on a pogo stick instead of a car.

  • I started with raspberry pi zero projects. Specifically projects that make use of various GPIO hats like cameras, displays, speakers, etc. At that level, things are still very abstract compared to bare-metal firmware, but you learn some of the basic principles of I/O. Next plan is to read up on circuit design, and start doing more projects with arduino-controlled breadboards.

  • I used to think I was just a fanboy. But as time went on and I gained more and more experiences, I've only become all the more sure that ANSI C is the only language I ever want to write anything in.

  • I/O Issues are problems that come with the territory for scripting languages like python. Its why I prefer to use bash for scripting instead, because in bash, all I/O are strings. And if there are ever any conflicts, well that's what awk/sed/Perl are for.

  • Consider how dead-easy it is to write a bash script or c program in Linux, and then enable it (have it run on boot) using SystemD daemons. A total noob could do it after reading a 5 minute tutorial.

    Is it even possible to do the same on an android phone? I have no idea, but willing to bet not.

  • This principle applies to the GNU C compiler also. Any other compiler is going to complain at you for not adhering to their stupid style guide, or for not using their proprietary "mEmOrY sAfE" libraries. But if GCC is giving you warnings, you darn well better fix something.