Posts by mburakov@mastodon.social
 (DIR) Post #B7rBNcf6LLhWIRAZWK by mburakov@mastodon.social
       0 likes, 0 repeats
       
       @wolf480pl IMO anything that manipulates entities in memory is generally useful. That is, read memory - process - write memory. If the intended area is system programming, I’d then go with super primitive io only usable for print-debugging. For any kind of “external” interactions - only provide basic (but solid) building blocks, e.g. strongly typed syscall wrappers. Engineers will figure out how to build the rest on top of that in an optimal way for their particular usecases.
       
 (DIR) Post #B7rDwR8HOvMUaAXty4 by mburakov@mastodon.social
       0 likes, 0 repeats
       
       @wolf480pl introducing super-advanced io with async sockets and stuff is exhausting and won’t cover all the possible scenarios anyway, forcing people to resort to syscalls in some cases. So… why bother?
       
 (DIR) Post #B7rDwRL2dTZPDkW5rM by mburakov@mastodon.social
       0 likes, 0 repeats
       
       @wolf480pl If you are thinking of higher-level language above system programming, I’d say there’s no need for a new one. The amount of already available ones is wild.