I feel like calling Janet "A Clojure" is doing both a disservice. It's more like a "Clojure-like but smaller on purpose" programming language, and it's also (self-described) for "exploratory programming, scripting, and fun side projects" rather than Clojure's intended target audience.
Nothing wrong with that, having different target audiences makes sense and is probably preferable, but Janet is more than just "Clojure without the JVM" much like C# is more than just "Java without the JVM".
Really disappointing to only learn this after a decade, but on Linux changing from 60hz to 40hz decreased my power draw by 40% in the last hour since reading this comment.
Going up from what date exactly? Construction start is when you already have all plans approved, permitted and financed, so 4 years from construction start is far from "putting up a plant in 5 years". So, some examples for 5 years all in?
There is a trick, you can multiple build simultaneously. Or better with a slight delay, so that construction crews (which do separate phases of construction) can move between projects and use experience gained in one build in another build.
Nuclear construction requires highly skilled workers doing very high quality work. One of the biggest problems with nuclear construction in U.S. and Europe is that last significant builds have been done around 1985, companies doing nuclear construction closed or moved to other products, or moved to maintenance, upgrades of power plants.
I second this, Tcl is a lovely language in general and quite lisp like. One of the nicest and most unexpected experiences was learning it last year. Tk is then trivial from Tcl, with nice native GUIs being 15 mins away.
Yes indeed, I concur completely with your comments. I've used Tcl/Tk for a few decades and for a long time enjoyed it's Lisp-like character. Of all GUI toolkits Tk is by far the best thought out, no wonder it's been adopted by a number of other languages.
Tcl does have a few disadvantages, for one the lack of distinction between string and list types makes certain programs hard to write. Also the absence of lexical environment for the apply command requires awkward workarounds. Many Tcl users dislike expr syntax.
Warts notwithstanding, Tcl has allowed me to be very productive. Over the years it's been steadily improved, and yet remains mostly compatible with code written even decades ago. That's a rare accomplishment in the programming universe.
reply