Somewhat unfair judgement against emails IMO, especially cause it’s the “trust list” that’s in the control of a few, with no open manner to add more people to the trust list. The protocol isn’t at fault for failing to prevent problems; it’s the ability for corporations to gain significant market share without control, before they are then allowed to put barriers down to disallow or discourage interaction between those in and out, forcing those within to stay in, while those outside to give up on others in order to gain usability.
- Posts
- 1
- Comments
- 56
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 56
- Joined
- 3 yr. ago
Those two libraries actually look pretty good, and seems like you can remove a lot of the boilerplate-y code you’d need to write without them. I will keep those in mind.
That said, I don’t necessarily agree that bash is bad from a maintainability standpoint. In a team where it’s not commonly used, yeah, nobody will like it, but that’s just the same as nobody would like it if I wrote in some language the team doesn’t already use? For really simple, well-defined tasks that you make really clear to stakeholders that complexity is just a burden for everyone, the code should be fairly simple and straightforward. If it ever needs to get complicated, then you should, for sure, ditch bash and go for a larger language.