Well that’s cool. Sounds like the workspace extensions are inspired by the tools.go pattern. Something that I recommend any go developer dig into!
+1
Personally, I abandoned chromium last year when Google forced the web drm nonsense into the code base. It was a grand example of the problem. Sure, they backed out the change a few months later. But the damage was done and I already migrated to Firefox. It’s been great.
For anyone not familiar, here’s a random article on the topic: https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/
Anyone know why?
Ethically, it should apply. In practice, it doesn’t because the rich make the rules.
Doctors willingly breaking the law to do what is ethically correct. Unfortunately, they would be risking much more than their jobs. They would be risking every major aspect of their lives. Their jobs, yes. Their income and lifestyle. A massive amount of media attention. Legal problems for months or longer. Incarceration. Basically everything. It’s very difficult to look at any single person and correctly say “this is your responsibility”. Self sacrifice just isn’t reasonable or ethical.
A doctor in jail and without a medical license will not be helping anyone with medical care.
Unfortunately, I think you find that extremely few people are willing to accept those risks. And if you could suddenly prevent them from practicing medicine because they follow the law, I think you will find that Idaho suddenly has no doctors at all.
It’s a terrible reality.
While I sympathize with the frustration, anger, etc. over these dystopian laws, we shouldn’t direct those emotions at the doctors. It’s quite easy to say that they’re ethically responsible and should break the law to do what’s right. It’s dramatically more difficult to be in that situation and accept enormous personal liability for your ethics. The doctors are victims too, obviously to a lesser degree.
Blame the law makers. Blame the voters.
This is an especially tragic case. IMO, Gitea has one of the best names in software.
Proton is obviously promoting their own product: proton pass. I tried it and found that it needs a little more development time. Just a little polishing.
In the meantime, Bitwarden is fantastic. I also hear good things about onepass. Don’t use chrome’s password manager.
I’m generally not a big fan of big social media like e.g. Facebook where you might have many thousands of followers, purposefully grow the numbers, etc. I personally think these things are an everyday evil. Yes, it’s a bit melodramatic 🙂but that’s how I feel. Reddit, and now Lemmy are about as far as I like to go with it.
So the isolation of geo-local-only federation is a feature. The feature, actually. I want an entire social media platform that isn’t capable of focusing on single accounts. Where you are near guaranteed to interact with your local community only. Where it would take a dramatic effort for a single actor to influence global opinions. I want a social media platform that isn’t so easy to manipulate. I could go on and on.
After reading your responses, it seems like we’re describing two different methods of building this system.
Your ideas seems to depend on having many instances for various regions, where all instances are federated with each other. So my local instance somewhere in the US would still be federated with for example, an instance in Germany. But the content I receive would be heavily focused on “nearby” content. Interesting
My ideas are based on an important difference. An instance for my town would only federate with instances for the surrounding towns. Maybe one or two more “hops” away. So sharing content between my local instance and one in Germany would be impossible. Content on my local instance would only be accessible to users in nearby instances. Local content enforced by local federation.
Here’s my random collection of thoughts on the subject.
I have no idea how common it is in general. Seems like some devs build tests while others don’t. This varies plenty on a team level as well as organization wide. I’ve observed this at small to very large companies, though not FAANG where I generally hope and expect that tests are a stronger standard.
I will say that test are consistently and heavily used in every large, open source project that I’ve reviewed. At some point, I think quality test cases become a requirement.
Here’s the big thing. Building automated tests is almost always a wise investment, regardless of the size of the org. Manual testing is dramatically more expensive and less effective than running unit and integration tests. I’ve never written unit tests and not found issues.
More importantly, writing unit tests forces you to write code that can be tested. This is important. IMO, code that can be tested is 1) structured differently and 2) almost always better.
Unit tests protect you from your own mistakes. Frequently. Integration tests protect you from other people. E.g when your code depends on an api and that api unexpectedly introduces a breaking change.
Everybody likes having quality tests. Nobody likes writing tests.
Quality tests are basically a strict requirement for fully automating ci/cd to production. Sure, you can skip tests and automate prior deploys, but I certainly don’t recommend it. I would expect people to be fired for doing this.
Chasing 100% test coverage is a fools game. Think about your code, what matters, and what doesn’t. Test the parts that add value and skip the rest. This is highly related to how writing unit tests change your code.
Building front end tests is inherently hard. It’s practically impossible to fully test front end code. Not even close.
Personally, I like the idea of skipping tests when you’re building a POC. Before the POC is done, you may not know if your solution is viable or what needs to be tested. The POC helps you understand. Builds tests for MVP and further iterations.
Quality ci/cd tests are complimented by quality observability, which is a large and independent topic.
/ ramblings of a tired mind