Artem @tourer_dev

While ppl obsess AI, I finished such a wonderful book about distributed systems and server side in general. I like this book for showing the tradeoffs, pros and cons, and never talking do this and that.

keyboard_arrow_left Previous keyboard_arrow_right Next

DDIA' book (2nd edition) is my first book related to BE. I am only covering the 8th chapter and wondering of how it is difficult to implement the DB from scratch. Definitely, this is the super interesting and complicated area at the same time. #rust #postgresql #ddia

I read DDIA book, slowly, carefully. I have never thought about DBs from tech point of view as mobile development does not require it mostly. That is interesting area, definitely, I would consider jumping into it. Is Rust a popular choice for DB development currently? #rustlang

#24 It passed much time to shake my head and forget most of deep theory about Rust. This is classic learning curve. I write my own web-server without hurrying. Today, I have covered interesting topic as log::Log. Rust gracefully shared responsibility to apps. I like it, simply!

This thread is NOT about AI. Rustee! #rust #rustacean #swift

Something interesting has been occurred today. Initial commit.

#23 Whooh. Today, I completed official Rust book including appendixes. It took me more than 2 months.

#22 Well, 20 chapters of official Rust book have been passed. It took me some time to get into Rust (high-levelly). I am more satisfied with that journey than not. It gave me broad understanding of both worlds, system level C, C++ and Rust and high-level Swift.

#21 By exploring of Rust's union type I have learned about C unions. Now it seems clear how enum might work under the hood. #c_lang #swift_lang #rust_lang

#20 Refutability. I am not sure I have ever heard that before, but that is interesting to observe how Rust's pattern matching is flexible. It seems Swift has been influenced by similar design. #swift_lang

#19 To go on with C. Pure lang where you should implement almost everything you have in Swift, Rust. I suppose C devs import many libs to have the same now. But imagine how it was decades ago. Hard skills - many mistakes, oh, sounds as scientific area.

#18 The more I explore Rust, the better I understand pure difference between C and all other langs. Every concept I explore in Rust, I check on difference between it, C and C++. C always is pure, without many std staff we have in Rust or C++. Respect. #c_lang #rust_lang

#17 Swift dev: "ok, async await, it works, all works under the hood, which hood? Who cares...". It is a joke with truth. Async, futures, and you think, wow I know it. But how often do you write a runtime for it? Right, never, as I am writing Swift. #rust_lang #swift

AI certified engineer, AI does, AI boom - ah. Most people have gone crazy, literally...

#16 Atomicity and atomic operations are ones that usually no one uses or think about in Swift. Obj-c had such mindset, though. I don't know if it's used commonly in Rust prod, but that topic is another brainstorm. #rust #rust #swift

#15 Exploring OS' user dominant API layers (pthread etc) allows me to learn low-level things which I only wondering about in Swift. That is not a fault of Swift, of course (its primary aim is different and that is it), but ability to jump into things lower than language is cool!

#14 What drives me reading Rust book is that it forces thinking beyond the words and wondering of what is this and that. Covering concurrency is interesting having the Swift background before. I learned `pthread`s many years ago and it is useful for me now. Thanks Swift.

#13 Interior mutability and smart-pointers are the brainstorm for me. Feelings are similar to if you need to write Swift with manual allocation of variables and ability to mutate their inner values, but not exactly, but maybe, ahh, well, forget about Swift... #rust #swift

#12 Since I was involved into Swift only, pointers and any smart-pointers are something new for me. I understood the fundaments and high level logic behind them from learning of computer science, but never worked with them closely. Interesting. #rust #swift

#11 Cargo is a good CLI tool, really. Compared to SPM, it has pretty simple syntax (correctly saying absence of syntax). Simple, quick, powerful helper. I have never enjoyed using SPM, but Cargo has seemed different.

#10 The time to tell about Rust marketing. Iterators is good thing: single loop, safety, potential compile (MIR -> LLVM) optimisations. Key word - POTENTIAL, means that is not always truth. While we create our own Rust loop we would encounter runtime bound checks. Ah...