unasync
Swoole
Our great sponsors
unasync | Swoole | |
---|---|---|
5 | 34 | |
82 | 18,219 | |
- | 0.4% | |
0.0 | 8.6 | |
12 months ago | 4 days ago | |
Python | C++ | |
GNU General Public License v3.0 or later | 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.
unasync
-
The bane of my existence: Supporting both async and sync code in Rust
Nice! This is similar to the solution here: https://github.com/python-trio/unasync
-
Need advice to design sync version of an async library
Lastly, I found another project name unasync that is pretty interesting and might works for me. Basically, you write the async version, you run unasync, it generate the sync version from the AST. This project is used by the official elastic search python client.
-
PHP 8.1.0 Release Announcement
Fibers "allow blocking and non-blocking implementations to share the same API"
That's an interesting contrast to Python where the need to use "value = await fn()" v.s. "value = fn()" depending on whether or not that function is awaitable causes all kinds of API design complexity, all the way up to the existence of tools like https://github.com/python-trio/unasync which can code-generate the non-async version of a library from the async version.
-
Async Python is not faster
Async Python has proven faster in my uses for IO and non-CPU-related stuff. But I think Python, either as a community or within the language, needs to solve the anti-pattern of maintaining separate sync and async versions of a library. I'm thinking specifically of aioredis and redis-py, both of which I've worked on.
Some people are looking at ways to solve this. I know urllib3, elasticsearch-py, and a few others use unasync (https://github.com/python-trio/unasync) to transform async code into sync code, leaving one codebase supporting both uses in different namespaces. This leaves you with some conditional logic (is_async_mode() -- https://github.com/python-trio/hip/blob/master/src/ahip/util...). I'm seriously considering this approach.
- unasync – transform your asynchronous code into synchronous code
Swoole
-
Performance benchmark of PHP runtimes
Swoole
-
Go with PHP (why it's still a good idea to use PHP in 2023)
It's a management UI where concerns were raised that it downloads from third party server. However this issue was handled very fast and code was removed: https://github.com/swoole/swoole-src/issues/4434
-
PHP Swoole or OpenSwoole?
The contribution log of the original swoole seems to be active: https://github.com/swoole/swoole-src/graphs/contributors
-
5 PHP Frameworks You've (Probably) Never Heard of
FOMO is created by Iranian developer amirfaramarzi. This framework sits on top of the asynchronous event driven framework swoole that creates insane levels of performance out of apps (we're talking Go/Rust level of performance)! Check out the performance on the Web Frameworks Benchmark.
-
Why is Apache clinging to OpenOffice's corpse?
> I tend to install FOSS because imo they are more "future-proof", but some of them are developed by companies (e.g., Fedora Linux) and that makes me wonder if they're truly future-proof.
The story of CentOS should be telling that, no, many pieces of software that are backed by a company will not be future-proof and will probably experience certain changes as a consequence of that, be it being transformed to better fit corporate goals (CentOS Stream), or being retired eventually so the company may focus on something else (Atom), or will just be left to slowly rot over time as happens with most code (OpenOffice).
Then again, it's not like open source projects are that future proof or safe from "drama" either - for example, the Lubuntu project has 2 homepages for no reason: the official one at https://lubuntu.me/ and some other one that serves old versions and is not trusted by my ad blocking solution https://lubuntu.net/
There are also cases, when open source projects experience fragmentation like happened with Gogs https://gogs.io/ and Gitea https://gitea.io/en-us/ and sometimes there are cases where particular individuals simply cannot work together and as a consequence pretty much the same happens, as was the case with Swoole and Open Swoole: https://github.com/swoole/swoole-src/issues/4434
Treat most pieces of software that you use as if they might not be there in a year.
-
A Self-Hosted and Open-Source Alternative to Google’s Firebase Releases Version 0.14
It's known by devs, it's simple, it's getting updates... I like PHP. Sure it has downsides but what doesn't. Oh, and with Swoole, even performance is bumped.
-
Take your Serverless Functions to new speeds with Appwrite 0.13
To allow for synchronous execution and prioritize speed, we decided to depart from the task-based system that most of our workers use and instead create a new component to Appwrite called the executor. The executor would handle all orchestration and execution responsibilities and remove the Docker socket from the functions worker. The executor is an HTTP Server built with Swoole and Utopia using various Appwrite libraries to interact with the database.
-
Using Bref's LambaRuntime to Asynchronously Run Swoole Coroutines as Functions on AWS
Swoole will be shipping something really-really cool that is it's own CLI. You can checkout the development at https://github.com/swoole/swoole-cli and you can start playing with it using the pre-compiled binary distributed under Swoole's releases at https://github.com/swoole/swoole-src/releases/tag/v4.8.7.
- Swoole 4.8.7 has been released
-
How is node compared to other backend tech?
It's been around for more then 8 years. Its a very established project with more the 17k stars https://github.com/swoole/swoole-src
What are some alternatives?
jigsaw - Simple static sites with Laravel’s Blade.
RoadRunner - 🤯 High-performance PHP application server, process manager written in Go and powered with plugins
Amp - A non-blocking concurrency framework for PHP applications. 🐘
Phalcon - High performance, full-stack PHP framework delivered as a C extension.
phpmiko - A netmiko implementation in php
Symfony - The Symfony PHP framework
blacksmith - REST API Client
ReactPHP Promises Testing - PHPUnit assertions for testing ReactPHP promises
React - Event-driven, non-blocking I/O with PHP.
CodeIgniter - Open Source PHP Framework (originally from EllisLab)
Slim Framework - Slim is a PHP micro framework that helps you quickly write simple yet powerful web applications and APIs.