scalanative-graphics-bindings VS handsonscala

LWJGL has lots of bells and whistles if you only need OpenGL take a look at: https://github.com/regb/scalanative-graphics-bindings

I recommend people go through Hands-on Scala, by Li Haoyi, a fantastic developer in the Scala community.

You can have a look at https://www.handsonscala.com/ and see if that's for you!

his book, https://www.handsonscala.com/

Hands-on Scala Programming

is there a great resource, book or library‍ on classic Algorithms and Data Structures in Scala, e.g. similar in scope and quality to Sedgewick Algorithms in Java https://algs4.cs.princeton.edu/home/ I found a very helpful section on algorithms implementation in /u/lihaoyi superb Hand-On Scala Programming book , but unfortunately it's only a few pages (p.107-121). And most other books provide algorithms just an illustration for some neat language feature. The thing is, to get a job as Scala developer these days (in competitive firms) one needs to be a competitive programmer, master of Leetcode, and Scala doesn't seem to have strong ecosystem in that regard as Java, Python or C++. Edit: in DIY spirit and as a learning exercise i'm thinking of translating Sedgewick Algorithms from Java to idiomatic functional Scala, if anyone wants to join this effort or aware of similar ones please let me know Edit 2 (in regards to comments on 'reinventing the wheel' below): if Scala is so great as a language and functional programming flagship, where are all the libraries of functionally implemented algorithms replacing conventional CLRS style imperative/mutable implementations?

handsonscala is a great read for programming in general using scala. Especially if you're the practical kind of learner.

I will toot the author's horn for him. He has a great series of Scala posts on his blog [1] and his book Hands-On Scala Programming [2] is a great introduction to building real applications with Scala so that any experienced developer can understand and extend them.

I work at a small company that has been using Scala for 7 years. Some of the prior employees clearly enjoyed playing with advanced language features and writing libraries for the most general possible case even when that made it hard to understand how they were used for the 2 actual cases we needed to address in our application code. Akka, Cats, and Shapeless were all over the place.

Those earlier employees have churned off to other places and I have successively simplified the code they wrote that is still useful, while encouraging the use of no more language power than necessary in new development. Hands-On Scala Programming is the book I give new hires as a language introduction that shows the sort of style to be preferred. It's much more like super-powered Python than like Haskell.

I have written C, JavaScript, Python, and Scala for money. When I started on Scala I had never written Java nor used any JVM language. I have come to really appreciate the rich ecosystem of JVM libraries, the instrumentation and profiling tools I get, and many aspects of the Scala language and standard library. I love Scala's collections and miss their power and ease when I'm writing Python. (Which I still do for certain scripting tasks and for accessing Python-ecosystem libraries.)

[1] https://www.lihaoyi.com/

[2] https://www.handsonscala.com/

Also, many scala folks are not happy with sbt. There's a new build tool on the block Mill - https://github.com/com-lihaoyi/mill - by Li Haoyi . He's a scala master and he's written a _great_ intro to scala https://www.handsonscala.com/

I tried using wkhtmltopdf for rendering my book https://www.handsonscala.com/ to pdf, but in general I found it pretty buggy and unreliable. Lines of text would get split between pages, some CSS like flexbox didnt render properly, font sizes and page scaling was sometimes off (e.g. a big image on a page would make everything else shrink), etc. In general it "worked", but it didn't work well.

I ended up swapping in Google's Puppeteer library to render my PDFs, and despite needing a bit of plumbing to get my Scala build script talking to the node.js runtime, in the end it worked much better. Things looked the same in puppeteer PDF as they did in the browser, which is something I could never quite achieve with wkhtmltopdf