It's a pleasant and practical language to write, yet fairly safe.
Imagine the safety of Rust but looking more like Python (or Haskell...), the concurrency of Go (since V5), and without a borrow checker (but a GC instead).
I watch some intro to OCAML videos, got excited about the languages features, then tried reading some real OCAML (Tezos, which was touted as the star of idiomatic OCAML projects - can't find the site that listed it now), and I found it so incredibly dense, hard to read, and almost completely devoid of meaningful naming and comments. It felt similar to reverse-engineering minified code to me.
oh it definitely is. A lot of Haskell can look like you describe, but it's perfectly legible if you have enough reps under your belt. I find normal languages hard to read nowadays.
One piece of advice: some things in university might be pointless and/or hard. Treat it like a game, the goal is usually quite clear (grades, passing, etc.) and work as much as you can to achieve the best results. Don't think too much about whether there's a point, and if it's boring, find ways to not make it boring (read more literature about it, solve trickier problems)...
But that's only because (unfortunately for the airlines) miles are not a universally accepted currency. Just like some poorer countries needing to be bailed out by the IMF, despite issuing their own currency.
You joke, and yet [Lucas 1988] uses an amusement park as a toy model to demonstrate how monetary shocks can affect real economic activity. The key difference between this and Chuck E. Cheese, though, is that Chuck E. Cheese is the only merchant that accepts their tokens for any sort of payment.
This is called electron beam writing, and is done routinely in research settings and to write the lithography masks, but does usually not have the required throughput for a production line. The upside of mask-based lithography is that all structures are exposed at once.
A single beam column with the machine around it costs millions already, and takes quite some space. Wafers are simply not large enough to accommodate more than, I'd guess, two or three columns at the same time. Each with independent optics.
A somewhat simple 2x2 cm Si photonics Chip in my line of work takes about 24h exposure for two layers - a full scale wafer is hundreds of times larger, more complex, and has dozens of layers. The math, physics, and geometry just don't really work out (yet)
Imagine the safety of Rust but looking more like Python (or Haskell...), the concurrency of Go (since V5), and without a borrow checker (but a GC instead).