You seem to have a rather limited understanding of what kinds of concurrency exist and how those needs are best met. Whether something is a server or not is not very relevant to this discussion.
SQLite is an excellent production db for many real world workloads, as has been widely documented. It is very different to Postgres, so requires learning a whole new skill set.
One way to think about it is that SQLite can work well for the parts of your system where there is naturally strong partitioning.
You can do big data in SQLite. Concurrent writes, sure, I'd recommend something else.
If you think the majority of systems require massively concurrent writes, I think you need to look a bit harder. SQLite is, after all, the most widely deployed database system, ever.
Yes, which goes in line with the argument that claiming that it's "the most deployed" as proof of superiority or suitability for any use case is equivalent to claiming the same for Internet Explorer. It's the most deployed because it's bundled in a lot of systems, not because people are purposefully using it as a DBMS.
But it doesn't, because none of those systems are presenting SQLite to the user as something they should be using; they don't even make SQLite available to the user at all. Those systems all use SQLite internally to manage data.
We recently just partitioned the data into many SQLite databases and got away with it. It's telemetry data from IoT devices: one device, one database. Backups are an easy rsync job now instead of streaming a multi gigabyte database with compression that take hours. Reporting will just open each database and aggregate multi device data into another database (Duckdb, SQLite or something else, we'll see). Duckdb is not readable when locked so it's probably also going to be SQLite. Even it it's going to spit out JSON it will go into SQLite rows instead of many files.
I saw that but it's a bit too much friction. We'd rather attach a SQLite database and copy the results into that. Also no worries about version changes and compatibility, the types are not too restrictive. But we'll see.
It’s widely deployed as a local DB for local apps like phones, desktops, and web browsers. But it’s not the most used for distributed, concurrent web apps, which db servers were designed for. Maybe people are talking past each other, but that’s the debate I see.
I couldn't find a CPAP mask that worked for me, even after 6 months of trying across 4 different masks.
Then I read studies showing oropharyngeal exercises can help treat sleep apnea. Originally I used https://snoregym.com/ for that, but then I switched to simply chewing gum once a day (being careful to chew on both sides of my mouth roughly equally), and also chewing my food a bit longer.
I was fully prepared to have to go through the entire gamut of masks to find one that worked, because I snore so surely I would need a mask that covers my mouth at least, right?
But even while sleeping, my brain is keeping my mouth shut so the simplest, nose-only mask works perfectly, with very little leakage.
q and ch both exist in pinyin, and have different sounds. The q sound requires placing the tip of the tongue on the teeth, and isn’t an initial consonant we have in English, so we don’t have a way to spell it.
TIL HN still doesn't support rfc3492, 23 years after it was published, and so this domain is not rendered correctly on the site. :(
(It should appear as: マリウス.com )
Nowhere does RFC 3492 say that browsers MUST render IDNs in the original language, so I think saying "HN does not support" this RFC is false, or at least disputable. Personally I strongly prefer having it in untranslated Punycode to avoid scams; IMO everyone should browse the web with Punycode disabled.
Perhaps I'm misreading something? From my reading of the article, it doesn't sound like Anthropic offered to let him use Mythos in any other way than that.
He explains in the article that he failed to actually secure access in the end, even though it was approved. Someone else prompted the model on his behalf, and just passed on the findings.
There's always someone making this claim when negative comments about AWS come up.
They almost always come from people that don't have experience running substantive infra at scale without AWS, so they can't make an informed comparison. The complexity of doing so, for a lot of infra, turns out to be lower than using AWS. Also, you end up with transferable skills and a deeper understanding of the foundational protocols and systems. And you save a lot of money, both because you don't have to pay to manage that complexity, and the systems themselves are cheaper.
It's super difficult on a psuedo-anonymous forum to discern if a comment comes from a neutral place or a heavily biased one.
This is made even worse when there's a financial or reputational incentive for people to parrot something. If I had invested the bulk of my professional career in Microsoft: I would be genuinely uncomfortable with criticism. I would subconsciously feel threatened and would work to convince myself and others that it's not so bad, or that criticisms are overblown.
This is even more true if the company actively spends (your companies) money to make you feel good. You neither feel the actual pinch of the financials and you feel good about the company.
It's really clever, and we're emotional animals: so we don't always make the most pragmatic choices.
The statement “there exists a project where zig led to an extremely high amount of crashes/memory bugs” does not imply “all zig projects have an extremely high amount of crashes/memory bugs”.
This is a classic logic problem - eg “there is an orange cat” doesn’t imply “all cats are orange”.
Indeed, considering the much of the cost in the end consists of carrying costs, litigation, and year-of-expenditure overruns that were caused by the delay.
Yeah this has always been the glaring blind spot for most of the "AI Safety" community; and most of the proposals for "improving" AI safety actually make these risks far worse and far more likely.
It makes quite a lot of sense to focus on reducing the risks of every human everywhere dying, rather than the risks of already existing oppression getting worse.
No, you are deeply misunderstanding the issue. Creating a rivalrous good that powers fight over for control, then use violence to maintain control of, creating a global feudalism, is not "existing oppression getting worse". It actually makes the risks of every human everywhere dying far higher, and even if that doesn't happen, decreases global utility by a similar percentage (99%, instead of 100%). It could actually be worse, if average human utility becomes negative.
GPL was created as a workaround for copyright - it wouldn’t have been needed if there wasn’t copyright. There are complex arguments both for and against copyright and there’s no reason to simply assume it must always be just as now even as circumstances change.
SQLite is an excellent production db for many real world workloads, as has been widely documented. It is very different to Postgres, so requires learning a whole new skill set.
One way to think about it is that SQLite can work well for the parts of your system where there is naturally strong partitioning.
reply