Sqlite implements all of the features you would expect from a relational database, including indexes, transactions, write ahead logging, consistency, and provides a SQL wrapper on top of its file API. _This is what makes it a database and not just a file format_. To the client, whether or not the API is happening over a socket or a locally linked library is irrelevant. How connection pooling works is also not relevant to whether it is a database or just a file format.
Calling Sqlite just a file format is kind of like calling Python "just a syntax specification." That's part of it, but we're talking about the actual implementation of it (probably CPython).
You're right, and it is only recently that this stuff became free anyways, sometime last year. I think Amazon's OpenDistro stuff put some pressure on them. Even TLS was gated, which was the biggest offense in my opinion!
This is not true, you can use some xpack security features such as basic auth, client TLS and node-to-node TLS for free. We use basic auth (with Vault integration) at my company using just the basic license. https://www.elastic.co/subscriptions has details on the subscription levels.
I don't get why it ever needs to be on the internet even when it does have authentication. Surely the public/private subnet split is a common practice.
This is kind of like saying "its technically not illegal!", in the same way it's not illegal to open the door for someone and then shut it as they are about to walk through. We are talking about social contracts that are not written but are collectively understood to some degree.
> Like it or not, there are implicit social contracts if you maintain OSS software.
I think I agree, and its tricky because its really hard to pinpoint what the contract is (without sounding "entitled"), like there is with any social contract I guess. Maybe it even depends on the various cultures of the people working on the project.
These both look cool. I've learned some Vue in the past but I strongly prefer these kinds of small, self contained libraries for my Flask + PicnicCSS + very simple JS apps.
There's always a surge in people who defend and even mimic Linus's tone whenever a post like this gets popular. People love being that smart guy who gets to feels entitled to act obnoxiously because they're right - at least about one small thing. Reminds me of _that_ group in High School.
It sounds like there was an expectation that Linux should support something that it doesn't, and whether it _should_ support it is up for debate. Totally agree about Linus's involvement in any communities.
I assume part of it is that he feels personally attacked when something about Linux is challenged.
Yeah I'm on your side here. This fear of AI medicine creating false positives that overwhelm hospitals and doctors and cause unnecessary and risky surgery is one of those ideas I see floating around comments here and there, and it doesn't seem to be backed in anything tangible. I mean maybe it's a concern, but it also seems like that if it ever happened, we'd adjust for it quickly.
I think the things you think are controversial are not the things that others consider controversial, and you should be aware of any bubbles you might be in. Anything that puts your job, employability, and social standing on the line takes a non-negligible amount of courage - let's not move the goal post by trying to classify what is "great courage" or not.
> I cannot imagine how you'd come to the conclusion that holding moderate viewpoints requires any real courage at all.
Expressing moderate opinions on the internet will cause a lot of people of accusing you of being a "fence-sitter" or siding with "the enemy", as well as accusations that you are a coward by people who are agitated that the opinions they hold in such high regard are not shared and are even challenged. It is inviting vitriol from people highly polarized on either side.
It's gotten to the point where when I read an article, I will move my mouse around to try and trigger the "Subscribe to our Newsletter" popup, so I can close it instead of accidentally triggering it as I read the article.
It is definitely concerning. 10 years ago I wasn't worried about putting my data in things like Dropbox because the general fear was "what if they go out of business?" to which I felt reasonably secure that I'd have time to get my data out of there before they shut down for good.
Now, it's much more likely that you'll get a "You have violated our Terms of Service and are banned from using <the service>", pointing you to a line that looks like: "The company may, at its sole discretion, decide what constitutes a violation of the Terms of Service, and terminate services as a result." It happens!
I've only been in the industry for 6 years, not counting my student programming job, and I've started to take tutorial-style notes for myself for all the technology jobs. For a part infrastructure, part software engineer person like myself, you're right there's a massive amount of tools you need to know and be a semi-expert in. There's no way I can hold it all in my head. I'm using mdbook and a very simple git workflow to build up a nice searchable notebook, so when I learn a new topic, I can learn it in a detailed way and take some notes that are tailored to how I re-learn. It's taken a huge burden off of me to constantly have every technology in my head.
I don't know about the rest of the software but Mattermost is easy to administer and requires minimal babysitting. I have it deployed with a simple docker-compose file which I only touch when I want to upgrade it, and there are Helm charts if you want a more production grade deployment. If I were to deploy it for my company I'd probably use the helm chart + a cloud hosted Postgres as the database and would likely never have to touch it between upgrades.
We don't have anything publicly available unfortunately, but we call ansible-pull the instance userdata to configure the host on startup. IAM Policies and Vault integration are used to grant the host access to certain secrets needed by the ansible run.
We just use ansible for the provisioning of EC2 instances, and Terraform for the actual orchestration of the resources. Userdata is used to call ansible-pull. Theoretically we can use Ansible for everything, but Terraform's planning makes the runs a lot safer, and in general it just seems a little nicer for orchestration.
We use the userdata to call ansible-pull so that we can just terminate and re-create instances when we want to re-provision them. We use Terraform for the actual orchestration of the cloud environment.
We use ansible-pull to decentralize our Ansible runs as much as possible, but we also use Hashicorp Vault's SSH Key Certificates functionality to make sure our SSH keys are short-lived when we run it from CI. The last thing we want is CI with a bunch of root level keys on it!
Yeah that's where I'm at. There's this general sentiment that if AI does not solve everything immediately, then it is worthless and hype. Especially the part about not being able to deal with corner cases, forgetting that all AI needs to be valuable is to deal with such cases better than your average human, which isn't a very high bar.
Good article. I would add one thing to this - pick a database that scales horizontally and is distributed. CockroachDB, Elasticsearch, Mongo, Cassandra/Scylla are all good choices. If you lose one node, you don't have to be afraid of your cluster going down, meaning you can do maintenance and reconfiguration without downtime. If your load is low or bursty you can even get away with running these on some small servers such as t3 (probably minimally t3.larges). Running a cloud managed database is also a good option.
If buildings catching fires easily was a real problem, then yes one major event would be a wake-up call to everyone else to provide a real solution to the problem.
One thing I fully believe led to Go's adoption is its feature-rich standard library. SSL connections, JSON parsing, HTTP and the like are all things that would be a major impediment if it was up to the developer to find some generally well accepted 3rd party module on Github and hope it stays maintained and stable.
I know its at least a year out but I'm personally looking forward to the 600Mhz 5G rollout - theoretically the range will be unbelievable. I don't want gigabit speeds when I'm 50 feet from a tower, I want 10mbps wherever I am!
It's probably both, but for me, I follow a pretty non-political group of people, but Twitter will absolutely insist on presenting me inflammatory and polarizing tweets just because someone I follow or someone popular engaged with that tweet. Facebook does not do this, at least for me it doesn't.
I agree that everything should be made in a memory safe-by-default language like Rust and I really need to see the Rust ecosystem really commit to this. Too many times will I come across a library with some very questionable uses of `unsafe`, which in my opinion has no place in things like HTTP request libraries or web frameworks.