kiitos

37 ms·

481.
by kiitos 2y ago
https://p-org.github.io/P/getstarted/install/ > [Step 1] Install .Net Core SDK > > The P compiler is implemented in C# ... > > [Step 2] Install Java Runtime Good luck!
482.
by kiitos 2y ago
> What Activity Monitor actually shows as % CPU or “percentage of CPU capability that’s being used” is what’s better known as active residency of each core, that’s the percentage of processor cycles that aren’t idle, but actively process
483.
by kiitos 2y ago
Yeah, definitely not suggesting domains are a better form of identity!
484.
by kiitos 2y ago
DIDs are stable only in the context of a specific 'verifiable data registry' as the spec puts it. https://www.w3.org/TR/did-core/#dfn-verifiable-data-registry DIDs delegate trust and authority to a data
485.
by kiitos 2y ago
> the convention on the function authoring side is to always ensure T is valid. I'm not sure where you got this idea from. It's not (in the general case) true. But do as you like, of course.
486.
by kiitos 2y ago
> Consider the case of (T, error). T should always be useable, regardless of error. Go convention dictates that T is only valid (usable) when error is nil. Equivalently, if error is non-nil, then T is invalid (unusable). In either case,
487.
by kiitos 2y ago
Any function that returns an error obliges its callers to check that returned error before attempting to use any other returned value. This is Go 101 type stuff.
488.
by kiitos 2y ago
You're using a definition of 'memory safety' which is not common.
489.
by kiitos 2y ago
Appending to slices concurrently, without synchronization, is unambiguously invalid code.
490.
by kiitos 2y ago
Even when a value satisfies these architecture-dependent requirements, the language still does not guarantee atomicity of concurrent reads/writes, and programs which rely on that assumption are buggy.
491.
by kiitos 2y ago
What? HTTP is just a protocol. Stateful or stateless is orthogonal. HTTP is both and neither. Also, HTTP has no concept of files (in general), only resources. Files can be resources! Resources are not files.
492.
by kiitos 2y ago
The folks who maintain system-level package managers (apt, rpm, etc.) love to equivocate their stuff with language-level package/dependency managers. But the folks who maintain language-level package/dependency managers essentiall
493.
by kiitos 2y ago
> Personally, I think the biggest problem with HTTP is that its a file access protocol, a state interchange protocol and an authentication system. HTTP is a state interchange protocol. It's not any of the other things you mention.
494.
by kiitos 2y ago
Repetition at the syntactic level, as you describe here, is, statistically, zero percent of the time spent in any meaningful software project. It, quite literally, doesn't matter. Time spent by authors typing source code characters int
495.
by kiitos 2y ago
No need for any func, you can just grep '\) methodName\('
496.
by kiitos 2y ago
Interfaces are consumer contracts, they say "I need this" not "I provide this". Regardless, any reasonable LSP will let you "Find implementations" of any interface definition.
497.
by kiitos 2y ago
Wild that you don't distinguish between error handling and name repetition.
498.
by kiitos 2y ago
80 _is_ impractically narrow. Even 120 is overly strict. SLoC line length isn't something that can or should be enforced by linters, or re-formatted by formatters.
499.
by kiitos 2y ago
It would be a mistake to try to solve this problem with regexes.
500.
by kiitos 2y ago
It does not. Believe what you will.
501.
by kiitos 2y ago
I don't need to change the definition. The existing (canonical, well-understood, etc. etc.) definition of a CRDT clearly excludes blockchain data structures.
502.
by kiitos 2y ago
I'm not sure what your original skeptical position is, so shrug?
503.
by kiitos 2y ago
> The rules are that state merges must be commutative, associative and idempotent; Yes! > if blockchains fulfill all three criteria, I don’t see why they wouldn’t count. Blockchains definitely do not fulfill all three criteria! > I
504.
by kiitos 2y ago
Feel free to read up on CRDTs; I'm confident this will answer your question. The short answer is, roughly, that a conflict is a discrepancy in state which cannot be mechanically resolved.
505.
by kiitos 2y ago
The "blockchain" notion of determinism you're referring to here, is far weaker than the notion of determinism used in the distsys context. This discrepancy was pretty well documented in the Jepsen analysis of the Radix DLT --
506.
by kiitos 2y ago
> So then Git uses a CRDT internally? No. Factually, inarguably, no. If you want to argue against this claim, OK, have fun, but it's not interesting to engage, because there's no interesting conversation to be had. However, if
507.
by kiitos 2y ago
Blockchains absolutely do not satisfy the definition of a CRDT.
508.
by kiitos 2y ago
Do you care that you're wrong, or... ? Pedantry doesn't enter into the discussion -- the definitions at play here aren't subject to any kind of subjective interpretation.
509.
by kiitos 2y ago
This is definitely not true. Are you open to understanding why this isn't true? If so, I'm happy to help you come to the correct understanding; please ask whatever questions are necessary. Otherwise, then, well, okay!
510.
by kiitos 2y ago
Immutability is a fundamental property of a language, it's not something that can be bolted on post-facto in a version update. Go as a language doesn't provide immutability.

More ›