zbentley

53 ms·

901.
by zbentley 2y ago
My hot take is that the root of this issue is that the destructor side of RAII in general is a bad idea. That is, registering custom code in destructors and running them invisibly, implicitly, maybe sometimes but only if you're poli
902.
by zbentley 2y ago
Live-updated aggregates are quite common in this area. Consider metered billing ("discontinue this ad after it has been served/clicked/rendered X times"), reactive segmentation ("the owner of a store has decided to
903.
by zbentley 2y ago
That would be extremely useful in some domains.
904.
by zbentley 2y ago
All very fair, though I think your issue may be more with the nature of real-time analytics ingestion pipelines in general than with Clickhouse itself. Even if you could remove all of the operational burden from Kafka or equivalent, hooking
905.
by zbentley 2y ago
This isn't appropriate for all use-cases, but one way to address your and GP's problem is as follows: 1. Aggregate (in-memory or on cheap storage) events in the publisher application into batches. 2. Ship those batches to S3/
906.
by zbentley 2y ago
I think this is an instance where, to crib a phrase from the golang world, "share memory by communicating" (i.e. programs that need to support this kind of intervention should provide some form of API) is more appropriate than &qu
907.
by zbentley 2y ago
I don't think there is, or should be, a way to do that. Granular copying of per-process resource state seems like a need that would be better served at either a closer-to-the-program layer (i.e. debug hooks in code you control that pro
908.
by zbentley 2y ago
Not sure how tongue-in-cheek that was, but I think your statement is the heart of the problem. Investment money chases confidence and moonshots rather than backing organizations that pitch a more pragmatic (read: asterisks and unknowns) app
909.
by zbentley 2y ago
You’re welcome! One more issue that I missed calling out: a bottle may not yet be available for your platform (Sequoia) as it is very new. In that case, patience.
910.
by zbentley 2y ago
Your Homebrew may not be configured to pull only the runtime dependencies; as others in this thread have mentioned, it's pulling in all those dependencies becauase it's building "eza" (or something, perhaps one of "
911.
by zbentley 2y ago
> It’s doing hash table lookups per variable access. That hasn't been true for many variable accesses for a very long time. LOAD_FAST, LOAD_CONST, and (sometimes) LOAD_DEREF provide references to variables via pointer offset + chasi
912.
by zbentley 2y ago
> Using shared memory for IPC is like using C or C++ and saying "well I'll be careful then" Sort of. In the replatforming/codebase conversion case, the amount of care and labor needed to effectively use shared memory
913.
by zbentley 2y ago
The observability tools in question (strace) follow the UNIX tradition of displaying and processing data as text by default. I don’t think that means that they suck. I’ll go even stronger than that: IPC and RPC should prefer plaintext-rep
914.
by zbentley 2y ago
The first alloc will be really early on in even trivial Python programs, so that’s not a good heuristic. It’s hard to pick a good heuristic in this area because the line between startup time and runtime is so blurry in platforms that suppor
915.
by zbentley 2y ago
> Shared memory works as a transport if you either assume that all parties are trusted (in which case why do IPC in the first place? Just put them in a monolith) There are all sorts of domains where mutually-trusted parties need IPC. Off
916.
by zbentley 2y ago
Not true at all. > Zsh is different from bash Ubuntu has had a non-Bash system shell (dash is /bin/sh) since 6.10. > no systemd Without getting into objected-on-principle distributions like Devuan, tons of stripped-down and
917.
by zbentley 2y ago
That was true, but the more recent Quorum queues provide more traditional scalability tradeoffs (you can set a ceiling on the number of synchronous replication hops that a published, replicated message goes through): https://www.
918.
by zbentley 2y ago
How would that work? Do you only access a really small/known set of IPs? Or would you program the firewall to only allow connections to an arbitrary IP if it had seen a DNS query to your preferred servers go out and return that IP with
919.
by zbentley 2y ago
Have private equity types been seen entering the building?
920.
by zbentley 2y ago
I'd say Python works well at greppability because community conventions generally discourage concealing certain kinds of definitions (e.g. function definitions are usually "def whatever"). However, that's just convention
921.
by zbentley 2y ago
Yep. And while that’s not something I’d call a mistake per se , it can be troublesome. What if a crate you depend on at different versions provides access to global state? What if a transitive embeds definitions from that crate into public
922.
by zbentley 2y ago
Virtualenvs solve not having separate workspace-local package installations, not a lack of versioned imports. Versioned imports are not a good solution to separate installations of packages: code is harder to upgrade, cluttered, and encour
923.
by zbentley 2y ago
How would you launch the python interpreter if its binary is missing execute permissions?
924.
by zbentley 2y ago
Maybe, but what if in return smartphones weighed and cost 1/10 as much?
925.
by zbentley 2y ago
C libraries compiled with -ffast-math would like a word…
926.
by zbentley 2y ago
Interesting! Can you compare this to traditional web/enterprise pub-sub systems? Obviously this has a lot more custom network code, but is it otherwise analogous to something like NATS or a brokered (but stateless/unbuffered) topi
927.
Deprecating the Observer Pattern with Scala.React (2012)(infoscience.epfl.ch)
1 points by zbentley 2y ago|0 comments
928.
by zbentley 2y ago
I'm not sure I interpret that as trusting the client; rather, it seems like the implication is that HTTP limits will be handled correctly by webserver harnesses, whereas WebSockets may not get any such behavior "for free" fro
929.
by zbentley 2y ago
The "--only-binary=:all:" option should force Pip to only install packages that provide wheels, which doesn't run arbitrary setup.py code (right? I've been assuming it doesn't and really hope that is a valid assum
930.
by zbentley 2y ago
> This led to classic bugs where the function returns a pointer to a local value. Compilers now usually catch this. C eventually got structure return by copy. Then C++ added return value by move, and automatic optimization for that. Jesu

More ›