3,664 karma · joined March 9, 2009
I previously built virtual power plants at Tibber, databases at Neo4j and fleet management Equipmentshare.
jake@davis-hansson.com https://tech.davis-hansson.com http://github.com/jakewins
In other words: My claim isn’t that they were better at ingestion but at onboarding and at creating switching costs.
Since that was how their leadership acted last time I used their code, I expect the same leadership to act the same way again with this other piece of code they own.
In my experience DuckDB is a batch tool, vs this thing which is a continuous stream tool
So if you have a stream of sensor data from a bunch of IoT devices, you might use Arroyo to run “live” queries over the flowing data, and you might use DuckDB to do analytical queries over archive data
Although they are both hammers to whack nails with I guess, so a lot of use cases likely work well to solve with both systems
In that context, OTEL is an existential threat, because it makes them a commodity. Then it becomes relatively clear why they wouldn’t put OTEL support in the Vector roadmap.
Given my experience with Datadogs pricing lock-in-and-switch, yeah 100% I’d rather run agents that allow me to pick the collection backend than another tool from Datadog.
Or are you thinking more on the UI/analysis/collection side?
However you will still have shared resource problems - some rogue query destroys IOPS in one tenant now ends up bringing down all tenants etc. There are in theory databases that solve this as well, but my experience has been that at that point what you buy into is a bad version of resource sharing - ie what an operating system does - and you’re better off using OS mechanisms
In other words: yes, but you still have noisy neighbours, and may be better off running lots of small fully separated DBMSes than a big logically separated one
Does C# have the same issue Python does with accidentally calling blocking code? In async Python - which I mostly quite like actually - it’s terrifying to bring in a library because if you’re unlucky it does some blocking network call deep inside that stalls your whole app..
Are there any talks or blog posts on how y’all wired this up, lessons learned etc?
David mentions as an aside “this place has other mechanisms for dealing with [spam]”. A lot of the complexities around “karma” - far from all of course - relate to spam. But lobsters has a separate giant hammer for that nail, so the karma feature complexities for lobsters becomes quite different. Not necessarily harder or easier, but certainly not the same compared to a site like, say, SO, where karma is central to who gets to take what actions.
But it was driven by both sides being made clear from the beginning: nobody is losing any jobs here, the goal is to 10x the number of accounts we could do per back office person; their new jobs will be overseeing the software and dealing with edge cases.
I’m not sure this would’ve been possible to do in such a way if the company wasn’t rapidly growing though.
Makes me wonder: what are things that are easier like this in orgs that aren’t in growth phases?
Can you help guide me where I'm misunderstanding the type system aspect of const generics that's missing in Python? What I meant was that in Python I can say something like this:
import typing as t
class FooEater[NUM_FOOS: int]:
def eat_foo(self, num_foos: NUM_FOOS):
print("nomnom")
one_foo = FooEater[t.Literal[1]]()
one_foo.eat_foo(2) # type error, NUM_FOOs for one_foo only allows literal '1'
And a PEP695-compatible typechecker will error at build time, saying I can't call `eat_foo` with `2`, because it's constrained to only allow the value `1`.I admit to not being a type system specialist, but at least as I understand Rust's "const generics" the type system feature is: "Things can be generic over constant values". Isn't that the same as what Python supports?
The question I responded to said: "Better static analysis, for one."
I asked: "What is something you can express in the C# type system that MyPy cannot statically check?"
Can you provide some examples where C#'s type system can express something that modern well-typed Python cannot type-check?
Conversely, I find myself constrained by C#'s typesystem not having features now widely popular from Rust and Typescript and available in modern Python: const generics / literals, protocols/structural interfaces and matching over algebraic datatypes, to name a few examples.
On the actual criticism you’re raising: In what concrete way would moving to micro services help with reducing data integrity bugs? In my experience I’d expect the exact opposite - micro services systems generally being harder to test and generally having more possible interleavings and partial failure paths.
I would say this: I agree with you that massive faceless monopolies with no accountability are terrible, and often a direct consequence of economies of scale.
It is also, simultaneously, true that the labour saving effects - human hours spent per calorie of food or pair of socks - is a number of orders of magnitude such that modern society (ie the not starving/not freezing part of it) could not exist without it.
These two things are simultaneously true, which is what makes the problem hard; we want one effect of economies of scale and not the other.
I think my argument was mostly like - don’t throw out the baby with the bath water; economies of scale are a real thing that brings us real benefits, and that should go in the scale too.
The economies of scale that put food on your table and mine and clothe our kids - for all the horrors - will not be replaced by artisans doing small batch t-shirts from yard-grown cotton using hand made tools.
You had me until here.
Economies of scale in commodities is the thing that makes it so we don’t have to do sustenance farming and everyone gets to have sewn clothes on :)
There’s truth in both sides there - we want nail production to not be done by hand, but also real humans with power to change things to answer the phone when we call support.
What would blockchain possibly be helpful with here?
Annoying though, I've really enjoyed not having to dig through pockets to open the car :(
At least in the two Hyundai's I've owned with this type of system - an Ioniq hybrid and a Kona EV - it drives just fine once started even if you chuck the key out the window.