enether

10 ms·

91.
Neoq – a queue-agnostic background job library for Go(github.com)
1 points by enether 1y ago|2 comments
92.
by enether 1y ago
There is a noticeable coupling in background job queue libraries today where most seem to be coupled with Redis. A good library should abstract it away and, in theory at least, allow you to seamlessly switch the background infra when it no
93.
Ask HN: What's your go-to message queue in 2025?
66 points by enether 1y ago|97 comments
94.
by enether 1y ago
It was actually pretty cool to bike through the streets. It all felt so calm. Stores/restaurants closed, no traffic lights, little traffic. Parks were full of people. Literally chilling, walking dogs. Most weren't on their phones
95.
by enether 1y ago
ditto, definitely TIL
96.
Mutually Beneficial Group Lies(stanislavkozlovski.com)
3 points by enether 1y ago|0 comments
97.
by enether 1y ago
Why don't you make a convincing long-form write-up about this then? Start a discussion in any bitcoin forum like stacker news - I'm sure you'll get a lot of attention
98.
Cheap Kafka is cool. Schema-driven development with Kafka is cooler(buf.build)
1 points by enether 1y ago|0 comments
99.
by enether 1y ago
if anything, "free software" should change its wording (when referring to freedom/libre). there's no way you'll ever convince the masses who use software to not call it free or appeal to software that's adverti
100.
by enether 1y ago
Can you share three? Without concrete suggestions, this is just a disparaging narrative (that a lot of vendors use)
101.
by enether 1y ago
In what way is it materially easier to maintain and less finicky? I read a lot about this but I haven’t seen a concise bullet point list of why, which leads me to naturally distrust such claims. Ditto for the resources - Kafka is usually bo
102.
by enether 1y ago
There’s inherently a lot of path-dependent network effects in open source software. Just because something is 10-30% better in certain cases almost never warrants its adoption, if on the other side you get much less human expertise, documen
103.
by enether 1y ago
Somewhat. The buying further validated the market, but at the time of purchase (Sep 2024) there already were 5 alternative proprietary solutions utilizing the same direct-to-S3 design shipped or announced (Confluent Freight, Bufstream, Auto
104.
by enether 1y ago
there was one post that detailed how those OpenAI models hallucinate and double down on thier mistakes by "lying" - it speculated on a bunch of interesting reasons why this may be the case recommended read - https://tra
105.
KIP-1150: Diskless Kafka Topics(cwiki.apache.org)
32 points by enether 1y ago|3 comments
106.
by enether 2y ago
Its really cool. How did you make it?
107.
Why Open Source Software Should Invest in Evangelism (2018)(stanislavkozlovski.medium.com)
1 points by enether 2y ago|0 comments
108.
by enether 2y ago
Can anyone with older Mac Studios/Minis comment - do you also notice a "throttling" of the hardware? I'm not sure if this is me not maintaining it properly (e.g fans having dust block them) - but I've always got thi
109.
by enether 2y ago
This is an amazing piece. It explains a lot behind the relative stagnation of technological innovation. Peter Thiel has been talking about this for a long time too - https://www.youtube.com/watch?v=jX07zPupNdc I love the id
110.
by enether 2y ago
Defauls do matter, in principle. But I think this particular risk is overblown, see my other reply for my thoughts
111.
by enether 2y ago
I agree that data can be valuable and even one record loss can be catastrophic. I agree that there needs to be better documentation. I just don't agree that losing 3 replicas each living in a different DC at once is a realistic concern
112.
by enether 2y ago
and it then becomes a self-perpetuating cycle because the network effect and usage of one product makes it become exponentially more robust & mature than the other. I've heard that Pulsar is buggy basically, and I wouldn't be
113.
by enether 2y ago
yep, I was mostly clarifying the timeline
114.
by enether 2y ago
It's just my polite way of saying it's safe enough for most use cases and that you're wrong. The fsync thing is complete FUD by RedPanda. They later introduce write caching[1] and call it an innovation[2]. I notice you also w
115.
by enether 2y ago
Even if you used a 100% random strategy - what OP described can still happen. Matching the number of consumers can still produce an uneven result too, and OP clarifies that even if the worst case he laid out doesn't happen - in practic
116.
by enether 2y ago
It's pretty safe. Kafka replicates to 3 nodes (no fsync) before the request is completed. What are the odds of all 3 nodes (running in different data centers) failing at the same time?
117.
by enether 2y ago
thankfully early access for KIP-932 is coming in 1-3 weeks as the 4.0.0 release gets published
118.
Snowflake reportedly eyeing a Redpanda acquisition(investors.com)
2 points by enether 2y ago|0 comments
119.
by enether 2y ago
What if it stops becoming cheaper?
120.
by enether 2y ago
Care to share more? Was there just a lot of unnecessary fluff being dumped in there?

More ›