Readit NewsThat said, we keep data usage rather low because we're on the metered plan.
Sure, most of that is not the compiler or standard library, but dependencies. But I'm not talking random opensource library (I can't blame the core for that), but things like protobuf breaking EVERY TIME. Or x/net, x/crypto, or whatever.
But also yes, from random dependencies. It seems that language-culturally, Go authors are fine with breaking changes. Whereas I don't see that with people making Rust crates. And multiple times I've dug out C++ projects that I have not touched in 25 years, and they just work.
Service members are anyone serving in the military.
Warfighter is used to describe combat roles.
If useful to distinguish between the two, warfighter is the correct term.
The POGiest of POGs are "warfighters" and individual organizations within the DoD proudly advertise how they serve runny eggs and chicken to warfighters every day or issue their uniforms/equipment with incredible lethargy or maintain their personnel records in 20+ different systems duct taped together.
"Service member" does get used a lot still. Usually abbreviated to "SM".
Source: Personal experience in both combat arms and non combat arms roles.
So, NPM? In reality AI is making this LESS likely to happen. It's easier to write a small utility function with AI then find and use a library these days
"Changing it back" is completely ahistoric.
So, you're saying you can still ship on time without including these things and we just add them ourselves? Cool.
Meanwhile, I have a box of hand-me-down spinning rust to fall back on. Sigh.
Servers perform work. For people. My oven (KitchenAid) is a machine, yet has a setting that makes it non-functional during certain religious events that require people not to work.
Similarly, B&H Photo's web site won't take orders on the Sabbath. They'd rather take the revenue hit than violate their principles.
A foreign notion to the tech industry.
So, how do you get around that? Constantly messing with the clock?