6 ms·
>Same here. I really don't see the point of renaming well known and defined concepts I kind of like this whole renaming things thing that a few projects have b
by djfm 11y ago
>Same here. I really don't see the point of renaming well known and defined concepts
I kind of like this whole renaming things thing that a few projects have been playing with lately. I think of elixir/phoenix with all their "hex" "mix" ".ex" files and other disturbing things, Rust with "crates", "cargo"... Words carry too much weight, sometimes changing a few words can force you to make the effort to learn again and you may learn something new
- MichaelGG 11y agoWhat else would you call cargo? It's a tool that only works for Rust. So any name is gonna be pretty much just a name, unless you take the MS approach and call it "Rust Package Manager" (RPM... oh wait.) I do think it's fine to pick up new names when things vary significantly. In my own projects, I will often eschew names that are too generic if it'll help clarity. Like CustomerUpdateAgent. If the program mainly revolves around that, and there's even a slight bit of ambiguity over what that might mean, then give it a name that conveys "you need to know what this is, don't assume based on the name". So, perhaps in that case, "Freshmaker" is a good name for CustomerUpdateAgent.