scastie VS Hugo

From personal experience Scala also works. It's 100% possible to learn monads using https://scastie.scala-lang.org/ as a scratch pad.

Instead I typically use https://scastie.scala-lang.org, or an ammonite script, or just create a new file that extends App in my test directory. The thing that worksheets do better is that you can import things from your project (like the little app in the test dir) but they also show runtime values (like repl or scastie). However I've just never gotten them to actually work.

I strongly recommend you play around with the local Scala REPL. I have Scala 2.13 on my main dev computer and Scala 3 on my other computer. The local REPL will let you know when things are deprecated and give you hints as to what you should use instead. Scastie https://scastie.scala-lang.org/ can also be a big help.

Operationally, as you might expect from a language borne from academia, Scala tooling can be problematic and compilation can be slow--particularly if you are not yet using Scala 3, which only recently emerged and is very slowly percolating through the ecosystem (Remember the Python 2 to Python 3 transition?). But type inference, a vast standard library, and the time-tested reliability of the JVM make you very productive once you get the hang of them. Performance varies with the JVM you're running, but regardless you do have to contend with the size of compiled objects and the latency of garbage collection at runtime. When you want to experiment, you can skip the ceremony of writing a class or test and instead use a command-line REPL, an online REPL called Scastie you can share, or an outstanding third-party command-line REPL called Ammonite. Dependency management is achieved with SBT typically but also more general JVM build tools like Gradle and Maven.

I am using https://scastie.scala-lang.org/ which does compile server side in Scala. The UI is a bit hard to handle tho.

https://github.com/scalacenter/scastie#how-do-i-embed-scastie

Hugo, one of the most popular open-source static site generators, is written in Go and optimized for speed, flexibility, and ease of use. In this guide, we’ll walk through how to seamlessly integrate Uniqrate into a Hugo-powered website, giving you a simple way to gather user feedback and improve your content.

Several years ago static site generators were all the hotness. Around then I switched to Hugo [1] from Wordpress and it's been a good experience. You do all editing locally with the CLI then chuck it to Git to be built and hosted by Netlify.

[1] https://gohugo.io/

As you may have noticed this site is built using Hugo and Papermod theme. After playing around with Hugo and getting comfortable with it, I wanted to push the initial version of this site to the git repository and set up an automatic deployment pipeline to be able to easily publish updates to the web.

I used to build my website using a known tool named Hugo, a static site generator. I also have a LinkTree account that displays all of my links.

Hugo - used by example for perl.com (source)

The descriptive text is stored as the alt attribute on the HTML img element, and the path to the image describes the relative path to the image or an absolute image URL. In our case, the static site generator Hugo parses these Markdown files and assets (images, etc.) and converts them into static HTML pages. I want my solution to be independent of Hugo, though, because Markdown is also used in other places, such as Readme files. For now, I've also decided to ignore external images in the form of URLs, i.e., http:// or https:// links. Mostly because we're not using them.

My previous website used the Gatsby framework, for a simple reason: I am very familiar with React, so I thought customization would be easier. However, I later realized I didnt have time to maintain a bunch of Typescript and Javascript, which made me reluctant to update my website. This time, I choose Hugo. Maintaining a small amount of Go Template is easier, and I am familiar with Golang, too.