421 karma · joined November 11, 2021
> In his landmark book The Art of Computer Programming, legendary computer scientist Donald Knuth noted that although the first binary search algorithm was published by John Mauchly in 1946, the first bug-free version was not published until 1962—taking a staggering 16 years to get right.
10m is larger than current resident counts, so people moving in can decide now if they want to move with uncertainty. It is not what everyone would like, but it is more understandable that recent Swedish changes, for example.
> doesn’t pose any constraints on the type of data.
logic, raw disk is also a database. One just need to add block level replication to other nodes to build a replicated/ HA database.
We may not agree, but anything not providing transactions across logically related multiple data read/ update operations is not a database.
> multiple instances to provide the same data
is easy and done by a bunch of software out there, but
> multiple instances to provide the same data on non-shared memory computers, with consistency
is a really hard problem, and no one has been able to solve it yet without introducing other problems to be considered (giving up on fast performance being one of the most visible one) by architects/ developers.
To put the simple terms... App writes to node-A, node-A (/process on node-A) crashes before change is synced from node-A to node-B, data is lost.
This is true for redis and true for postgresql/ mysql or any similar database. Difference between redis and a "database" is that database protects against this problem by writing change to durable storage before telling app that write is successful. Redis
So if one wants to have a consistent session storage, one should use a proper database or use AOF redis persistense with single node (https://chatgpt.com/s/t_6a24ab818e2881918db959cec8d8cc2d)
No, redis is a memory cache, with some ACID like features bolt on.
Even real databases have hard time maintaining consistency across nodes. CAP is a real constraint.
Just to put things in context, https://www.bbc.com/news/articles/ce8444gex65o shares income for a good number of people now a days. (note that many of those workers are taking care of a family of 2+ members, most of the time)
That is way to high recurring cost that many won't be able to afford. One could get a second hand calculator or even computer, and then additional resources needed was one's willingness. With mandating AI usage, we'd only increase the gap of haves and have-nots. I personally do not like the idea.
I personally have no qualms about one criminal extorted by another, specially if their fued is making world better for everyone.
https://www.haproxy.com/blog/route-ssh-connections-with-hapr...
from the blog
> Did you know that you can proxy SSH connections through HAProxy and route based on hostname?
But if I interpret the question with line of thinking "should I anticipate right/ full answers despite incorrect/ incomplete inputs?" I think Baggage was pointing out the problem in the logic why such questions should arise.
I would expect the question to be phrased "under what circumstances the machine with provide wrong outputs?", and would have hoped for Babbage (or may be anyone) explaining many ways how things could go wrong.
I guess many of us quality for british parliament.
I guess it's futile to argue in this circular logic when full picture is not considered and argument are being put forward only for the sake of winning argument. Have a good $time_of_day.
this guy's forked MIT'd version 0 will be as real and valid as version 6 of original chardet.
instead of
> Your fork of version 6 is just as real and valid as the MIT'd version 7!
Supporting for a decade is not a basis for unilateral takeover. In last 3 months there seem to be at least 3 other active contributors, any many dozens in past, who share the copyright on parts (ownership)
> nobody is entitled to this guy's pip account or GitHub account just because he rewrote the library
this guy's also not entitled to takeover what is communal, exactly in the same manner.
Someone answered it long ago in quite some details. Feel free to have a look: https://stackoverflow.com/a/11455485
First reason would be use the "name recall", and second guess would be to do another rug-pull to re-licence under some other conditions.
> It's owned by the maintainer
This is completely in-correct. GPL and variants (FOSS, not OSS) were meant to make software free of "any ownership".
my understanding of the situation is:
Is the caretaker paying from his own pocket to maintain the hall? no
Is the caretaker paying from his own pocket for community usage of the hall? no
Is the caretaker spending time to maintain the community hall? yes
Is caretaker obliged to spend time on community hall? no
Is caretaker free to stop spending time on community hall? yes.
Is caretaker free to raze current hall, build new hall on same ground for new purposes WITH community agreement? YES
Is caretaker free to raze current hall, build new hall on same ground for new purposes WITHOUT community agreement (even if paying all the bill)? NO
Is caretaker free to build another similar hall someplace else? YES
Reasoning of your comment is of someone who is hell bent on staking claims on community resources (like big companies) without having slightest concern of the wishes or well-being of the community. Not sure of the commenter's motive either, given the new account with just two comments, supporting such blatant disregard of basic human decency.
It should be perfectly ok (by maintainer or anyone for that mater) to be inspired from a community project and build something from scratch hand-crafting/ AI sloping, as long as the imitation is given a new name/ identity.
What rubbed me off personally was maintainer saying "pin your dependncies to version 6.0.0 or 5.x.x", as if maintainer owns the project. maintainer role is more akin to serve the community, not rule.
If it is completely new, why not start a new project with new name? No one will object. And of course leave the old project behind to whoever is willing to maintain it. And if the new name project is better, people will follow.
I first hand saw in, AWS devDays, an AI giving SIWINCH as "root-cause" of Apache error in a containerized process is in EKS for a backend FCGI process connection error. It has been extremely hard since that demo to trust any AI for system level debugging.