I don't normally give tripfags attention but you actually talk about Zig Forums instead of LARPing for attention so I'll break my rule. I'd advise being less of a faggot though. That trip will eventually bite you in the ass if you catch the attention of the wrong autist.
These applications are intended for use in an environment that rarely changes and where there are minimal resources. A general purpose computer generally doesn't have those requirements. So storing two versions of a lib doesn't cause a problem. You _can_ use them on a general purpose machine but there really isn't much point.
You lose the ability to modify the software and have it back up and running quickly for the most part. Embedded software is designed to be used as a whole where the tools in most OSs are designed individually. Upgrading and auditing the software becomes a harder/longer task if you're having to re-audit all of the code every time you want to change it.
Depends, best answer I have is "more than it's worth when better options exist already". The current way of doing things works well enough. You develop bleeding edge stuff in a general purpose environment, take the things that work best, cut all the bloat, audit it, then package it together for an embedded system. That's the main difference between the two; Embedded software is intended to run for many years without changes/updates and is expected to function until the death of the hardware it runs on. General purpose software is designed to be changed quickly/often and will probably do so many times before the hardware it runs on finally gives out.
Also, it's worth noting that in the "good old days" embedded software was generally found stored on things where you only got one chance to get things right. When you're attempting to squeeze everything you can out of a small ROM chip you aren't going to be in business long if you allow bloat or badly written software to get through. It's why optimization has become a bit of a lost art. There isn't a problem of storage anymore so people just shit out something that works and call it good. I've watched the quality of the average programmer's code go down my entire life and I mainly place the blame on the fact that we have so much storage on systems these days. When the average PC sports 8-16GB of RAM with TBs of HDD space it's easy to hide bad practice.
Nobody who comes from an embedded background wants to use weenix for their embedded. The problem is it has all the momentum in that market. If there was a good free RTOS for ARM embedded linux wouldn't be a thing.
Sebastian Gonzalez
I get that a lot! well: thats kinda what the point is. "embedded" software like the ones mentioned in the OP would probably have better code quality and less bugs, on top of being smaller, which as you said doesn't mean much with how much storage we have today, but it appeals to my autism uwu and of course is better practice.
umm, isn't Jewgle Fuchsia an RTOS? Could that be stripped of its GUI and used for that purpose? Of course the best option, although its not really an RTOS would be something based on seL4. You don't get much higher quality than literally mathematically verifying the code's correctness.
I'd like to embed my shotgun into your incontinent boypussy and pull the trigger until your corpse resembles a Pollock original. I will then release a detailed, step-by-step guide to the public domain and procedurally generated fag corpses will take the art world by storm.
anyway, I guess this is sort of a software minimalism thread now, so any suggestions/recommendations would be great! I will say that as far as shells to be used interactively, busybox's ash implementation and mksh are the two smallest, yet still usable without losing your mind. dash I think is the actual smallest, but has no tab completion or history so it's a pain for interactive use. also as cool as they look, avoid using htop or screenfetch to get the amount of ram your system is using. Both of those programs use quite a bit themselves and over-report the number. I recommend just using the free command if mem usage is all you need, or whatever the BSDs use (they don't have free it seems) What's the best practice and most /minimal/ option for serving files over a network/networks btw? I'd prefer something with encryption, so no NFS (as comfy as it is). SSHFS looks great! but apparently pretty bad for setups where more than one person is working with it at a time. Samba? FTPS/SFTP with vsftpd?
Austin Morgan
I would just use scp if you need to move just a couple of files into another computer or setup vsftpd. Don't Samba and SMB have a lot of security issues?
y-your pic is so lewd! OwO Well I meant file serving as in being able to “mount” stuff over a network or share entire directories, like for a NAS. idk about samba security issues. I know from a course I took that if you have the NETBIOS features enabled they can be used as an enumeration tool, but I thought you could disable that. I did see that SMB can be encrypted though.
