News for hackers. Stuff that matters.
Re:BGP Implemented in Go by platinumrad on Saturday March 19, 2022 @07:56PM (#30738686)
HTTP and JSON may count as "really really basic" to you and BGP may not, but I worked on BGP years before I ever touched HTTP or JSON so the opposite would be true for me. People from different backgrounds are familiar with different acronyms and as a result different acronyms are assumed to be known in different contexts. Don't assume your experience to be universal.
Re:BGP Implemented in Go by innocentoldguy on Saturday March 19, 2022 @08:42PM (#30738917)
It is good form in technical writing (or any writing, really), to define your acronyms the first time they are used. For example, this would have been helpful:

"GoBGP is an open source Border Gateway Protocol (BGP) implementation..."

Writers should never assume that knowledge of an acronym is universal.

Re:BGP Implemented in Go by markkrj on Saturday March 19, 2022 @09:17PM (#30739109)
Would you post something like "go-json is an go implementation of JavaScript Object Notation"? Or "Nginx is an Hypertext Transfer Protocol Server"? Please.... It is not that hard to search for "BGP" on the web.
Re:BGP Implemented in Go by spc476 on Sunday March 20, 2022 @12:27AM (#30740110)
Maybe so, but I wrote about mixing acronyms towards the end of this post: <http://boston.conman.org/2003/11/19.2>, where IRA can stand for one of three different things. My solution: use use <abbr> (<acronym> seems to be deprecated these days).