deathclassic

Everyone says germline editing would reduce diversity in the gene pool, and I can see validity to that argument. But, could it not do the opposite when people start altering their children to align with their own values? I could see the loss of some universally "bad" genes, but a lot of the judgement on this sort of things gonna come down to who does the gene editing and how they exactly implement it. When multiple groups start doing this in practice, I could see it fracturing the species more than homogenizing it. Especially when combined with something like iterated embryonic stem cell selection when you can jump several generations at a time. That would result in multiple post-human species derived from baseline humanity with their own specializations, talents, etc. Which would be more diverse.

Same. Specifically I would want to be a pharmacologist. There are two major barriers that prevented me from considering this route:

I'm a fairly terrible student and 8 years of school wasn't gonna happen. I can't stand blood/body parts. Even if I got through school I don't think I could stomach a clinical position.

hmmm. Wonder what would happen if you configured a zfs pool with this as the l2arc vdev.

Yeah docker is great and I've done the exact same as you for a few years. But, I don't think I even knew what a docker container was until 2018, and again, as an intern or college kid with a school/work windows workstation telling them to run it in a container is a non starter.

Ever try to install postgres on windows? On a school or work computer you may or may not have admin access on? That's the kind of enviroment a lot of people (including myself) started in. In that sort of enviroment, it's easier to run sqlite3.exe database.db. And that's the kind of enviroment a lot of people (myself included) got started in databases.

Ignore this, I was wrong. Django supports sqlite just fine. Last time I did anything with django I was an intern and just copied the setup from the readme which happened to include a mysql setup. I have not touched django since.

It's been at least 3 years since I did anything with django and that was with mysql.

SQLite has other advantages over larger db systems. - By far easiest db to install. - Really go to learn database fundamentals with.

If you have no experience with databases and are just starting out programming, PG is going to steepen the learning curve substantially.

It would probably be harder to bend Django to use SQLite as a backend then it would be to just setup MySQL or PostGRES and use the existing Django tooling for it.

Also valid. I just use ISO8601 and bite the bullet because storage is cheap.

It's ok until you have to deal with loading a bunch of point cloud or geometry data based on associations and sort it out in memory. Then PostGRES becomes your friend.

Ok JSON maybe wasn't the best example. I wasn't aware that SQLite had those json features though, thanks for the advice.

Blocking can become an issue pretty quickly with SQLite unless you do what this guy does and make a different database for essentially every process writing to the db. This can crop up in all sorts of situations.

For example today I was writing tests for a python application I'm working on that uses SQLite. SQLite is the only option I have for this program as I have literally no way to setup a client server db in it's environment.

I had the tests all configured to write to the same test db file. The program I wrote the tests for had no issues with locking because it doesn't run anything concurrently.

However, when I did the same in my test suite, they ran in parallel, which caused my tests to hang. Of course, I figured this out quickly and made the tests write to their own individual DB. This is a really small program, so cleaning up afterwards is no big deal. (I could also just use an in memory db instance instead of even dealing with files). But, for a program with a LOT of tests, I could see this being an issue.