Works on the slint UI toolkit for rust, lives in Berlin/Germany.
#rust, #cpp, #slint, #qt, #tooling, #programming. #web, #encryption, #linux, #stateless_systems
@YaBoyMax @Pantherina this assumes that a C++ dev gets by without managing lifetimes. That is just not true: Mismanaging lifetimes is a bug in all languages.
The difference is the rust compiler detects those issues and errors out, so you have to fix the issue right away. In C++ the compiler will just accept the code, so you can deal with the issue later once bug reports come in.
@JTskulk @woelkchen Because I can easily limit which files are seen by applications in a flatpak.
I love being certain that my browsers can not access my ssh keys or actually anything outside the Downloads folder.
@Yora @woelkchen most people do not look beyond the UI. Unfortunately writing a pretty UI is the easy part of writing a browser. Maintaining some browser engine is much harder.
So make sure to use a browser with an engine backed by as big an open source project as possible and one where the browser engine has as few downstream patches as possible.
Wrapping the entire engine in a new set of APIs not available upstream involves way too many downstream patches for my taste.
@YaBoyMax @Pantherina I do think that KDE is doomed if it stays with C++ long term. The tooling is just horrible, you spend so much time debugging things. In my experience young people just do not put up with all that! It’s just us old people doing what we always did.