Omg, doing (because I need to) C or C++ stuff, where you have (or lets say you are bound to for several reasons, compatibility, regulations,..) C++11.. or even C99 .. man I feel so old and slow as I potentially am, lol.
598 karma · joined January 14, 2022
Omg, doing (because I need to) C or C++ stuff, where you have (or lets say you are bound to for several reasons, compatibility, regulations,..) C++11.. or even C99 .. man I feel so old and slow as I potentially am, lol.
But even then, what's different limiting to the safe subset of C++ (haha yeah I have to chuckle a bit) and declare the dame for the necessary unsafe parts there? I really dont get it it seems ;)
"Copilot is generatin 40% of code in projects where it is installed" - is that any true, to start with something? What are these kind of projects?
No because Rusts bigger calling card is the borrow checker, which adds a lot of complexity besides other things in Rust, and even leads to justifying unsafe (because some optimized correct data structures are just not possible with it).
Second no, because if Rust calling card is that, you can have this alone even in the most hated unsafe C++ if you limit yourself and admit to doing it right. If you quote that sentence you must also quote his calling card, which is about culture and complexity of language:
> In addition to this, I think the most important reason we have so many vulnerabilities (and bugs in general) is completely disregarded in the hunt for “safe” code: culturally tolerated and even encouraged complexity14. In conclusion, putting up with Rusts compile times and submitting to the borrow checker seems like an extreme solution that doesn’t address the most important problem, which is a cultural one. Jai on the other hand is extremely concerned with complexity and tries to get the cultural part right.
And in that regard I agree with him, definitely better there than C/C++, BUT NOT MUCH!
That's why I fully agree, Rust may be not it, and something like Zig, Jai, Carbon or even Herb Sutters safec++2 thing may shine one day more..
Rust is overfocusing on the memory safety part, which adds too much complexity while not even being able to get fully rid of unsafe..
> widespread rehabilitation is impossible
Ah come on, that assumption is easily disproved by looking a bit around and elsewhere.
Geberally surprised about the false beliefs around anonimity on block chains, as soon as you have the right anchors they are the most tracable.
Or do you mean you sit at the doctor on your vacation, pull out an app to access your CT scan and hand it him over somehow or what is the use case here really? Seems so unrealistic on manu levels and much more easily realized with more solid tech, sorry?!
> Encrypted records can be easily added by any doctor/clinic as your public key is publicly available.
Yes, crypto101, which works fine without any blockchain?
But for why and what if I'm not into martial arts? Just for social norms and studies that say only then I am really engaged and pay attention, which is definitely not true for me?
But why not just a reasonable product? Yes, what could that be, there cannot be something that is fairly priced and people really want, need, what just helps. Not today anymore!
> By your definition insurance
I know what you try there and on a very abstract level you are maybe slightly right, but PLEASE no, high level gambling (==milliseconds&millions) is not at all comparable to the insurance model in many regards, foremost maybe purpose for the community?
(and its pretty clear that fintech here sure doesn't mean the classical bank and modern "normal" payment system... ).
No, because both approaches could be right at a higher level, to pretake that decision at this level is definitely wrong here?!
double wow to people seeing it like that.
:(
> I would rather inherit someone's stateful JavaScript or Java than a complicated codebase by a seasoned Clojure, Haskell, Scala developer. I stand a better chance understanding the sequential code than a complicated recursive monad. Depending how it was written.
True, but you add here the "complicated" attribute deliberately .. usually it is the other way round. The functional approach code is simpler to read and reason ( and usually not with much recursive monoids), while the believed sequential program has so many "concurrent" paths (even if there is no real concurrency, but just in the many hidden ways how the super distributed statefulness is manipulated).. not?
From climate catastrophe to treating other empathetic beings, as soon as there is beleive of any impact to our current luxuries (even if not even proven): Economy over all!
Humanity IS doomed. And deserved..
Click on the first picture and you get the undertitle:
"Eadweard Muybridge first lesbian kiss Item x of 16 Eadweard Muybridge naked kiss women lesbian"
So even if not the photographer's statement or intention (though the article does also not clearly state the opposite..) and the article's author made thst up, it is like it is.
> You seen to be reading something that isn't in this article, and using the word "woke" in a bizarre way.
Those judgements are often seen quick and given easy, but not always as simple, eh??
Hell, why are we even discussing that??? Point for OP...