101 karma · joined May 30, 2020
[2] B12 sources up until it was possible to synthesize in the 60s were exclusively from animal products. Also, if you're even vaguely predisposed to anemia, you will likely struggle getting enough hema-available iron from plant sources without supplementation.
Glad you are able to live off of entirely soybeans, legumes, grains, nuts and seeds. For a lot of people, this isn't sustainable. Would love to see your bloods, discuss athletic performance and energy.
[1] https://www.scientificamerican.com/article/diet-and-primate-....
[2] https://ods.od.nih.gov/factsheets/VitaminB12-HealthProfessio....
I understand there is a morality aspect at play but it's frustrating hearing the vegan vitriol dolled out without thought for consequence. Meat is by far the most nutrient dense food available to humans. The vegan diet (as in strict vegan, not vegetarian) is incredibly unhealthy. Have you considered the land use required to grow the crops necessary to deliver the same amount of nutrients to a global populace?
There's a burgeoning industry growing which conflates health and veganism and snidely appeals to the morality aspect of the vegan diet while dangerously touting non-existent health benefits. The list of ingredients ina a beyond burger is longer than my arm.
My advice? Stay away from fast food (vegan or otherwise), eat whole, unprocessed foods much as possible, eat 'mindfully', make your own decisions regarding your health and diet and don't buy into anyone's snake oil/capitalistic agenda.
Intuition would make me wager testosterone levels of you average powerlifter would be in the higher ranges (necessary to build muscle), despite not generally being lean.
While Moore's law may be over in terms of number of transistors per chip, we are still seeing growth in the number of cores per CPU, not to mention faster memory and the death of spindle storage.
ImO software will start leaning more heavily towards parallelesim (if it hasn't already, building a threaded or asynchronous application is no longer an arcane dark art). Couple that with the surge in adoption of distributed architecture (yes microservices), and the emergence of languages which encourage pragmatism and efficiency (ala Go and Rust) and I think we'll be okay for the next while. Can't speak to electron though (gross).
One thing the article fails to mention are the boat loads of tooling out there to address the failings of, and complement microservices architecture, of which Kubernetes is only one.
Sure they come with their own levels of complexity, but deploying K8 today is orders of magnitude simpler than it was 4 years ago. The same will hold true for similar tooling in the general microservices/container orchestration domain, such as service mesh (it's a lot simpler to get up and running with Istio or Linkerd than it was 18 months ago), distributed tracing (Jaeger/Opentelemetry) and general observability.
I'd also point out that MS can provide benefits outside of just independent scaling and independent deployment of services, but should in theory also allow for faster velocity in adding new services, all dependent on following effective DDD when scaffolding services, they allow different teams in a large org to design, build and own their own service ecosystem with APIs as contracts between their services and upstream/downstream consumers in their own org and new team members coming onboard should in theory be able to get familiar with a tighter/leaner codebase for a microservice as opposed to wading through thousands of lines of a monoliths code to find/understand the parts relevant to their jobs.
Frameworks catalyse development. It's much easier for a new team member to read the very rich and well explained Django documentation than to pour through reams of poorly documented code for a custom mvc for instance.
This feels like both tilting at windmills and irrational expectations on devs who for the vast majority need to turn out features, not core libraries.