I have never once been asked to provide a transcript. Literally never. I also don't know anybody who has been asked to verify qualifications.
I'm sure it happens but it's not the standard.
I have never once been asked to provide a transcript. Literally never. I also don't know anybody who has been asked to verify qualifications.
I'm sure it happens but it's not the standard.
Yeah, it's funny because I've been doing the same thing with my wife on some personal projects like family wiki and event calendar and things where we wanted a web application that could be used on both desktop and mobile.
Here's what I found so far, Avoiding JavaScript entirely by using a templating language and a HTTP server like Axum Produces fairly sub-par results if you are hoping for interactivity ( Frequent page reloads mean that you can't have big sodebars etc.)
Qt/qml are OK, but no mobile.
Leptos is what I was looking at, but in the end TypeScript with solid-js was simpler, more performant and more features (although I absolutely hope to revisit leptos down the line).
What you get with solid is signals/slots for state, server side functions to avoid the need for an api, routing for template management, easy tailwind integration and of course any js you may want (eg full calendar io).
I wouldn't recommend egui if your focus was web.
Oh, and finally, the other issue with Leptos over Solid is that it's a bit more work to get into Electron from what I understand. Tauri Does not support Linux, so that's not really an option for a cross-platform.
Well you will write 0 js in leptos, however js is used to initialize the WASM.
What is your goal and the reason against JS and maybe I could provide more recommendations.
If it's a personal choice against Js, leptos will be the best compromise. One could use Axum with minijinja but if you're not careful about routes etc. performance will be shit.
Id just use leptos. There will be a little bit of js to load the WASM but that would be it.
If it's a performance concern, i think solid-js had better performance than both egui and leptos anyway plus you get some niceties like codemirror (vim bindings), marked.js etc.
Egui is really nice dx wise but you will be restricted to those widgets, immediate mode may not scale as well as signals/{slots, effects}.
If it's a general dislike of JavaScript, you may want to look at QML.
I personally found QML to have really poor documentation around a lot of the widgets. Leptos is good, but I found SolidJS to have more of what I needed and the performance was good enough that I went without for my own personal stuff. But I also had different needs. I really needed something that could do charts, data tables, and your general GUI stuff as well.
Steam deck is quite good with touch I find.
Must be nice in that small section of western Europe. For the rest of us things are not so blissful.
Tail scale already has a bunch of limitations for unpaid users but it's only an extra step to set up wireguard in a container.
Honestly, I've had little trouble. The Gentoo Wiki and Void Handbook have a lot of overlap with OpenRC and musl, respectively.
While the documentation could be improved, the overall experience has been quite good and very stable.
I'm not trying to be unhelpful. My advice would be to steer into the terminal. Bite the bullet. I use arch and alpine for my servers but Fedora would be fine (but SELinux can be a pain with bund mounts)
Probably just go with Fedora with btrfs for snaps. It has lots of support and is a common choice for servers
Well, it could change the meaning of the prompt unintentionally.
The real challenge is that this technology is not universally accessible so people aren't learning effective use-case and prompt strategies.
Whilst 1B models are easy enough to run and have plenty of use, nobody can teach this, its a nightmare on Windows and most universities have collapsed under their own weight. Half my comp sci profs didn't know python 10 years ago and I know for a fact this hasn't improved (hiring developers -- not fun).
Yeah for all the things he says that many disagree with, this one is pretty good.
Yeah this wasn't ratio or even obiter, perhaps convention. Without looking deeper this was along the lines of an impact statement. Whilst it raises points for discussion its a far cry from precedent for the admission of evidence.