running your own email is the hardest part of the list, imho. even deployments technicalities aside, your server needs ''reputation" to not get into spam. i ended up just paying for protonmail.
about frontend dev: you can now do a lot without js or with minimal vanilla js, without npm hell. get a good css framework, get a template engine for your backend of choice, and that should serve you well.
In part this is going to be super frustrating because to do this I need to move a lot of things I do in naive apps to web-apps (which I write myself) and I kinda hate web-development.. maybe I should learn to use #wasm?
running your own email is the hardest part of the list, imho. even deployments technicalities aside, your server needs ''reputation" to not get into spam. i ended up just paying for protonmail.
about frontend dev: you can now do a lot without js or with minimal vanilla js, without npm hell. get a good css framework, get a template engine for your backend of choice, and that should serve you well.
@orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam
The idea is an email server which will have an list of known trusted servers of friends and family to send and receive email with, & will allow receive email from anywhere else but flag these as suspicious by default. I don't think I will send much email to any where else more than once a week.
I can use #RubyOnRails for web apps as needed ¯\_(ツ)_/¯
if you need a lot of interactivity, wasm is a fun option. however, we don't have big web UI frameworks like React. for low-level access, Rust has wasm-bindgen and Go has gweb. for high-level, Rust has Macroquad (and more) and Go has Fyne. however, they are not web-native but cross-platform, so you might face limitations quite fast.
wasm shines for porting non-web-native apps and for games, imho. for the rest we're still far behind from js in terms of ecosystem.
