Hi Bogdon! I want to make a cross-platform app with Tauri that makes use of Python libraries (and others). I think this is possible with sidecars. However, I'm worried about updating the sidecar libraries after users installed the app. A video on this topic would be awesome ! At any rate, awesome channel man and many thanks.

I'm mostly still learning the basics but looks like you guys are making some pretty awesome stuff. Can't wait to have a go once I'm up to speed.

It might be you've forgotten about Rust Chi-shee... 😁

@@pioneer_1148 same here ❤

Rust did exist 10 years ago so that's still valid though it's a joke

@@coffee-is-power Yeah but given how relatively obscure it was up until like 2017-ish? your hiring pool is going to be SUPER limited and you're going to run out of it very very quickly.

So far so good 😎

Ex firefox developers...

True XD

we cannot learn everything... wanted to learn everything, but cannot... the question is, where should i first focus on

Is this something like PNPM solves?

it would only reduce the compiles where you've added a new crate, as all further compiles you've already got the crates. most compiles are not going to be adding a new crate, so i would think it actually doesn't make that much difference. still probably worth doing tho

Sounds a lot like Nix regarding the reuse of crates.

WTF c will never die!!!

Rust is not as minimal as C/C++ when it comes to programming for embedded systems like micro controllers. The fact it relies on a working internet connection and package manager for external libraries, that makes things worse.

Thinking that C is deprecated is hilarious. Almost every language relies on heaps of C code like glibc, its ABI (when you use rust code through C++ or vice-versa, you're actually generating C-conforming code from one to be used by the C FFI of the other language), and it's getting more and more used in this way. It is also uniquely simple, which is a major feature for embedded systems and any performance-sensitive task, for which it's still a major considerarion.

The most important factor for a first language is flexibility (can you do a lot of things with it) and learning reasources. Therefore, it is better to learn Javascript or Python first IMO

@@computerfan1079 Thank you! Those are the two I'm considering. I just heard Rust builds "good coding habits" and is challenging, so if you understand it everything else is easier. I tend to like to save easy things for last so yeah. Not that you asked, just maybe for any other takers. Again, really appreciate your input!

​@@TONyjustRoCks If you are enjoying it, then continue with Rust. The employability of a language doesn't matter when you are just starting out.

@@blemmyes it does when you're trying to land a job in the next few months, good luck with rust

Thanks guys!

Or for WebAssembly. E.g., as an experiment I ported a hand-written machine learning application to WA and scripted it from React.

Oh wow. I think I'm currently at the point where I like tools written in rust but don't actually write rut 😢

My reasoning would be that rust's correctness strategy for asynchronous and multithreaded code requires extensive understanding of systems programming with functional programming concepts being a great help on top of that Essentially, rust requires you to know multiple concepts beyond just writing simple programs. It's just possibly too overwhelming for a beginner cause fighting with the compiler in non trivial scenarios would require understanding much more than you're currently even trying to learn as a beginner. This doesn't apply if you're a stubborn learner willing to get into the nilly gritty details of everything

To solidify my point - when writing a server for the first time with shared data in most other languages, you'll probably write unsafe data sharing that'll lead to data racing bugs, try to wrap your head around that as some sort of rite of passage after which synchronous safety will finally have a concrete meaning to you - you learn through experience there. Making mistakes is one of the best ways to learn and understand things long term. Whereas in Rust you would have to either write synchronously safe code from the very beginning, run into deadlocks cause you hadn't learned about channels, cells with atomic operations etc to reduce mutually exclusive code when handling shared state and how to handle mutexes correctly in the first place, or fall into the dark habit of writing unsafe code before you fully understand why you're writing unsafe code (and that you're actually supposed to define your own justification for safety that the compiler cannot understand or check for you at that point)

@@Grempington yeah not knowing lambdas or asynchronous programming will be hell, as some crates straight up are only suppose to work with the await keyword

Finish what you start otherwise you’ll never finish anything and just have a bunch of incomplete side projects

the framework tauri wil make something like react native. Backend rust frontend your js frameworks like react etc

I also experiment with Rust and ChatGPT. Its pretty good, and if there are problems, i just paste the rustanalyzer errors into chatgpt, and it fixes it! Its so damn awesome.

It can be a confusing language, you end up looking up awnsers a lot because of that. Once you get a better habg of it, I'm sure you'll be asking less from chatgpt

It doesn't matter if its competitive programming tbh. I'd go with C++ personally since I'd get a lot more learning resources of algos written in C++ or Java. If its a personal project then definitely go with Rust

@@roct07 thanks sir.

C++ is by far the best option. As we break a LOT of rules and good practices for the sake of writting speed. Rust can be way more verbose and unforgiving in this aspect. For sure some problems would be good in rust.

Just remembered of unsafe in rust haha. But even then I think rust is slower to write

@@leonardodavid8749 I suppose that you could write your own macros to do a lot of common patterns far more shorthand with rusts macro system though, in principle you could even create your own DSL through the macro system if you really wanted and have those macros use unsafe code if you like. Though barring coming up with your own language in Rust I agree that if literal writing speed matters, its probably too verbose in most cases.

😂

It was :D 4:34

@@joe0932 try reading the original post again

@@BillEffinMurray Ah gotcha, my bad 👍

This is complete nonsense, there is nothing wrong with cryptos. We could question web3, but cryptos do solve a social problem to some extent.

@@diadetediotedio6918 no they don’t. all the crypto stuff is centralized anyway in practice and is only useful when you can convert it back to fiat. there are few things you can buy directly with crypto and how unstable it is makes it questionable to use it as digital cash. it’s a failure. it’s just gambling and scams. i bought drugs with it 10 years ago and that was really the only problem it ever helped solve, ebay for drugs with ways to stay anonymous.

Any senior developer should always be language agnostic. You are only limiting your own growth if you limit your toolbox to only one or 2 languages. I have been a developer for 34 years (never wanted to go into management), and through the years coded in ASM86, Pascal, C, C++, C#, Java, Python, JavaScript and am learning Rust also now. I have never ever needed to go job hunting as I was always head hunted.

If you stick to crates that don't use a lot of procedural macros it's not bad at all.

Well, passion is good but I need to pay the bills.

Good for you!

it's hard compared to other languages, but if you learned rust as your first language, than it will be naturally easy to get also, what's your crate? just for curiosity lol

I don't see how that's a problem unless the syntax is inconsistent.

@@davidowens9597 but for beginners will it b easy?

Because it is a growing tech? lol

Rust is all over the place.. Doesn't really need advertising. It's more pervasive than people think, from big tech to startups to tools.

How is it better

There are things you can do with Rust that you cannot do with Go. Ergo it is not possible for Go to be better. Go is simply not usable in many situations.

Interesting opinion, why do you think that?

Go is better because you know go?))) there is no better but more universal, and answer is Rust)

Gophers: “Go is better” Google: *quietly switches to Rust*