[0]: https://github.com/ghc-proposals/ghc-proposals/blob/master/p...
[1]: https://blog.poisson.chat/posts/2023-01-02-del-cont-examples...
1,529 karma · joined November 22, 2017
[0]: https://github.com/ghc-proposals/ghc-proposals/blob/master/p...
[1]: https://blog.poisson.chat/posts/2023-01-02-del-cont-examples...
I've been using Pandoc for my static site, which I also used for my PhD thesis. I wrote pandoc-plot[0] to render figures in documents like the author does, inspired by Matplotlib's plot-directive[1]. I feel like this feature is a must for technical writing, but getting the details right is tricky!
[0]: https://github.com/LaurentRDC/pandoc-plot
[1]: https://matplotlib.org/stable/api/sphinxext_plot_directive_a...
Even if tools to programmatically create maps were available, I wouldn't have known how to program. So this is more about my lack of knowledge of tools of the time.
4-bit is small enough that you can build it manually, without the use of external tools (which I don't think existed at the time anyways).
Highly recommended for children interesting in computing!
I also enjoyed the writing style, and wandered onto another post. First sentence:
> I’ve always seen cathedrals as presenting a kind of implicit argument to atheists. Something like: God must exist, because otherwise it would have been insane for people to build [a cathedral]
This is my new favourite writer
At my work, my team of 5 was tasked with creating the beta version of a customer-facing app in 2 months, after which we launched and iterated as fast as possible. It was barely functional, and did not scale well, but it worked. Now we're working on the next phase -- making it scale and add customer-requested features.
This is typical in tech startups facing lots of competition.
The author remembers this, uh, event differently than I remember it... George Hotz boldly claimed that he could "fix Twitter search" faster than those lazy Twitter devs, only to bail almost immediately. Hubris!
On the way out, he removed that login popup as a sort of consolation prize.
I'm a big proponent of the "writing is thinking" mantra. Unfortunately, in my experience, not all technical leaders value grassroots proposal processes like the Oxide RFDs
This stands in s t a r k contrast to other disciplines (e. g. Physics) where papers are usually ultra dense, making it hard to read even for subject-matter experts.
Thank you for sharing
However, unfortunately, the notation is so terse that I can't imagine spending the time to learn this. This looks write-only.
Is there an obvious reason to prefer a k-like language like Klong, over e.g. Futhark[0] or Accelerate[1]?
Do you think you would have benefitted from a resource like the Rust book? I've been toying with the idea of writing something similar and donating it to the Haskell Foundation
I'm not familiar enough with Nix to understand, but it looks like the performance gains in the blog post might not all materialize to upstream users.
In any case, cool stuff
I share the author's frustration with the lack of non-compiler-related examples of GADT uses. It seems like such a powerful idea, but I haven't been able to get a feel for when to reach for GADTs in Haskell
However, if you decide to start learning, the path is hard, especially if you come from a non-computer-science background like me. I attempted to learn Haskell twice; I bounced off the first time, quite hard, and didn't try again for years.
What worked for me is a combination of two things:
* Having a goal in mind, that has nothing with the choice of language. For me, it was building a personal website
* The book Haskell Programming from First Principles [0]
and if you have more questions, reach out.
The one construct that unlocks this lack of colored functions, STM, did require runtime support (as opposed to language support), which at least is transparent to downstream developers
[0]: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...
In practice, it is not. The canonical Haskell compiler, GHC, is excellent at transforming operations on immutable data, as Haskell programs are written, into efficient mutations, at the runtime level. Also, since web development is quite popular in the Haskell community, lots of people have spent many hours optimizing this precise use-case.
In my experience, the real downside is that compilation times are a bit long -- the compiler is doing a LOT of work after all.
This is both hilarious and more common than you might think. In my field of expertise (ultrafast condensed matter physics), lots of noisy garbage was rationalized through "curve-fitting", without presenting the (I assume horrifyingly skewed) residuals, or any other goodness-of-fit test.
Regarding nuclear power: it is a great technology for the base load (edit: I mean firm power), but there's always going to be fluctuations in consumption, which needs to be met with fluctuations in generation. Grid interactive buildings can help mitigate this fluctuation.