dom0

41 ms·

391.
by dom0 9y ago
> Erlang What the fuck. And I thought constant-time indexable strings were a bad idea!
392.
by dom0 9y ago
> The only exception I can think of is the difficulty in getting a bytestream version of standard output. sys.{stderr, stdout, stdin}.buffer
393.
by dom0 9y ago
The issue w.r.t. paths is that paths have different types depending on the operating system. On Linux and most BSDs paths are bytes. On some Unices they are bytes, but must be in a specific encoding (e.g. macOS => UTF-8). On others, they
394.
by dom0 9y ago
The comparison is interesting, but CPython's lavish use of memory (which of course has a performance impact by clogging caches, though that's one of the least problems you have with CPython, performance wise) is well known. ¹ This
395.
by dom0 9y ago
> This means taking consistent backups is not straightforward. And they're not even straightforward to begin with...
396.
by dom0 9y ago
The whole idea of building an ecosystem of an open ISA with open implementations, where the ISA can be extended for specific applications . See e.g. https://riscv.org/wp-content/uploads/2016/12/Tue1100-R
397.
by dom0 9y ago
That's an entirely valid line of reasoning, but it only applies to a certain set of applications. Further, SQS or whatever have the same drawbacks as other external queues compared to an in-DB queue; see all the sibling comments in thi
398.
by dom0 9y ago
> If the success of RISC architectures taught us anything, it's that replacing simple primitive operations with special-purpose combinations is rarely worth the transistors. RISC-V argues the exact opposite :)
399.
by dom0 9y ago
The row lock is held by the RDBMS itself on behalf of the client. When the client goes away, times out (configuration) etc. -- the transaction aborts -- then the RDBMS releases it. You don't get exactly once here, because between per
400.
by dom0 9y ago
> Why use a database as a queue? Already have a central, configured and monitored server and need "just a small queue" for something. This is not per se a bad decision. For the same reason it doesn't have to be a bad idea
401.
by dom0 9y ago
You should perhaps mention that your examples are also written in a Lisp dialect which is a rather different thing from your average 90s script language.
402.
by dom0 9y ago
> Currently, diversity initiatives’ strongest accomplishment may actually be protecting the organization from litigation Cynical: works as intended?
403.
by dom0 9y ago
Lisp has nothing to do (in many ways) with the late 80s and 90s wave of dynamic languages.
404.
by dom0 9y ago
> Any idea as to why implicit casts aren't more supported in strictly typed languages? That's the difference between weakly and strongly typed. If you take a strongly typed language, and add implicit casting, you get a weakly t
405.
by dom0 9y ago
Type systems can enforce so much more, depending on the language. They make reasoning about the code far easier for both human and machine. They enable efficient optimization. They allow far superior static analysis. They allow superior IDE
406.
by dom0 9y ago
Annotations at least help the IDE dig through the mess faster. That's ... something. I guess.
407.
by dom0 9y ago
> It's just that dynamic languages outcompeted them. All "trending" languages are statically typed (Rust, Go, Swift, Kotlin, ...) and all the popular JavaScrip-improved-languages are statically typed as well. Even further,
408.
by dom0 9y ago
Most of these languages are pretty terrible to run at scale. Also, all of the examples you cite a rather the "in spite of" kind. Wikipedia? Struggles to maintain the code base, lest to speak of significant new development. Wordpre
409.
by dom0 9y ago
Thank you, that's a good and important point. It also has the angle that the CA can't accidentally "miss" anything, since the certificate is not constructed from client-supplied data (=> voila, we're at Langsec :
410.
by dom0 9y ago
Thank you for an insightful answer.
411.
by dom0 9y ago
On the one hand, yes, if you're looking at the API design and the docs from a "clean slate" perspective, then they are clearly not very good. [1] On the other hand, matplotlib is ridiculously powerful as an embedded plotting
412.
by dom0 9y ago
Zen has shown excellent efficiency figures for both the CPU itself and entire systems. That does not necessarily translate to good mobile systems, but is a good sign.
413.
by dom0 9y ago
The same is btw. true for SATA, SCSI, SAS: the "DMA modes" (UDMA etc.) mean that the host controller is doing DMA transfers, while SATA drives cannot initiate nor control DMA transfers.
414.
by dom0 9y ago
No, RVO is about the compiler silently moving the on-stack location of the "returned" object into the callers frame .
415.
by dom0 9y ago
Why does Go not use LLVM? Are there technical reasons to reinvent the wheel, or is it just because LLVM is Apple's pet?
416.
by dom0 9y ago
??? EV guidelines have nothing to do with Let's Encrypt or ACME. They state that even for renewal all checks have to be done again, which cannot be automated .
417.
by dom0 9y ago
acme.sh + static verification is indeed a very nice zero maintenance solution.
418.
by dom0 9y ago
> A user wants to get the public key for a certain domain. So he knows he is talking to a server by the domain owner and not some man in the middle. > So he asks a third party whos public key he already has. In this case Let's En
419.
by dom0 9y ago
acme.sh reduces SSL deployment to fifteen minutes with virtually no maintenance.
420.
by dom0 9y ago
EV certificates are not allowed to be renewed automatically AFAIK.

More ›