Issue trackers and PRs are definitely getting harder and harder to trust. That said, AI is helping ALOT in OSS, but we definitely need guardrails around provenance, automated issue actions, and sudden changes in a contributor’s behavior.

Also, building rapid temp shells plus nearby gas turbines paints a very different picture than the one conveyed by the "clean-energy" PR around hyperscale data centers.

It will be interesting to see if the Private Cloud Compute + on-device routing can make third-party model capabilities feel like a first-party system without leaking user context to the model provider.

If Apple handles the Google-Apple boundary right, this will be an elegant move on their part, otherwise it will feel like Apple Intelligence with a just a privacy-polished frontend for Gemini.

Comments URL: https://news.ycombinator.com/item?id=48298164

Points: 2

# Comments: 0

We should draw a distinction between "AI is valuable" and "AI justifies its current investment levels." There's real productivity value in AI, especially for things like search, boilerplate, tests, refactoring, etc...BUT that doesn't mean every enterprise should let token spend grow without strict telemetry, cost-attribution and outcome-based measurements.

The teams that win here will not be the ones using the Most AI, but the ones that treat it like any other expensive production dependency, which means measuring unit economics, cap runway usage, properly align models with tasks(not just Opus everything), and scale workflows with ROI in mind.

Comments URL: https://news.ycombinator.com/item?id=46891529

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=45057293

Points: 2

# Comments: 0

We're building a high-performance, streaming-native protocol-agnostic proxy. After completing an OpenMessaging Benchmark on the proxy deployed in front of Apache Kafka, we've shown that it has near-zero impact on p99 latency, and actually absorbs and smooths out latency variation in a Kafka deployment, ensuring low and predictable latency at the 99th percentile, even under long-running, high-throughput workloads.

A link to the benchmark repo is included in the post to validate/confirm results.

Comments URL: https://news.ycombinator.com/item?id=44720467

Points: 1

# Comments: 1

We're excited to share that Zilla officially supports another protocol — MQTT! With this, MQTT clients can publish and subscribe to Kafka directly without running a dedicated MQTT broker and Kafka Connect. In fact, Zilla turns Kafka into a full-fledged MQTT broker, meaning it doesn’t just mediate between the MQTT and Kafka wire protocols but maintains MQTT client state across Kafka topics!

The latest Zilla feature highlights include: - MQTT v5 and v3.1.1 Support: Zilla supports both major versions of the MQTT protocol, ensuring it works with legacy and modern IoT clients. - MQTT-Kafka Proxying: Zilla maintains MQTT client state across Kafka topics, providing all of the features and guarantees of a dedicated MQTT broker, such as Keep-Alive, Last Will and Testament, and all three Quality of Service (QOS) agreements. MQTT over WebSocket is also supported, so you can use Zilla to deliver MQTT messages from Kafka down to a browser. - Manage Millions of Clients: Zilla is stateless, scales out linearly and handles MQTT to Kafka connection offloading.

You can quickly try out MQTT-Kafka proxying with Zilla with the following https://docs.aklivity.io/zilla/latest/how-tos/mqtt/mqtt.kafk... (the guide includes a docker compose file for quick and easy setup). We also have a fun Taxi Hailing Demo that simulates an IoT mobility use case powered by Zilla and Kafka for a more end-to-end setup: https://github.com/aklivity/zilla-demos/tree/main/taxi

Looking forward to all feedback and questions!

Comments URL: https://news.ycombinator.com/item?id=38684879

Points: 24

# Comments: 3

Zilla has no external dependencies and does not rely on the Kafka Consumer/Producer API or Kafka Connect. Instead, it natively supports the Kafka wire protocol and uses advanced protocol mediation to establish stateless API entry points into Kafka. Zilla also addresses security enforcement, observability and connection offloading on the data path.

You can try Zilla out by running the Quickstart linked in the ReadME. The Quickstart uses a Postman Workspace with pre-defined API endpoints and a Docker Compose stack running pre-configured Zilla and Kafka instances to make things as easy as possible.

It would be great to get your feedback!

Comments URL: https://news.ycombinator.com/item?id=36774490

Points: 7

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=36071707

Points: 2

# Comments: 1

Zilla is super easy to get started with because it's declaratively configured via JSON; however, we’ve made it even easier via a GUI tool called Zilla Studio. Check out the announcement and give the Studio a try. Thoughts/comments/feedback/questions are welcome!

Comments URL: https://news.ycombinator.com/item?id=33574923

Points: 3

# Comments: 1