Відео

BASED-agen

Nice clip, bro.

John 14 21 He that hath my commandments, and keepeth them, he it is that loveth me: and he that loveth me shall be loved of my Father, and I will love him, and will manifest myself to him. 22 Judas saith unto him, not Iscariot, Lord, how is it that thou wilt manifest thyself unto us, and not unto the world? 23 Jesus answered and said unto him, If a man love me, he will keep my words: and my Father will love him, and we will come unto him, and make our abode with him.

this article is such a sloppy job. how about instead of saying "stoopid people don't understand ADTs", just go feature-by-feature and compare it with analogous solutions in other low-level languages? Go is not low-level

38:32 " I'm investigating languages such that I can show people..." * remembers Jai is a 10 yo proprietary language * "what's coming into the future my goal is to show you what's available and what potentially the next 10 years could have available to people to us" Jk, don't hate me. I know this might apply to Zig too, since it may not be ready for prime time just yet. But you have to admit, Jai is not it. And we don't know when it will be (if at all). Because it's closed-source and unavailable to the - general public.

Delphi and Visual Basic dead?

C# drawing had Unity t-shirt that is the other strand of c# person.

I work serverside, and need to maintain a small maintainance UI. We run Jquery, and that's just about it. Our experiment with Angular was a failure. We spent more time satisfying the framework than building the whole thing with just jquery for dependency. React is a little better in that regard, but not better enough to consider introducing it. All we need are a few displays, nobs, dials, buttons and text fields that trigger commands to the big java server. It's been really surprising how little support there is for that.

Rust is really complicated and yeah it's my skill issue

i swear python to me is harder than Rust .. it s full of magic code

for loops in the python is the slowest thing ever. when i removed loops from drawing section in python, that were working absolutely fine in c++ in the same app, the fps went from 8 fps to 130 fps, lmao

You had me at stop saying rust

Prime ignores the let-else clause in rust which makes rust error handling read like go error handling.

RAII is horrible

22:35 To be fair that should really be a match statement to avoid the multiline return. match id { 1 => Some(User::Alice("Alice".to_string())), _ => None }

Solid 4 minutes before reading a world of the article 😂

I think you cant even compare things like c, c++, rust to go or any other GC language.. c: is a simple language and is easy to learn, but programming correct c is very complicated and takes years to develop. c++: is a more complex language then c, and so a bit more difficult to learn, in return you get some nice things so you can write correct c++ a bit faster then c rust: is a complex language to learn and takes quite some time, in return you can easily write correct rust without match effort, conclusion: program correctly in these non GC langs takes time, the ratio of where this time is spent depends on the language, and is of your own choice.

I really do feel the "type modification cycle" mentioned here, where you declare your data types, but they're so precisely defined that they quickly become interdependent and when you change one, you have to change many of them. I have a hard time recognizing when fucking with types is a productive exercise in modelling the application and when it's just procrastination, because it is so often a mix of both.

I thought Meursault would use assembly.

I hate how he dopemine :w in his vim

2:48 Reqwest... uwu.

you don't HAVE to propagate the err in Rust with the ?. You can also handle it with a match statement just right where it occurs.

Funnily enough, chances are due to the fact that other libraries depend on is-number this will *increase* network usage, because now this longer line will need to be downloaded.

I can't tell you how many times I've been doing lifetime refactors and thought "id rather just manage the memory myself"

prime lang when?

How much did you spend on that kettle?

New style async in Java with virtual threads, concise stacks, thread shutdown/cleanup on failure. If child virtual threads start virtual threads, the task scope tracks the thread graph and shuts it all down on exit. Very cool. By bye reactive. try (var scope = new StructuredTaskScope.ShutdownOnFailure()) { var shelterFuture = scope.fork(this::getShelter); var dogsFuture = scope.fork(this::getDogs); scope.joinUntil(Instant.now().plusSeconds(2)); // easy timeouts var response = new Response(shelterFurture.resultNow(), dogsFuture.resultNow()); // ... }

Rust is not difficult we just have too much people out there with MemoryManagmentPhobia and this Cult is getting bigger

Rust is top! :-)

