That's not of my business, I cant protect people from themselves, and even if I could, I think it's wrong to protect somebody by restricting the options. Anyway... those arguments will never make a point against sharing an open tool.
I already did. Here is how to createa a self-hosted VPN server at a cloud provider of your choice. Don't trust your network traffic to anyone but yourself:
> Don't trust your network traffic to anyone but yourself
You still trust the cloud providers' upstream. In case of UK providers, the GCHQ sniffs upstream and ingress, so they can correlate traffic. Same for DE (BND, MAD) and basically all countries.
Yes, and you also have to trust your home ISPs upstream, and the routers upstream from that, and so on and so forth. Are you trying to say that using a VPN is useless?
> Are you trying to say that using a VPN is useless?
No, but you're making your traffic stick out and yourself a target for dragnet surveillance. The constant flow "packet in, other packet out" is easy to pick up for snoops, compared to "just packets out" from your home ISP.
Do you have users in China? I'm curious whether IKEv2 works well through GFW. I use Shadowsocks (on my Asus router, and on my Android/iOS devices), and it works well.
What would I gain in ease-of-use, performance, or security by switching to Algo?
That's a common refrain. It's just that I don't think there's a good idea on which to build/improve. I commend you for putting (presumably) your work out here for all to see, and good on you for making your project FOSS, but this is not a project I will support.
You know why many SQL databases use a lot of RAM? Because it improves their performance. They don't require the RAM, they just use it when it's available. Would you rather that it uses your free RAM to speed up your database operations, or to just have it sit idle doing nothing?
As for not being "the only choice" - while technically correct, this is very misleading. SQL databases and schemaless/document stores are _not interchangeable_. They are used for different usecases with different data models and different integrity requirements.
MongoDB is a special one entirely - even for a schemaless document store, it's just very poorly designed and maintained. Use any of the many other such databases - which gained a reputation by actually working well in production, rather than its developers organizing lots of hackathons as a marketing stunt.
1. SQLite isn't heavy. There are probably even lighter-weight relational solutions, but I haven't needed one, so I haven't looked.
2. Even among non-relational document storage solutions, Mongo has a poor reputation. As someone else says elsewhere in the comments, it's hard to trust a team that let so many ridiculously dangerous bugs (and a basically unreliable design) out into production for so long.
No SQLite isn't heavy but I hope you mean for use in development only.
The issue isn't MongoDB is bad and relational DBs are awesome. The real issue is new developers being taught that Mongo and NoSQL in general are the databases you should be using with Node. The problem secondary to that is devs not knowing when each is appropriate.
It's actually commonly used in production for certain types of databases. SQLite is not a replacement for something such as postgresql but it certainly has it's use cases.
The use case for SQLite isn't high traffic public facing webpages. Here is their own list of 'famous' users: https://www.sqlite.org/famous.html
Every iPhone, and Android phone have SQLite running on them, which easily makes it the most used production database. It's use case is typically very low traffic websites or as client side storage.
Maybe I'm missing something but is Mongo in use on the client side in that same way? If not then SQLlite is being shoehorned into the discussion and the context in which production was used should be clear. I feel like people are trying to be technically right instead of following the actual discussion. I never meant client side software and definitely didn't mean someone's micro traffic blog, where a toy database could be used.
It is interesting how much penetration SQLlite has on the client, though.
At any rate, I know better than to not be extremely specific so I brought this on myself.
It seems like there have just been some assumptions going both ways.
This all started when someone trashed RDBMS for being "heavy", implying that Mongo is good because it's light.
Why would you care how heavy a DB is if it's not on the client side? The kind of memory and storage you need for even the heaviest popular RDBMS (MySQL?) is still low enough that's nearly free to create a small app.
It is a very early project. I want to improve it in the future.
The cool part is that it uses dontpad as a database :P