My first “real” job (I used to work at McD’s and Walmart, barely three months each) was 120k a year as a software engineer. I left that job for 200k within six months and here I happily stay

Agui, but it’s not yet ready for legitimate use. Well, sort of. The engine should be mostly there, I’m just working on integrations with renderers and windowing (winit), now. It doesn’t have focusing or accessibility support yet, but that’s my next task

I’m actively working on a UI framework, so hopefully it helps, haha

Pure widgets are just ones that don’t contain state. You pick which one you need based on which one you need, so in your case you need state because you must store what’s within the number input box.

I’m not wholly familiar with iced, but I’d venture to guess the example you looked at didn’t need to store state so it was able to use a non-mutable view, whereas you need to store it so that example doesn’t exactly work for you. However it could just be a bit out of date, and I’m sure they’d appreciate a PR

Working on a mobile client and this is a biggie. I’d rather not deal with user credentials ever. Luckily I’m also a rust dev who has implemented OAuth quite a few times, I may take a look