Must watch/listen episode of Lex Fridman podcast, especially in current situation on crypto market (which will alienate many people from decentralized cryptos, definitely, and then may swamp into the developed market of centralized proprietary digital currencies of central banks) - discussion about money, currencies, assets and values with a very solid person:
https://youtu.be/gp4U5aH_T6A

More on this topic:

https://t.me/technologique/1351

https://t.me/technologique/1490

https://t.me/technologique/1491

What was happened with Terra (LUNA) and their TerraUSD (UST) stable coin and what became the reason why the whole crypto market is down now - really good analysis, which shows the weaknesses of the whole crypto market, especially for the altcoins, which has the paired stable coins and liquidity pools in BTC (which is true for the most of other coins) - read in this thread:

https://twitter.com/OnChainWizard/status/1524123935570382851

Really close example of the weakness of any L1 crypto liquidity ("beware of crypto whales", especially rightful for BTC):
https://twitter.com/megastuffs/status/1520355389555978240

Here's my conversation with John Carmack, legendary programmer & engineer. At over 5 hours, this is officially the longest conversation I've had on the podcast, and we can talk many more times. This was really fun and a huge honor for me. https://www.youtube.com/watch?v=I845O57ZSy4

Intel SGX and thus AWS Nitro enclaves are having vulnerability.

https://aepicleak.com

https://aepicleak.com/aepicleak.pdf

https://github.com/IAIK/AEPIC

AES-NI and RSA keys easily leaked through APIC registrers and MMIO memory, i.e. through data transferring between L2 and L3 cache. This is Intel's architectural vulnerability, affecting 10, 11, 12 generation.

Microcode update (with registers and MMIO pages cleaning after every operation with enclave) is already on its way.
Also it's recommended to use MSR registers (x2APIC mode) instead of MMIO (xAPIC mode) to use and access APIC registers.

https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00657.html

https://www.intel.com/content/www/us/en/developer/articles/technical/softwaresecurity-guidance/advisory-guidance/stale-data-read-from-xapic.html

https://blog.rust-lang.org/inside-rust/2022/02/03/async-in-2022.html

Obviously Rust needed more powerful abstractions, GAT (generic associated types) implementation stabilized, also going even further to HKT (higher kinded types, also referred as types of types, or type constructors), and dependent types, with following implementation of CoC (calculus of constructions).

And as a systems language there're a lot more things should be done to use Rust even more widely, espesially for embedded systems (automotive and aerospace sphere for example). For example, fault tolerance to run-time memory allocation exceptions in stdlib collections, dealing with infallible methods (panic on allocation failure in operations with collections), more improved error handling (to handle panics in main thread), and process recovering, after alloc errors, not yet fully supported in Rust stdlib's collections API (see this issue: https://github.com/rust-lang/rust/issues/29802).

Have you remember (or am I just oldie here) the story behind Firefox versus Iceweasel in Debian Linux distro? And how many years it was take for resolution of that situation for community?

Looks like Mozilla lawyers in Rust Foundation made the same for Rust name, logo and branding. They successfully thrown shit on a fan again.

This is bad for community, open source and projects, which are based on Rust language and bad for wide spreading and mass adoption of Rust language.

It's time to make a fork of Rust language compiler, consolidate community efforts on it and name it TRUST with Ferris logo. =) This way it will conform with FLOSS spirit.

(And looks like I should now unstick my favourite violet Rust logo from my old Thinkpad laptop.)

https://youtu.be/gutR_LNoZw0

#Rust
#RustLang

A good intro, with an example on a poker black-jack game, to the relatively new features of C++, which are provides a good memory management practices (with unique_ptr and shared_ptr).

https://www.youtube.com/watch?v=b8V-WIjlScA

#CPP

Next chapter - about shared pointers

https://youtu.be/Tp5-f9YAzNk

#CPP

Crab Lang 🦀

Well, making a community driven and community oriented fork of a Rust language was only a question of time. History does repeat itself again.

https://crablang.org

https://github.com/crablang/crab

https://github.com/crablang/crabgo

#Rust #RustLang #Crab #CrabLang

Beware (or be aware, already) of community fragmentation!
'Cause it's already happening (Crab language as a response to Rust management mistakes)!

Here's the video about all recent events in the Rust community:
https://youtu.be/QEnuzwCWpgQ

#Rust #RustLang
#Crab #CrabLang
#RustFoundation

Rust Rover

New standalone IntelliJ IDEA based IDE for the Rust language ecosystem with a cool name. Not just a plugin for CLion anymore.

https://blog.jetbrains.com/rust/2023/09/13/introducing-rustrover-a-standalone-rust-ide-by-jetbrains/

Rust language gaining more and more traction!

#Rust
#RustLang

You know what does it mean. Wouldn't be equal to Rust though, in terms of immutability for everything by default.

Upcoming streaming from CppCon:
https://youtu.be/I8UvQKvOSSw

eBPF: Unlocking the Kernel

Documentary about the development process of #eBPF subsystem for #Linux by the Linux kernel hackers all over the world - the executor (#VM and #JIT compiler) of extended #BPF bytecode to run system programs safely in a kernel space and use Linux kernel API and system calls (including #POSIX).

This simplified the development of programs integrated with the Linux kernel in a better way, so cloud native landscape with cloud infrastructure development has been changed forever!

https://youtu.be/Wb_vD3XZYOA

BTW, #Rust compiler has a eBPF backend, already proved for production grade programming and compilation, and has a bunch of good frameworks for developing for the Linux kernel using eBPF VM host functions interfaces.

#Rust
#RustLang
#Linux

Uncontrolled type conversions and forced type coercion can be dangerous, affect your codebase and make high financial harm to your product, even if you're using memory secure programming language like Rust!

https://lapitsky.com/how-to-get-paid-800k-for-a-clippy-warning/

(Enable all Clippy warnings in your CI and locally! It can saves you from harm!)

#Rust
#WASM

An article that unburied an old hatchet - Rust versus C++ debates.

https://lucisqr.substack.com/p/why-i-think-c-is-still-a-very-attractive

#Rust
#CPP

And a good (and what's more important - fun) analysis with debriefing of this article, with pretty fair reasoning for both sides.

https://www.youtube.com/watch?v=Wz0H8HFkI9U

With funny takes and a good sense of humor (for ex. here 14:40 - it cracks me up! =)

Moral: Use what fits better for your needs and tasks - there is enough of engineering space for everyone!
For me, as I'm working on modern finances and cloud techs - I've made a choice already a way back before, many years ago.

This reminds me an old debates on what's better, faster and more secure - Borland's Turbo Pascal, Modula -2, then Delphi versus Borland C++ Builder and Visual Studio.