Honestly you should shop around on LinkedIn
Honestly you should shop around on LinkedIn
In the winter I’d remote start my car from the top floor and even I got to the bottom my car would be heated; their remote start uses server time.
Now if they charged me to use the remote start from my keys, that’d be a different story.
trait HttpService {
async fn fetch(&self, url: Url) -> HtmlBody;
// ^^^^^^^^ desugars to:
// fn fetch(&self, url: Url) -> impl Future;
}
Man I’ve been waiting for this to be stabilized for a long time. So excited about it.
I don’t use rocket normally but it was great when I have used it. Rust and foundations seem to have a…storied relationship though, so I hope this plays out well.
To add, turning everything into an enum can make the code nearly unreadable and hard to work with. This isn’t Rust, and there’s no performance gain for using enums over string unions.
Honestly, easiest to learn is probably React. That + market share would make me learn that first. Newer frameworks tend to base what they do with ergonomics from React. Even my favorite (at the moment) frontend library, SolidJS, has all their tutorials with references to how you do things in React, and how similar signals work with Solid. Learning Vue, Svelte, all have the same issue; they compare themselves to React to show you how they do things with their library. And it makes sense, for better-or-worse.
Doesn’t matter what an internet rando thinks, there are more React jobs at the moment. I’ve only seen Angular used by large enterprises for internal BI apps, which are harder jobs to get.
That’s huge thanks for the tip
Love using this, the only issue is some key defaults clash with nvim, but it’s customizable so basically a non-issue. I do wish they’d make a PS port, not everything I do can be done in WSL. But when it works it’s great.
literally every app on windows/macos