<beneroth>
I've had a case where (set> . +Entity) removed/NILed the objects (+List +Joint) properties (it had two), even when the relationship is absolutely the same in the new class
<beneroth>
okay, I'll investigate the cause and come back to you
<Regenaxer>
ok, no idea atm
<beneroth>
I'll look into it.
<Regenaxer>
razzy, not sure here too
mtsd has quit [Quit: Leaving]
<tankf33der>
razzy: I know what is it.
<tankf33der>
your llvm eco system is broken.
<tankf33der>
ah, stop
<tankf33der>
E: Nelze najít balík libffi #cannot find libffi
<miskatonic>
one lvvm version for every architecture?
<tankf33der>
no
<tankf33der>
for void linux crystal lang requires specific version of llvm as dependecy, but mainstream went forward
<tankf33der>
something is broken too.
<tankf33der>
all above is trivial if you know understand the things.
<tankf33der>
who cares. :)
KingRiver has quit [Ping timeout: 272 seconds]
<aw->
beneroth: you here?
<beneroth>
just about to leave
<aw->
ok let me know when you're back
<aw->
nothing urgent
<beneroth>
okay
<beneroth>
afk
miskatonic has quit [Quit: ERC (IRC client for Emacs 24.5.1)]
KingRiver has joined #picolisp
KingRiver has quit [Ping timeout: 265 seconds]
<beneroth>
aw-, re
<aw->
hi
<aw->
what do you think of Consul and other similar Hashicorp tools (Serf, Nomad..)
<beneroth>
heard about it, never used it, never had any need for it, and I also haven't seen it yet at client companies
<beneroth>
my stuff is not on cloud-scale yet, so I'm happy with some simple VPS/standard linux servers
razzy has quit [Ping timeout: 258 seconds]
<beneroth>
I have clients who make use of clouds, but so far without such tooling, also because their projects are individually too small to benefit from it. Generally they work with one or multiple cloud vendors, but without integration
<beneroth>
aw-, you're asking about the technical tooling, or about the business model?
<beneroth>
I see the use case, but I haven't had it yet
<beneroth>
"philosophically" I'm currently believing focusing more on vertical scaling than horizontal scaling would benefit many projects when mass-parallelism & especially write-availability aren't inherent to the use case
<beneroth>
s/when/unless
<beneroth>
I'm strongly in support of spreading over multiple vendors to minimize vendor lock in - but that also means not taking advantage of vendor-/stack-specific advantages
<beneroth>
so it's a price that has to be evaluated per case
<beneroth>
the more layers, the more "attack surface", the more space for issues and more ways for failure chains
<beneroth>
My impression is that in an attempt to minimize spaghetti code in a single application the "micro-service" approach gets overused, resulting in a spaghetti system architecture
<beneroth>
I haven't had yet the opportunity to work on the forefront of such large projects, so my experience and ability to judge it is small
rob_w has quit [Remote host closed the connection]
<aw->
ahaha i love that "spaghetti system architecture
<aw->
ok i see, so these types of tools just move the problem from one place to another
<aw->
beneroth: thanks for the response, your opinion is always valued
<beneroth>
thanks for your interest :-)
<beneroth>
aw-, important is to differentiate, I don't say there are no valid use cases for such systems - but I feel in general their often overused/used without requiring the benefits (while paying the cost)
<beneroth>
my impression is that most of this stuff is CV-driven programming
* beneroth
recently started working with Linux Containers (LXC/LXD)
<beneroth>
aw-, do you know Proxmox?
orivej has quit [Ping timeout: 246 seconds]
<tankf33der>
Regenaxer: found why doubled link tests failed