- theCodeStigWith Metals the Scala 3 development experience is better; plus one is no-longer tied to one specific IDE.
- No, you're right. It is perfectly clear from the type signature
- Exactly. I've long held the sentiment, that pure functional programming is easier than imperative programming. The only hard part, is switching from an imperative mindset.
- Meta, Jane Street, IO Global, Standard Chartered Bank
- Has anyone tried Uno with F#?
- 9 years in Singapore, and I’ve never gotten Myna feces on my pants (nor anywhere else on my person)
- It's an Indian ringneck parakeet (aviculture name) https://en.wikipedia.org/wiki/Rose-ringed_parakeet
- Sounds like you have a sun conure
- predators hunt, humans farm
- One can run Emacs in the terminal. What’s the use case for this?
- This is definitely true in Asia
- Here we go again
- I use exa daily, and this is the first time that I’ve heard of eza. From a marketing standpoint, eza should be merged upstream.
- I trialed a similar set up with code-server for a few weeks, and was shocked at how well it works, provided stable and fast internet access.
Although VSCode is impressive, at the end of the day, I'm an emacser. I went back to: emacs in a terminal over mosh, accessed with Blink Shell on the iPad; or access the same instance over Microsoft Remote Desktop for a desktop experience.
- The compiler/type system is your friendly assistant. Learn to use it, and it's your greatest asset.
- This exactly.
The Scala community caters a lot to JVM/Java inter-op, and to recruitment of Java engineers. In the peak-hype days, Java compatibility, and Scala for Java engineers learning resources were a huge selling point for Scala. Now it is one of its greatest weaknesses holding it back. Even as late as June 2023, the second edition of Functional Programming in Scala is catered toward Java programmers.
Functional purity is an option in Scala (no pun intended), and the org/team must have the collective discipline to write pure code in-order to make it work.
Pure/lazy effect handling is not included, one must use a 3rd party library. There should be one, or a small handful of compiler options which would enforce purity by the compiler. There isn't. The -Xlint options are not easily discoverable. WartRemover is a 3rd party library, which doesn't get enough visibility. Some of the "good stuff" from Typelevel should be absorbed into the standard lib.
The numeric types are not ergonomic, there is no natural number type for example.
I haven't had issues with Haskell tooling, though I also use Nix. On the flip side, I've never heard anyone say "I love SBT". Yes there are alternatives to SBT (Mill for example), but again they suffer from low visibility. Martin Odersky has admitted faults with SBT, and praised Mill; yet, what does the Scala community push... SBT.
- It's like a specialised case of org-babel for the masses.
Anyone with emacs can do this today, for free. The huge caveat is that it requires emacs. Where this tool shines, is that it's a superset of markdown, and thus not tied to any particular editor.
- Yes, most likely. Many organisations are still tied to manual/semi-manual deployments due to company policy or regulatory compliance (banks for example).
- You’re right. I love emacs, though I must admit it’s quite a barrier to entry