fastkafka VS contour

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

After a short discussion, we concluded we were just too spoiled to use low-level libraries that were nothing more than just tiny wrappers around C++ libs and that we could just build our own. So, we shamelessly made one by reusing beloved paradigms from FastAPI and we shamelessly named it FastKafka. The point was to set the expectations right - you get pretty much what you would expect: function decorators for consumers and producers with type hints specifying Pydantic classes for JSON encoding/decoding, automatic message routing to Kafka brokers and documentation generation.

FastStream simplifies the process of writing producers and consumers for message queues, handling all the parsing, networking and documentation generation automatically. It is a new package based on the ideas and experiences gained from FastKafka and Propan. By joining our forces, we picked up the best from both packages and created a unified way to write services capable of processing streamed data regardless of the underlying protocol. We'll continue to maintain both packages, but new development will be in this project.

FastStream (https://github.com/airtai/faststream) is a new Python framework, born from Propan and FastKafka teams' collaboration (both are deprecated now). It extremely simplifies event-driven system development, handling all the parsing, networking, and documentation generation automatically. Now FastStream supports RabbitMQ and Kafka, but supported brokers are constantly growing (wait for NATS and Redis a bit). FastStream itself is a really great tool to build event-driven services. Also, it has a native FastAPI integration. Just create a StreamRouter (very close to APIRouter) and register event handlers the same with the regular HTTP-endpoints way:

Inspired by FastAPI, FastKafka uses the same paradigms for routing, validation, and documentation, making it easy to learn and integrate into your existing streaming data projects. Please check out the latest version adds supporting the newly released Pydantic v2.0, making it significantly faster. https://github.com/airtai/fastkafka

Another problem is that the cursor moves while the screen is buffer is being rendered. The location is only really known once the cursor settles in the same place for some time, which is unacceptable in terms of latency.

The synchronized output extension could be used to do this, though. https://github.com/contour-terminal/contour/blob/master/docs...

https://github.com/contour-terminal/contour/issues/382

This apparently does not support the Kitty graphics protocol, just Sixel, which makes it look fairly unattractive to me, personally.

contour - https://github.com/contour-terminal/contour. https://github.com/contour-terminal/contour/issues/100 and other modern unicode focused attempts to update the terminal world

contour : a terminal application

https://github.com/contour-terminal/contour Contour has a implementation for this. See this release: https://github.com/contour-terminal/contour/releases/tag/v0.3.6.240

Now that I'm well rested I decided to compile some similar terminal emulators with clang++ and rustc to see how big of a gap we're looking at. For the C++ terminal emulator I compiled contour with ~80k lines of C++ and over 200k lines when accounting for dependencies (not including dynamically linked dependencies), and then I'm using alacritty with ~35k lines of Rust and over 2 million (!) lines for the whole dependency tree when vendoring all dependencies. Because Rust tries to make most software cross platform with conditional compilation and many of these aren't Linux specific libraries I'm gonna assume it's compiling half or two thirds of the lines of dependencies for this experiment with the C++ compiling probably 3/4ths of the dependency tree considering I'm not on windows.

I have my eyes on this though.