I guess you can assign 3-4 bits for identifier version number as well.
And yes - for long living data dealing with compatibility issues is inevitable so you have to take that into account from the very beginning.
283 karma · joined June 30, 2017
I guess you can assign 3-4 bits for identifier version number as well.
And yes - for long living data dealing with compatibility issues is inevitable so you have to take that into account from the very beginning.
Using idempotency identifier is the last resort in my book.
Hash index is ideally suited for UUIDs but for some reason Postgres hash indexes cannot be unique.
The solution is not to come up with yet another artificial identifier but to come up with better means of identification taking into account the fact that things change.
git log --first-parent
git bisect --first-parent
The above gives you clean PR history in the main branch while retaining detailed work history in (merged) feature branches.
I really don't understand why would I squash having git merge --no-ff at my disposal...
It is just too risky as there is a hard limit to scalability and while it might look it is high enough for foreseeable future, what am I supposed to do once I reach this limit? Financial database has to be planned with at least 15-20 years of growth in mind.
But the real problem is oppressive government. My government is not oppressive - my government is here to help me and help the society to maintain civil rights.
The view that it is the government that is against civil rights is anarchistic and... wrong. In reality it is the opposite: the only way to maintain civil rights is to have the rule of law and the government that protects them.
What's more: anonymity itself has to be guarded by... the government (and that's what you require). So your logic is twisted: you trust your government to protect anonymity while at the same time you don't trust it to protect freedom of speech.
I have nothing to worry about from my government - that's the important difference.
Maybe oppressive government and lack of freedom of speech is a problem in your country, I don’t know that and I’m sorry for you. My suggestion would be though, that you try to fix your government instead of anonymously requiring online anonymity because you’re afraid of your own government.
I guess here in Poland trying to protect people from theft and violence is more pressing issue than freedom of speech.
So we agree: authoritarian regimes are a gargantuan problem, not stripping away anonymity.
> Trolls are a very minor problem comparatively.
Online predator almost killed my child - this is not a "very minor problem". At least not for me.
> This is essentially saying "freedom needs to come with punishments and restrictions when you do things I don't like". It's an oxymoron.
It is not bout things _I_ don't like but things that _we (society)_ don't like. In my country nazi symbols are forbidden in public space and I think it is a good thing. So yes - "freedom needs to come with punishments and restrictions".
> The responsibilities a free populace have are moral and civil, they aren't about giving away anonymity to governments.
Why not? There are countries which governments are elected by citizens and are _trusted_ by citizens. Why would I want to be anonymous if I _trust_ people I elected?
Secondly: I think you are happy to not being the target of online violence. I have experience with teens on the brink of suicide caused by it.
Broken lives of people harassed by anonymous trolls on social media are the dark side of anonymity.
Freedom must be accompanied by responsibility and accountability.
Object algebras: https://i.cs.hku.hk/~bruno/oa/
Tagless final: https://okmij.org/ftp/tagless-final/course/lecture.pdf
and Data types a’la carte: https://webspace.science.uu.nl/~swier004/publications/2008-j...
I can't find clear information about how re-rendering and stateful third-party components interact.
Let's say I have a stateful data table web component that I use in the template. Is it going to be re-created every time the template is re-rendered (loosing its internal state)?
Most of the times the solution is not pre-aggregation but proper indexes on foreign key columns (missing fk indexes is one of the most common mistakes in RDB design).
Bitcoin adoption is a chicken and egg problem. But my guess is that censoring porn creates a very big incentive for people to start using it.
It is a very liquid asset - easy to move and easy to sell.
I wonder if (when?) we reach a tipping point when people massively start using it. Censoring porn like this looks like a very strong incentive.
Buck and Buck2 from Meta are descendants. Buck2 is an excellent piece of software. Too bad it is still niche.
No - I only expressed my thoughts about using natural language for computing.
Usefulness of LLMs has yet to be proven. So far there is more marketing in it than actual, real world results. Especially comparing to civil and mechanical engineering, maths, electrical engineering and plethora of disciplines and methods that bring real world results.
Using a formal language is a feature, not a bug. It is a cornerstone of all human engineering and scientific activity and is the _reason_ why these disciplines are successful.
What you are describing (ie. ditching formal and using natural language) is moving humanity back towards magical thinking, shamanism and witchcraft.
This part is the most frustrating in discussions about LLMs. Since there are no criteria to measure the quality of your prompting there is really no way to learn the skill. Assessing prompting skills based on the actual results is wrong as it does not isolate the model capabilities.
Hence the whole thing looks a lot like an ancient shamanism.