I don't know what you're looking for, and what your "not super simple" is, but baseline browser tech provides various controls, layout mechanisms, styling, interactivity, etc.
Do you have a concrete idea of what and where specifically you hope for gains by using frameworks? Do you plan to hold a lot of state on the client that needs state separated from the DOM and its mechanisms? Do you want a standard library of styled components instead of using the native ones or styling them yourself? Do you want more robust JavaScript? Those are all very different concerns and requirements.
I like the low complexity, low barrier, low requirements of baseline web tech. The native html form controls may arguably look "ugly", but those can be styled, individually or through a style-only CSS lib.
How viable is shifting from app to the web platform? Installable PWAs or PWA without installs.
Seems like it could be an alternative for most(?) things.
The most future proof web tech is not using frameworks and libraries at all.
Render native HTML controls.
I also assume it's lower barrier than any of the libs and frameworks you could use, which is always a subset of web tech with the addition of their own concepts.
Tailwind is an example of those frameworks fighting against/crossing the native web technologies referenced further up with the links to webdev posts.
The idea of shifting CSS declaration into the DOM element class attribute seems flawed to me. You lose what CSS provides natively.
If you don't care too much and don't have experience yet, why not go for native browser and HTML/CSS/JavaScript?
Even if you eventually migrate to other web UI libs and frameworks, the foundations knowledge will be useful.
What kind of tech and project did or do you use it on?
These terms included affirming the statement that we 'do not, and will not during the term of this financial assistance award, operate any programs that advance or promote DEI [diversity, equity, and inclusion], or discriminatory equity ideology in violation of Federal anti-discrimination laws,'
Insane. I can't even fathom adding such a condition. And to a well established org with a positive track record.
Toxic offer. Wouldn't even be able to say that inclusivity is a good thing.
Starship is a customizable prompt with support for multiple shells, including Nushell.
Starship v1.23.0 includes:
completions: Offer Nushell completions (#6366) (df454d5)
The completions can be generated in the env.nu into an autoload dir:
starship completions nushell | save --force $'($nu.user-autoload-dirs | last)/starship-completions.nu'
I have a setup that generates env files only once per day, resulting in faster shell startup otherwise.
call-if-old $'($nu.user-autoload-dirs | last)/starship-completions.nu' {|filepath| starship completions nushell | save -f $filepath }
call-if-old is a command I defined.
Completions Demonstration:
I use GitLab diffs in single-file-view mode, TortoiseGit Merge when it exceeds what GitLab can reasonably display (including block indent changes I can ignore in TortoiseGit Merge or moves I can better track), and WinMerge (previously I used KDiff) for manual copy-paste text diffing (like copying blocks from the code change diff to compare similar, categorically similar code, or code moves, etc)