Lazarus gives you cross-platform and multiple architecttures at no cost. From what I recall, Lazarus is a more lightweight install, while the Delphi IDE has better coding features. For the classic VCL (Delphi has other new frameworks), I haven't found anything that LCL cannot do yet, but I don't do anything unusual with the widgets. The FreePascal language is mostly compatible, however, they don't plan to strictly follow newer Delphi language features (e.g. inline declarations).
My favorite camera + lens in use is a micro 4/3 mirrorless body with a pentax lens adapted with an off brand "speed booster" making my lens an F/1 in principle. Filling in the gap where the mirror was supposed to be is an easy problem, making it fun to repurpose lenses designed for SLRs on mirrorless cameras. There are even passive spacer adapters that just fill the flange distance. It can be an option for Pentax to design these adapters with the autofocus also working.
Back in the early 2000s, I had a Windows 3.1 386 machine to myself as my family was using the new PC at the time. The glaring difference to me was the missing "X" so I programmed a small window that would dock on the corner of the active window and provide an X close button (as well as maximize, minimize as the real ones were now obscured by that window). It was very hacky-spaghetti Visual Basic code using whatever I can figure out from WinAPI documentations I could find and I was too inexperienced back then. But it worked. My older brother didn't realize the "X" wasn't supposed to exist and it even ended up getting bundled with someone's Calmira fork. Good times.
Borland stuff are great for getting things done and are also what I'm considering if ever I will have time for recreational retro-programming. But for an article, C++ with WinApi would give more to talk about.
Put another way, I'm not sure what you would be paying for instead of using Audacity (for a full blown DAW, I'd still go with Reaper). I haven't used MuseScore in a long time (it was good enough for me back then), but it had also been improving a lot lately. And I don't know of anyone who still uses WinZip (though I still see WinRar on less savvy users).
I personally like using IDEs when coding. Reading is another matter, and the code we read will not always be inside an IDE (e.g. code shared on the web, or written in a book).
Could what winevdm be doing on 64bit Windows be considered the same? (I find it very interesting but don't know enough to tell if it should be considered an example)
There's a relatively new C++ GUI library literally called "Elements". Not sure how it works though, but the way it looks, and the music background of its creator makes it appear that DAW applications might have at least been considered.
In my former university, the people in power hasn't changed in the past 30 years. So worshiping the big publishers is still the norm and it takes a while for new students to detach themselves from their supervisors' delusions and realize the whole scam.
It's not just readers who pay. Scientists also have to pay some journals to get their work published (assuming the submission went through) which is totally backwards. Scientists do not get anything monetary from what the readers pay. Now look at other publishing industries. It's the publishers that pay the creators (even if the rates may seem unfair at times, it is still far far better than negative gain for scientific research content creators). Been there multiple times back when I was a PhD student. So I have absolutely nothing against those who use the free sites.
As the books document complete implementations, they do feed you the code, and it is easy to fall to the trap of just copying the code from the book. I think the best approach is to port it to another implementation language as you read the book. However, compared to other books I've seen these are more "granular" in the code explanations so you're simulating the authors' coding thought process instead of just looking at big blocks of finished code.
In particular in Crafting Interpreters, there are many parts where you go back and revise the code from previous chapters as some language features/concepts are introduced in subsequent chapters (my memory of Writing an Interpreter/Compiler in Go is not that fresh).
I think it is a good sign that these books start with "int main()" (or it's equivalent). Other books I've seen start by describing functions in isolation, so they are not immediately testable, and it encourages the reader to just get the finished codebase to have something to play with.
I've gone through similar books at some point. The closest that comes to "Crafting Interpreters" is "Writing an Interpreter/Compiler in Go" by Thorsten Ball. You can tell that these authors really took their time to describe everything going on with the code presented and carefully guide you through testable code leading to a full functioning interpreter at the end without having to look elsewhere outside the book.
Lazarus is a compelling reason to pick Pascal. But I share your pain and had been looking for alternatives for machine-code-compiled RAD GUIs. To add, only modern Delphi supports var declarations that can be placed elsewhere other than the top of the function.
While I know others for whom church have worked, I often feel that people, especially myself, are not who they really are at church, only showing the good parts of themselves while hiding their unpopular quirks (i.e. the warts and all). This prevents me from being more interested in people I meet at church.
I used to have an irrational fear for curly braces and semicolons, given BASIC looks clean and simple. I see that now in some young programmers who try to stick to Python. Interestingly, seeing Rust code for the first time also reminded me of that.
Basically how Pascal still exists in Delphi/Lazarus. I'm not a fan of the language, but Rapid cross-platform GUIs that compile to native code instead of bytecode that anyone can just drop to ILSpy are really compelling.
At the opposite end of the spectrum, there are languages with case insensitivity and even style insensitivity. I personally avoid them, but it's interesting how the users of these languages have a very different philosophy.
Except where comparisons being made, the first and second halves are mostly independent. If the tree-walking interpreter might not be what you have hope for, you can, in principle, skip finishing it. The bytecode VM half is a re-implementation (in C instead of Java as the first half) and only the scanner/tokenizer has some inevitable redundancies in implementation. For me, who had less prior knowledge in interpreters, it is still good to have fully gone through both halves to relate to the comparisons and trade-offs of both implementations.
There's GNU Solfege [0], but I have not really used it (I was a casual piano player that realized theory just gets in the way of fun for me). It has ear training for music patterns and has some music theory practice in it. Not sure if it has a mobile version, but it's been around for a long time.
Also a simplified font spec while we're at it? While there are libraries for it, it is apparently discouraging if you wanted to code your own parser for the existing font formats.
> I do not understand why anyone would ever choose to be an acedemic,...
When you're young and don't know enough it's easy to look up to the "smartest" people you know at the time, which are often your teachers and other university celebrities. And while at college, if you don't have any serious plans, masters and so forth seems like easy options going forward. Your university mentors will even make you believe it is a good choice. Been there myself. I regret it. Surrounded by academics while my friends and relatives are just "normal", I had a very one-sided worldview.
On the bright side, I think more are quitting the academe recently, realizing it is not worth it.