1,333 karma · joined December 31, 2016
Just like Scala and F# a decade ago.
Or like ruby 15 years ago, or like Java in the 90s.
In the end of the article I've told this should be taken lightly, as an exercise in minimalism and a joke.
When I am curious about something, I read as much materials as I can, and I use the blog as a tool to document my findings and put my thoughts in order. It's rather a last test for me to see if I can make sense, and an opportunity to practice my English.
3 of my articles so far went to this front-page and it was a nice feeling of appreciation. But that's not the point of blogging, internet points don't matter.
> "Mary", "Smith", 10, Test, "Some long string with, comma" ?
We've lost our way in the masked marketing the cloud providers are creating to help us solve problems we will never encounter, unless we are building the next Netflix or Facebook.
I've made some experiments on my phones (bot Android and IOS), and you would surprise how many of the apps are "calling home". Because those apps are closed source, God knows what information they are sending back to their servers.
When I was hungry I was taking an apple instead of eating biscuits.
RSS is the only way I know, without having to scrap things by hand, to get an aggregate of "news/articles" from the sites and blogs I follow, and I consider to be of good quality.
I prefer to filter my information like this, instead of having to rely on some algorithm, or endlessly scrolling in a "social medial wall" full or clickbait articles, immortal/vintage memes or exuberant rants.
If RSS dies, what is the alternative then? I understand that technically speaking it's not a good solution, but let's have something else before killing this.
PS: I've clicked on this link from a RSS reader (just a simple browser extension... that keeps me posted every morning).
Also as a non-popular opinion in this current age, I recommend you to learn how to implement your algorithms in C, rather than an easier to grasp programming language. Even if you are probably not not going to program in C in your future career, understanding how memory management works will give you an edge later.
Also given C's loose style, you will also get some skills in organizing your code in a language that doesn't impose a lot of obvious constraints to the way you write your code. You will be able to build your own conventions, and evolve them once you get more skilled. Seeing what others are doing is also important.
Good luck!
PS: Don't fall into the macro trap, you will never get out. (inside joke).
Initially mw was mem_write and mr was mem_read, and reg was registers, etc. But because I wanted to keep the functions as short as possible (to put them on the single line without making them totally unreadable), I've comeup with those names, which are confusing at first.
But from a performance perspective, you are right!
You are right about the TOC, my other long articles have them, but for this one I simply forgot to generate one. I will generate it tomorrow.
There's no compiler, and yes you are right managing a limited set of registers is hard when compiling from higher level languages. But there are a few compilers for LC3, so it's not impossible to write them even for such a limiting number of registers. But this is not my area of expertise, so someone more knowledgeable can comment on that.
When it comes to FE, I don't touch that anymore. I did some react and old angular in the past, but it was more like an obligation... I don't "feel" the community, or how complicated things have become.
For programs that are closer to the hardware or operating system, I feel quite comfortable in C (not C++).
For scripting, data visualization, and anything math related I use python. I usually end up having one big script, terrible written that works.
When it comes to databases, I pick mariadb because I have the biggest experience with it and it didn't disappoint me. From the NoSQL land I've tried the most popular ones, and I had good interreactions with redis, and the elk stack.
I've tried to love Go and Rust... I still try, because some companies I follow and have interesting projects are using them. But it's more like a long term goal to learn rust.
I believe my stack is boring, if not boring conservatory.