Technologique
730 subscribers
143 photos
3 videos
42 files
906 links
Deeply involved developers about various aspects, tendencies & conceptions of programming technologies, FLOSS, Linux, security, cloud infrastructures & DevOps practices, distributed systems, data warehousing & analysis, DL/ML, web3, etc.
Author: @andrcmdr
Download Telegram
One step to more wide application of Rust in aerospace sphere!
Obviously, there're a lot more things should be done to use Rust even more widely, espesially for embedded systems. 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), error handling, and process recovering, after alloc errors, not yet fully supported in Rust stdlib's collections API (see this issue: containers should provide some way to not panic on failed allocations · Issue #29802 · rust-lang/rust · GitHub)
But the Genie is already out of the bottle!
More things to come and that's will be huge!

https://github.com/CIUDSE

#Rust
Rust release 1.59.0

https://blog.rust-lang.org/2022/02/24/Rust-1.59.0.html

Be aware that incremental compilation now off by default and should be enabled explicitly via set RUSTC_FORCE_INCREMENTAL=1 environment variable.

What's new:

Cargo and rustc now support stripping when the binary is linked, this can be enabled in Cargo.toml.

In generic types default values for const generics can be specified now.

Inline assembly in unsafe blocks via asm! macro.

#Rust
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://tttttt.me/technologique/1351

https://tttttt.me/technologique/1490

https://tttttt.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
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