That's a pretty far fetched interpretation of the 1st amendment. It doesn't say "one's religious beliefs supersede the laws enacted by congress". Having religious beliefs doesn't mean I can practice ritual human sacrifice, or sell bleach to people with promises that it cures cancer, or impregnate a harem of child brides. Freedom of speech isn't a get out of jail card either. Most criminal statutes involve speech of some kind. You are not free to commit fraud, to lie to law enforcement, to engage in a criminal conspiracy, etc.
I'm all for magic mushrooms and legalization, but I don't buy this 1st amendment religious exemption bullshit. The law should apply equally to everyone and everything, or it ceases to have any meaning. It's the same as the Supreme Court carving out a religious exemption to the Civil Rights act. There's no good reason why people's woo-woo beliefs somehow changes whether the law applies to them or not. It's ridiculous.
I think an inevitable but mostly untapped direction of research is to leverage biotechnology to manufacture materials to replace plastics, metals, chemicals etc., that either don't have renewable sources or can't be biodegraded back into source material. We can go even further and create new biological machines, bioengineered motors and computers and all kinds of shit scaled up from existing models in nature.
The technology of nature and life is far more advanced than anything we have conjured up ourselves, and the more we learn from it and harness it, the more we will be able to advance and evolve our technological progress without creating all the geopolitical and environmental problems that usually come with these advancements.
I'm not sure you can. If it is possible, it probably requires some open-source tools and a pretty painful process to get the credentials off a hardware token (if that's even possible) and go through the various API calls.
1. There are pretty damned good reasons to use a single sign on (SSO) authentication across all company resources. Managing multiple accounts for every employee across every service is a prohibitively burdensome and messy affair, error-prone, inconsistent in policy enforcement and quality of security, features that would difficult to roll out on your own, the list goes on. SSO is an absolute must in any modern organization.
2. WebAuthn just a marketing scheme? It's a pretty big jump forward in authentication security, protocol, user experience, etc. It eliminates passwords, the cornerstone of authentication for as long as computers have even had authentication, and the #1 cause for security breaches by far. It does away with the need for 2FA. It allows users to use a range of devices to easily authenticate themselves without the need to juggle credentials for every account they have. It uses public/private key cryptography, a robust standard for security for years, uniquely for each site, attested to prevent fake hosts from registering keys, and all automatically managed behind the scenes so nobody has to go through the painful song and dance of creating and managing their own keys anymore. And it does all of this with a universal and open protocol that is currently already baked into most browsers. Seems like a pretty big deal to me, and certainly a big enough deal for huge companies and services like Google, Github, Microsoft, etc. to have prioritized its development and rollout.
Google was one of the earliest adopters of Yubikeys, and they used them for EVERYTHING. When I worked there, we always received 2 keys: one of those itty bitty ones that sits in your USB port permanently, and a regular key that fit into our security badge holder, or you could keep at home, or whatever. The switch to security keys reduced account takeovers to 0:
One of the reasons I got my degree in Biotechnology was because I realized that the technology of life is mind-bogglingly advanced and learning how it does things can have profound insights into how we solve other problems. The process of mutation and evolution is definitely a strong contender for this, maybe one of the most important and powerful.
Considering the fact that you can inject python code blocks, I kind of doubt it. It also makes API calls that populates a dashboard with an inventory of resources created, so it seems to be more of an api wrapper like other IaC solutions.
A rare opinion but one I share wholeheartedly. I started my career at Google Cloud but spent the rest of it working with AWS. AWS always feels like an uphill struggle, lots of micro management and resources that need to be duct-taped together. I'm lucky to have recently landed a Google Cloud gig and my God, things are so much easier and smoother now. It just seems better designed and integrated to me, albeit much fewer services to choose from if you don't buy into their ecosystem.
Terraform, and by extension HCL, is more powerful and flexible. It can be used across clouds. It has providers for all kinds of things, like kubernetes. It can be abstracted and modularized. It supports cool features like workspaces and junk, depending on how you want to use it.
Also recently I was forced to use Google Cloud Deployment Manager scripts for some legacy project we were migrating to Terraform, and I was shocked at how buggy and useless it was. Failed to create resources for no discernible reason, couldn't update existing resources with dependencies, couldn't delete resources, was just unfathomably shit all around. Finished the Terraform migration earlier this morning and everything went off without a hitch, plus we got more coverage for stuff Deployment Manager doesn't support. It's also organized much nicer now, with versioned modules and what-have-you.
Cloudformation is ugly and again, surprisingly isn't well supported by AWS. I don't understand how it's possible, but terraform providers seem to be more up to date with products and APIs. Maybe that's just me but I've seen others complain about the same thing.