Works on the slint UI toolkit for rust, lives in Berlin/Germany.
#rust, #cpp, #slint, #qt, #tooling, #programming. #web, #encryption, #linux, #stateless_systems
| Github | https://github.com/hunger |
| Work URL | https://slint-ui.com/ |
@karolherbst Wow, what a shit show. So basically I need to join an instance big enough so that one idiot joining will not get the entire instance blocked?
This must be this decentralization thing that I hear so much about.
@justsoup #slint might fit the bill. Written in rust, backed by a UI toolkit company, DSL (compiled to native rust or C++ code) and support for writing your business logic in either #Rust, #C++, #JS or #python.
It scales from microcontrollers with a few KiB of RAM to Win/Mac/Linux and Android (with GUI acceleration of course).
Of course open source (GPL) with a commercial option and a royalty free license for anything not embedded.
@glebd It's sad how few conventions exist in the C++ world (not even file extensions!), and how little will to improve. E.g. file extensions for C++ modules are undefined, complicating the process of supporting modules for all build tools a bit more than necessary.
No shared conventions between projects and tools means build tools need to be excessively configurable and users need to configure the resulting mess.
Granted, that is only part of the problem with CMake;-)
The #Akademy2024 schedule is here!
Find out all about KDE's goals, what's new in the latest wave of desktop and mobile applications, and how KDE Eco is saving the environment, backends, frontends, and KDE for work, life and fun.
https://akademy.kde.org/2024/program/
Day Morning Afternoon Evening Fri 6th Welcome Event Sat 7th Talks Day 1 Sun 8th Talks Day 2 Social Event Mon 9th BoFs, Training, Workshops & Meetings Tue 10th BoFs, Training, Workshops & Meetings Wed 11th Daytrip Thu 12th BoFs, Workshops & Meetings To interact with Akademy attendees online you must first register (if you haven't already) and then join
🌍 Environmental stewardship is key at #RustLab2024. From reducing waste ♻️ to minimizing carbon footprint 👣, we're dedicated to making our conference eco-friendly.
Together, let's pave the way for a sustainable future!
👉https://rustlab.it/rustlab-for-the-planet
@sotolf That particular approach seems not to have worked well in python, that's all.
The supply chain problem is very real and trying to automatically analyze all the crates that get uploaded for bad behavior is not going to solve that. `cargo crev` does not seem to scale.
Some form of "blessed crate list" (with extra eyes on those) is needed, we "just" need to figure out a good way to do that without killing what makes the crates popular in the first place.
@sotolf so you want 3): Fork all the good libs, polish and integrate them with each other into one nice package that's blessed by "the language". That probably means a new crate in the rustlang org on github.
You end up setting a huge API into stone, and make it hard to continue developing the functionality: Languages with a big stdlib joke its where code goes to die.
At some point users start using alternatives in their programs and dependency hell is back.
@sotolf How would you build such an extended standard library?
* Make a crate with lots of other crates as dependencies. Simple to do, but keeps the entire mess visible.
* Bundle a bunch of crates in one repo. Hides the mess, but needs constant updates to keep in sync with the "real" crates and will not feel likemone unit.
* Fork all the dependencies into your repo and smoothen out the API. Lots of work as you fork everything.
I hope there is more, as neither of my ideas seem great.
Akademy
🦀 RustLab Conference