It could also just be for clarity’s sake, since truck could mean a pick-up truck (or some other type of truck), and tractor could refer to a farm tractor (or some other type of tractor).
Calling it a semi-truck disambiguates since "truck" and "tractor" are too ambiguous.
We overload the meaning of "GFM" to mean "GitLab Flavored Markdown", which is a superset of GitHub's version. However it can cause confusion as they are not the same thing.
It's a pet peeve, but I wish that people would stop describing their HTTP RPC APIs using the term "REST".
The only solution is probably to advocate for moving away from "REST" entirely—for all parties. Mend the discord by coining two new terms and clearly articulate the two meanings that should be attached to them.
("Indian" is another word like this, but that did not get fully deprecated. This is resulted in lots of confusion. "'Indian'? Like Native Americans?" "No, Indian as in 'from India'" "Oh, all right." A similar thing is happening with "open source".)
This probably involves making the terms (or at least one of them—so long as it's the right one) somewhat cool. Maybe the non-REST term should be AROH (pronounced like "arrow") for "Application RPC Over HTTP".
If you have both foo.scss and _foo.scss, then foo.scss will take precedence. If you want _foo.scss instead, you'll need to add the underscore to your import statement. @import "test/_foo";
BitTorrent is a peer-to-peer (P2P) communications protocol for file sharing. It may also refer to: BitTorrent (company), a company which develops and maintains the BitTorrent protocol BitTorrent (software), the original BitTorrent client