2 ms·
I stopped writing anything like rust because rust its ecosystem is mostly complete enough , expressive, and rapid to prototype and use. To save my cognitive loa
by fnordpiglet 3y ago
I stopped writing anything like rust because rust its ecosystem is mostly complete enough , expressive, and rapid to prototype and use. To save my cognitive load I shelved my python, Bourne, JavaScript, etc, and just write rust now. It’s not a decision for everyone and I’m not here to convince anyone of anything. But my life is simpler, my scripts more general and faster, and I don’t particularly ever miss the interpreted languages. It took a while to build that level of facility in rust for simple tasks, and of getting over the mental wall of “python is for X and compiled is for Y.” But I’m generally glad I did. Except when it comes to coding interviews and none of the graders know rust and my Python is getting rusty (harhar) after a few years of leaving it aside.
- unethical_ban 3y agoIn my profession (sysadmin related) it seems that if you want the glue-code orchestration and SDK availability of Python, but with better performance and types, you use golang. I don't think most vendors are popping out Rust SDKs for the product's APIs. I'm not invalidating your experience, it sounds wonderful to find the solace in one language.
- fnordpiglet 3y agoYeah just similar to Python the build and package management stuff in go is a nightmare, and I’d rather hitch my cart to the Mozilla guys than the Google guys. (I’m ex-Netscape and helped launch the OSS of the browser into Mozilla) On apis, honestly, I just write my own api integrations. But most of the APIs I use are documented without programmatic specifications, and sdks are usually garbage written by an intern :-)