Uh oh is he using rust again

It's not complicated, it's annoying and "not fun" (this argument is of course subjective). But nonetheless, it has huge pro's.

Complicated is what it is ... or convoluted. What it isn't is complex.

"Stop Saying Rust Is Too Complicated" - says someone who is proficient in rust, but sucks in other languages. skill issue.

Spent two years using rust professionally. And then I quit and went back to C++. It's refreshing. I went from miserable to happy.

Compared to any GC'd language with a managed runtime, it's absolutely more complex.

Rust syntax is ugly AF

rust is inconvenient, i do not know how rust is better with their borrow crap in comparison to smart pointers in c++. p.s. golang's error handling is great.

I consider a language complex if I couldn't bootstrap a compiler for myself if I had to. I don't think I could implement rust, particularly given the lack of a written standard to write towards.

Prime keeps complaining about people who use anywhow as if thats an inherit problem of rusts error handling. 😂 its a library, I just don't use it. By default that's not how Rust works.

Rust people always advocating that the rust way is the only good way is why we all hate Rust with passion. Rustaceans are A LOT to handle, and the worst part is they think they they have objective arguments, when most of the times is just preference on programming paradigms. Now, the argument about gen-ai will be the way of doing code and we need the rust compiler to save us.... talk about dystopian future, the two hype trains I hate the most together!

Rust👏Is👏Too👏Complicated👏

rust is literal trash

for me, the Rust community is more complicated than the language itself

00:12 "software engineering problems that show up in every sufficiently complex system" Ah yes, my sufficiently complex hello world in rust where i try to get and print chars from the string by index

Keep saying it, it adds value to rust connoisseurs

3:50 just use .map_err()? instead of only ?. Map the library's error to your own. And in mapping, if the error is unrecoverable, you can panic or whatever you need.

What really gives me fatigue in the tech world right now isn't the new frameworks per say, I need to actively select a framework, so it's up to me to do that choice. My real annoyance is the JS semantic versioning trend going on that says: minor version is a patch, major version may contain breaking changes. The breaking changes part wastes so much freaking time for me. I do a lot of maintenance work on already existing systems, and we certainly don't want to prematurely slide our systems into the area of legacy code where none of the packages has been updated for 5 years. That means that at some interval, things needs to be updated. Which means tons of broken packages with changes I don't give a crap about. Sigh. New version of the framework may require other packages to be updated, breaking changes. If the breaking changes where significant then I can understand this, but many times they're not, it's just that some package maintainer thought, "oh, we can do this thing this way, that will 'look better', so we'll do that in next major version" hence me wasting hours on unnecessary BS. I do wonder sometimes how many hours we combined waste on things like this. Breaking changes should be RARE. In Linux they have a rule: "DO NOT BREAK USER SPACE", perhaps a tad bit extreme for packages, but the general idea that it should be avoided as much as possible would make life easier for all of us. We don't just use your package, we use many different packages. Breaking changes for minor reasons is a huge waste of everyone's time. I've recently gone through a horrible maintenance cycle dealing with this, hence this rant.

29:40 when I tried Rust, it definitely wasn't a few minutes of compile time. Given that I do TDD, the compile times and borrow checker hits were taking way more time. Yeah, I probably could learn to play with / circumvent the borrow checker to reduce that time, but even C++'s horrendous build times enable my workflow better. With tests and valgrind I can get rid of most bugs anyway, and keeping thread communication narrow (e.g. channel-like constructs) will reduce bugs there. P.S. I'm getting less and less enthusiastic about RAII

Probably due for Microsoft to release another Incompatible XAML framework. Drives me nuts, I loved WPF. It’d impossible to keep up with all the other versions.

Google Android devs reported 68% less bugs in new Rust code vs old C++.