[kwlug-disc] On Rust

[Mikalai Birukou]

>> If you want it to be read and understood correctly by other devs, write
>> it in Rust.
> To all Rust fans: I'm curious.  If you were to list all the major
> programming languages you've used in your career, in chronological
> order, until Rust, what would that list look like?

Let me do chronological order of language use:

- Pascal and with/within Delphi visual thingy

- C / drop into C++, pre-generics epoch

- Fortran (gonna count numbers)

- Java (with big body of work)

- Python (with big body of work)

- CommonLisp (wrote TwinLisp transpiler, switching brackets into 
C/Java-style syntax, ... vs semantic in language)

- JavaScript

- TypeScript (huge body of work, cause by now gut knows value of types 
helping, reminding about intentions behind code)

- Kotlin, in 20-th, hence through lens of Java and async-implementations 
in Java-backed land, e.g. TypeScript

- Dart, in 20-th

- Swift, a touch

- Rust


Java had for a long time throwing an exception, at runtime, when you 
change map, that you iterate over. Rust asks, what resources I have 
borrow, at compile time.

I start to use Rust macros as a copy and paste of sections that are 
similar, but not quite to split function. Simpler than Lisp's, as it has 
more explicit info. And I have been decoding C macros in others' code.

I really appreciate traits, and my ability to add "method" on a thing 
from somewhere else, with "impl ... for ...", ... like you do in 
JavaScript. In Python? Don't remember. To me, there is hint of approach 
to objects-style in CommonLisp. Vibes.


I am a ctrl+space programmer.
I fully appreciate that ... language server with editor, part of IDE, is 
what one really writes and reads. Plus docs. So, my dives into languages 
was with IDE tooling. Libraries is a secondary thingy here.