564 karma · joined November 8, 2018
Personal blog: https://www.more-magic.net
Many people hook up their TV (or media box) to their home audio system which often has much better sound quality. The built-in speakers of TVs are a bit pointless in that context.
I've heard it said that SAP is sold on the golf course, not in the IT boardroom.
Edit: source (in Dutch): https://www.security.nl/posting/721810/Litouwse+overheid%3A+... Source in Lithuanian: https://kam.lt/lt/naujienos_874/aktualijos_875/ka_daro_isman...
And next year, there will be a new model, so all those one-star review updates to last year's model will not be seen by someone in the market for a new one.
Thanks for the kind words. I tried to keep my biases out of it as much as possible and tried to avoid making it too ranty. And on the whole, I like Clojure; it's just not really my first choice as far as Lisps go.
> It's a bit surprising they didn't get into the whole "hygenic macro" business, which seems like the most obvious differentiator between the two languages to me.
I debated including a bit about macros, but in the end decided that this would be a bit too in-depth. Clojure uses namespaces in a somewhat clever way to work around the bulk of the hygiene issues you get in CL with defmacro, but the macro system itself is rather uninteresting. I think their custom syntax for gensym is a nice touch, even though it's yet more syntax.
Scheme's macro system is very advanced and relatively complicated indeed, and the R5RS/R7RS standard system is only pattern matching/rewriting based.
Maybe I'll do a separate piece on the macro system if people are really interested.
There's just tons of research which went into Lisps, because it's such a nice vehicle for language experimentation. There's half a century of research going into Lisps. Other languages haven't been around for that long, so I suppose there's something to find in Lisp history for everyone, but it might not be the same thing for everyone!
For example, "code is data" is true in the most trivial sense for machine code, yet having code as structured data makes it much easier to manipulate. Having easy to manipulate code gives you the power to manipulate code at compile-time. Having code run at compile time inside the compiler, which is also an interpreter running the same language that you are compiling is kind of magical and mind-bending.
In fact, more recent research into this has gone down the rabbit hole even deeper, and it turns out you can have an entire tower of meta-levels (see for example http://www.phyast.pitt.edu/~micheles/scheme/scheme22.html). This is all continuing on the same basic ideas which were present in early Lisps, just crystallized and refined further and further.
Also, as research into macros has gone on over the years, hygienic macros were discovered, which Rust has adopted as well (and there are other languages which have them as an add-on, like Sweet.js). Deeply understanding how this stuff works gives you a better grip on the issues with macros in older languages (notably C).
And that's just macros (and homoiconicity). There's also lexical versus dynamic scoping. This is a lot less "magical" now than it was 10 years ago, when almost no mainstream language even had closures.
Personally, I don't mind manually entering the stuff, because you'll need to classify everything into the correct accounts anyway.
On top of that, they even use "free and open source", which refers to certain moral freedoms rather than license mechanics.
The output of inexact numbers is typically truncated. In CHICKEN, you can use flonum-print-precision to tweak that. In an example, straight from the manual:
> (flonum-print-precision 17)
> 0.1
0.10000000000000001Even for legacy projects, starting with adding regression tests for every bug you find is a great way to introduce testing. And when you add new features, you can write tests for that as well.
I find that a FP mindset is helpful mostly because it tends to reduce the amount of global or spread-around state. This in turn makes testing and quickly iterating in a REPL a lot easier. Also when later the time comes to debug, it's much simpler if you don't have a huge amount of state to set up first.
And even if a lot of state is required, having it be an explicit input to a procedure is helpful because it makes it much clearer what you need to set up when doing manual testing.
Including one .c file in another is a bit odd, but less surprising. But then having include guards makes the entire thing a bit weird :)
The worst you could possibly do was destroy a program stored on disk or a cassette.
You could even both play half the game in single player and then swap discs, but I'm not sure that really was the intention.
People who have to work hard physically may be more naturally inclined to understand how to live in a more balanced way: work hard, then relax in your off hours. Us tech folks tend to live in the same "mode" much of the time.
I personally found Stoicism helpful in becoming more self-sufficient and less whiny about things that befall me. Your example of the mug is great and can be generalised: complaining helps nobody and makes you feel worse and you get "stuck" in this emotion. Instead, move on and fix or replace it. And even if it can't be replaced (maybe it was a hand-made mug by a loved one you lost), being sad about it still does not serve your well-being in any way.
This is inherently user-hostile, as it presupposes tracking and identification. I don't want them to know anything about me!
I think KerTeX (http://www.kergis.com/en/kertex.html) now allows a similar style of pick-and-choose package installation, but it doesn't support a lot of packages (yet?).