thesmokingman

To be fair, LinkedIn has been actively supporting deadnaming via their Clear verification program since before the inauguration so one could say they’re near the front of the parade ¯\_(ツ)_/¯

Coincidentally an American investment fund owns ~42% of the company and is the single largest stakeholder. Many would say that qualifies this as an American service.

I didn’t realize Codeberg offered email services. When did that start?

I was cautiously excited until I saw the Vercel sponsorship and now I’m just waiting for this to turn into the thing they’re satirizing.

I assume this is Poe’s Law in action. Elon historically doesn’t understand shit about tech so the commenter is just highlighting something that’s been GA for other tools for years.

The biggest issue with this is the “contract” you “sign” when you do pay. Usually there are terms that let companies come after you. See Creative Cloud, Planet Fitness, and other movers in the “fuck you pay me” subscription world.

There isn’t a universal language to fill all these needs. DevOps covers a ton of areas so you want several tools in your toolbelt instead of just one (granted if you’re an incredibly talented greybeard bash can honestly do everything and do it fairly fast; I’ve never taken this analysis too seriously).

• bash is something you need for every day tasks and quick tooling to improve everything else in this list
• POSIX tooling is something you should know well to improve everything else on this list (eg awk is something you’ll use a lot in bash)
• Python with or without types will handle more advanced scripting in a cleaner and more maintainable way for your team (explaining bashisms slows things down. Does your junior know what : is or why we currently prefer $() over backticks?)
• Go is something you want to use for containerization and scaling servers
• Rust is something you want to use for process work and embeddables

Each of these languages meets some of the requirements on your list but not all. That’s because nothing is a silver bullet. Depending on what you’re doing, you might even want to introduce, say, Java or C# in your pipelines if that’s what you’re maintaining. DevOps should support not alienate and overall it needs to be flexible.

In all fairness, you’re able to distinguish the difference in speech without capitalization using context clues. There are certainly situations where you might have to ask for clarification; while reading you just have to figure out context clues like someone figuring out the meaning of a new word.

I don’t follow this argument. In this context, proprietary code is work product that has value to its owner. Often large swathes of said work product is reused across games so the theory is that releasing the work product means your competitors can make your work product. I do not understand how wrapping someone else’s work product in your own work product doesn’t require them to first release their work product.

Note I don’t necessarily buy the company mindset on proprietary code; I explained here because I don’t understand where you’re coming from.

California is not Colorado nor is it federal. I don’t think you understand the things you’re saying since you don’t seem to grasp, as you put it, the regulations are “often state-specific.” You linked California, not Colorado, which this article is in reference to. Even in the beginning, you didn’t seem to grasp why regulation and some level of understanding about what people should or shouldn’t do is reasonable to have defined. Good luck!

In the US? I’m gonna need to see some statutes there bud. Last I checked there are no federal requirements and as far as I can tell there are only insurance requirements in Colorado at the moment.

1. What about ride share companies that aren’t Uber or Lyft that don’t have safety programs?
2. What requirement do Uber or Lyft have to maintain good safety after, say, they own the market?