At least one of the advantages in targeting React is being able to leverage the vast existing library of React components to quickly expose new and advanced functionality to the Reflex app.
Thanks for the feedback. I work on Reflex and in a recent release, the team added a template and CLI for creating third-party components and publishing them to PyPI.
Since then, I've built a few authentication libraries that might be of interest:
The problem with having auth built in is that it's been hard to find a solution that actually works for a majority of use cases. That said, as these auth libraries get more popular and refined, they might be moved into the reflex-dev organization as officially maintained components, or even integrated with the core framework.
I've recently deployed this trick on my company's confluence instance (with an HTML macro) to create a "poor man's" link shortener that allows me to change the link target after the fact.
Also recently deployed it as a very simple server side denounce: when the client first accesses page X a long running operation is dispatched. Subsequent requests for the same resource before it's done processing return a plain HTML response that says "Still thinking about it" and meta refresh after 1 second.
I haven't been privy to those kinds of conversations. Mostly we are replacing Ubuntu LTS and older CentOS with OpenSUSE Leap for servers. Some developers are deploying Tumbleweed as a rolling release.
I'm trying to give it chance, change being hard and all.
The other comments here from long time users are giving me some hope that we may find tangible benefits, especially w.r.t btrfs and snapshots.
At the company I work at currently, we're in the process of replacing all Linux-based machines with OpenSUSE... not for any technical merit or reason that I've heard other than, "we should all use the same thing for everything".
So another 20k+ SUSE installations coming from that alone this year.
Market share by mandate; some sales guy at SUSE probably got a big bonus.
In the last month, I’ve been experimentally replacing my use of Trello, stickies, and todo lists with a phpBB instance.
So far I’m the only user, but it’s a surprisingly nice system for keeping track of notes and regular status updates on my projects. And when I need to collaborate with someone, the permission system is quite nice as well.
The fact that it’s free, mature, and relatively easy to install and maintain are what led me to give it a try.
I have plans to eventually write a kanban view and scheduled post plug-ins to make it a bit better project tracker.
Previously I used Nextcloud News and enjoyed it, but recent versions require 64-bit PHP [1], which I didn’t have on the Raspberry Pi. Never did figure out why this requirement was imposed just for the News app.
1. Synced feeds, read/unread status, and consistent UI across all devices
2. Hosted feed reader for friends and family.
The author mentions the friction they imagine their friends or family would have using RSS feeds, so hosting the reader for them can reduce that friction and bootstrap cost (everyone already has a browser). Then they could always export their feeds and move to a different solution later.
As a recent returnee to the world of RSS feeds, I’ve been enjoying the miniflux client [1] self hosted with docker-compose. Fast, cross-platform, not fancy.
I’m currently using cibuildwheel and github actions to create Linux and macOS wheels [1], but I need to install some host packages to make it work, particularly automake and friends.
The main issue I have with GHA is it doesn’t support ARM (aarch64 or armv7l) executors, so building these needs QEMU, which is slow.
I also maintain a different package [2] that doesn’t currently distribute its Kerberos module via PYPI, because I haven’t had time to make the same kind of GHA pipeline and test it.
Wondering how these kinds of non-Python platform dependencies (automake, libkrb5, etc) could be handled by this system?
When would it be available to the public? It looks cool, I want to play with it.
I recently developed a tox plug-in, tox-pin-deps [1], that integrates the pip-compile workflow with dependencies specified in tox.ini (per environment). This was in response to both poetry and Pipenv being non-standard and consistent stumbling blocks for ramping up new devs on the team.
Despite the shiny, I seem to always find my way back to standard tools and text files.