11–20 of 36 posts
If you can’t easily and intuitively understand why you shouldn’t call it “Mac” here in 2022, I confess to zero confidence that you’ll have successfully achieved any other objectives. Just being frank. The “Go” team ignored sense and it seems to have worked out somehow for them, so it may be moot to lose my random individual interest so quickly.
The reason this problem is hard is that a resume is an intersection of multiple kinds of data: education, licenses, contact information, work history, and narrative text. Business can't even agree on how to best organize this data, or even how to represent it. Individuals? Well, the CV is all about me, and I want mine to uniquely be me -- even in that means using comic sans. Also, people don't look for jobs every day, so many make a new resume and a new profile whenever they start searching. So you have consumers of data (businesses) and creators of data (job seekers) who really are misaligned.
Finally, business want perfect candidates, and people are not perfect. There's actually an incentive in job hunting for people to stretch the truth, which makes CV data unreliable regardless of format. In some cases, the automated screening is so tight that only a lie will get through the filter.
If you can’t easily and intuitively understand why you shouldn’t call it “Mac” here in 2022, I confess to zero confidence that you’ll have successfully achieved any other objectives. Just being frank. The “Go” team ignored sense and it seems to have worked out somehow for them, so it may be moot to lose my random individual interest so quickly.
Who was using "Go" before Go?
If you can’t easily and intuitively understand why you shouldn’t call it “Mac” here in 2022, I confess to zero confidence that you’ll have successfully achieved any other objectives. Just being frank. The “Go” team ignored sense and it seems to have worked out somehow for them, so it may be moot to lose my random individual interest so quickly.
Who was using "Go" before Go?
If you can’t easily and intuitively understand why you shouldn’t call it “Mac” here in 2022, I confess to zero confidence that you’ll have successfully achieved any other objectives. Just being frank. The “Go” team ignored sense and it seems to have worked out somehow for them, so it may be moot to lose my random individual interest so quickly.
In case the tone comes across harsh, I was trying to hold back just how I really feel. I can read and write in Go, but I hate the entire language and it’s ecosystem. It’s obvious to me that it was designed to be a better Java for Googlers at Google living in a monorepo world… the only positives I have to say about it are that talented people have somehow managed to write excellent and useful tools and software using it, but I really can’t like a language that makes me feel like I’m programming with the accidental child of BASIC and Java. However this isn’t a thread about Go, I just wish the poor choice of name had doomed it to obscurity and a quick death.
If you can’t easily and intuitively understand why you shouldn’t call it “Mac” here in 2022, I confess to zero confidence that you’ll have successfully achieved any other objectives. Just being frank. The “Go” team ignored sense and it seems to have worked out somehow for them, so it may be moot to lose my random individual interest so quickly.
Who was using "Go" before Go?
There is another language called "Go!"
https://github.com/golang/go/issues/9#issuecomment-66047478
Russ Cox's response was, "The naming similarity is unfortunate. However, there are many computing products and services named Go. In the 11 months since our release, there has been minimal confusion of the two languages, so we are closing this issue."
Earlier quoted context omitted.
That already stands for message authentication code and media access control.
There's also a cosmetics company named MAC.
This is an interesting concept but as we have seen when the semantic web started out it only really served to enhance search engines instead or large tech companies would internalize the semantics of the data. Making large formats for interoperability never really caught on. Naming the standard Mac is also an issue (due to a product by Apple Inc.) but since its an acronym you should always format it as MAC
That's the American convention, but it can vary elsewhere. If you look at BBC articles, you'll find that initialisms (like HIV) will be capitalized, but acronyms (like Aids) will only have an initial capital letter. Since "Mac" will be pronounced rather than saying "M-A-C", the style in a lot of the world would be to only capitalize the "M".
Wikipedia's English language style guide specifically notes that it doesn't follow the convention of distinguishing between acronyms and initialisms: https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Capi.... There's more information in the article about acronyms: https://en.wikipedia.org/wiki/Acronym#Case
"Some publications choose to capitalize only the first letter of acronyms, reserving all-caps styling for initialisms, writing the pronounced acronyms "Nato" and "Aids" in mixed case, but the initialisms "USA" and "FBI" in all caps."