spec
livebook
Our great sponsors
spec | livebook | |
---|---|---|
42 | 79 | |
3,843 | 4,390 | |
2.9% | 3.1% | |
7.9 | 9.8 | |
1 day ago | 2 days ago | |
JavaScript | Elixir | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spec
-
10 realtime data sources you won't believe are free!
AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.
- Comunicar microservicios con: ¿Kafka, RabbitMQ u otro? ¿Por qué?
-
FastStream: Python's framework for Efficient Message Queue Handling
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.
-
Introducing FastStream: the easiest way to write microservices for Apache Kafka and RabbitMQ in Python
Automatic Docs: Stay ahead with automatic AsyncAPI documentation
-
FastStream: the easiest way to add Kafka and RabbitMQ support to FastAPI services
FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.
-
An AsyncAPI Example: Building Your First Event-driven API
However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.
-
Is this a viable approach to a chat microservice?
You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.
- OpenAPI v4 Proposal
-
Propan 0.1.2 - new way to interact Kafka from Python
Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...
-
Make API product lifecycle management easy
Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.
livebook
- Arraymancer – Deep Learning Nim Library
-
Setup Nx lib and EXLA to run NX/AXON with CUDA
LiveBook site
-
Interactive Code Cells
I prefer functional programming with Livebook[1] for this type of thing. Once you run a cell, it can be published right into a web component as well.
[1] - https://livebook.dev
-
What software should I use as an alternative to Microsoft OneNote?
If you're a coder, Livebook might be worth a look too. I certainly have my eyes on it.
-
Advent of Code Day 5
Would highly recommend looking at Jose's use of livebook to answer these. It makes testing easier. It's old but still relevant. Video link inside
- Advent of Code 2023 is nigh
-
Racket branch of Chez Scheme merging with mainline Chez Scheme
That's hard to say. Racket is a rather complete language, as is F# and Elixir. And F# and Racket are extremely capable multi-paradigm languages, supporting basically any paradigm. Elixir is a bit more restricted in terms of its paradigms, but that's a feature oftentimes, and it also makes up for it with its process framework and deep VM support from the BEAM.
I would say that the key difference is that F# and Elixir are backed by industry whereas Racket is primarily backed via academia. Thus, the incentives and goals are more aligned for F# and Elixir to be used in industrial settings.
Also, both F# and Elixir gain a lot from their host VMs in the CLR and BEAM. Overall, F# is the cleanest language of the three, as it is easy to write concise imperative, functional, or OOP code and has easy asynchronous facilities. Elixir supports macros, and although Racket's macro system is far more advanced, I don't think it really provides any measurable utility over Elixir's. I would also say that F# and Elixir's documentation is better than Racket's. Racket has a lot of documentation, but it can be a little terse at times. And Elixir definitely has the most active, vibrant, and complete ecosystem of all three languages, as well as job market.
The last thing is that F# and Elixir have extremely good notebook implementations in Polyglot Notebooks (https://marketplace.visualstudio.com/items?itemName=ms-dotne...) and Livebook (https://livebook.dev/), respectively. I would say both of these exceed the standard Python Jupyter notebook, and Racket doesn't have anything like Polyglot Notebooks or Livebook. (As an aside, it's possible for someone to implement a Racket kernel for Polyglot Notebooks, so maybe that's a good side project for me.)
So for me, over time, it has slowly whittled down to F# and Elixir being my two languages that I reach for to handle effectively any project. Racket just doesn't pull me in that direction, and I would say that Racket is a bit too locked to DrRacket. I tried doing some GUI stuff in Racket, and despite it having an already built framework, I have actually found it easier to write my own due to bugs found and the poor performance of Racket Draw.
-
Runme – Interactive Runbooks Built with Markdown
This looks very similar to LiveBook¹. It is purely Elixir/BEAM based, but is quite polished and seems like a perfect workflow tool that is also able to expose these workflows (simply called livebooks) as web apps that some functional, non-technical person can execute on his/her own.
- Livebook: Automate code and data workflows with interactive notebooks
- Elixir Livebook is a secret weapon for documentation
What are some alternatives?
springdoc-openapi - Library for OpenAPI 3 with spring-boot
kino - Client-driven interactive widgets for Livebook
WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
awesome-advent-of-code - A collection of awesome resources related to the yearly Advent of Code challenge.
asyncapi-react - React component for rendering documentation from your specification in real-time in the browser. It also provides a WebComponent and bundle for Angular and Vue
interactive - .NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
mqtt-venstar-bridge - Simple MQTT bridge to the venstar HTTP API
Genie.jl - 🧞The highly productive Julia web framework
eventbridge-atlas - Open-source tool to document, discover, and share your Amazon EventBridge schemas.
Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications
Flask-SocketIO - Socket.IO integration for Flask applications.
axon - Nx-powered Neural Networks