gilmi

Not everything is mentioned in this list. Check out the release notes[0].

[0]: https://downloads.haskell.org/ghc/9.2.1/docs/html/users_guid...

Because it's not an effective learning resource. Too many people read LYAH only to be left with a very shallow understanding of how to use Haskell and little to no experience on building even small projects in Haskell.

I mention other, better resources in my haskell study plan: https://github.com/soupi/haskell-study-plan

Reminds me of the Deep C slides

https://www.slideshare.net/olvemaudal/deep-c/255

This is very nice! I think it would be more useful if it talked about the memory model, heap allocations and pointers which I'm guessing is pretty important for anything non trivial.

I don't know, I haven't watched most of them! But the best one I did watch this year was Alexis King's 'Effects for Less' (Haskell).

https://youtube.com/watch?v=0jI-AlWEwYI

cs4410[1] is really really good, and cse131[2] is basically the same thing but with videos. I highly recommend them both.

[1]: https://course.ccs.neu.edu/cs4410/

[2]: https://ucsd-cse131-f19.github.io/

I love 'the incremental approach to compiler construction'. Here are a few other courses that use this approach to teach compiler construction:

* http://www.ccs.neu.edu/course/cs4410/

* https://ucsd-cse131-f19.github.io/

* https://jeapostrophe.github.io/courses/2017/spring/406/notes...

Let's be real, life is too short to read every article on the internet before deciding if it's worth your time.

There are alternative preludes you could use instead that provide a much better experience. I recommend taking a look at relude [0].

Could you share a bit about your experience with sockets in haskell? I had the chance to use sockets in haskell on multiple occasions and they worked as expected.

[0]: https://kowainik.github.io/projects/relude

This is a very good comment.

I think the author did a great job with the format of this tutorial!

It includes all the steps needed to write the app, has exercises, is neatly splitted to chapters with clear expectations and summaries for each chapter and so on. Everything needed to reduce frustration, maximize knowledge retention, and make it a nice experience as possible to the reader. Awesome work!

Ok. Thank you and good luck with Gleam!

I'd really like to read about your finding wrt hot code loading. Is there anything you can point me to?

Purerl (erlang backend for purescript) is worth a mention in this context:

https://codesync.global/media/purescript-on-the-beam-typed-o...

Not at all - thank you.

I have created an updated version of the game available for download which includes the following features:

* Automatically restart the level on death

* Updated bullets opacity and speed

* Enter key can be used to progress textboxes

* Scale down window size using the F12 key (unfortunately this somewhat messes up the fonts, but it's the best I can do at the moment)

Also a reminder that you if you press 'R' 5 times in the main menu, a new hidden menu will appear where you can select a specific stage of the game to play.

Thanks again for your feedback!

I have made some changes after your feedback. namely bullets changes, usage of enter in textboxes, and auto restart on death. Linux build is done. Will try to build for windows tomorrow.

Thank you very much for the feedback. I haven't really gotten much feedback on the game so I appreciate it.

Regarding the resolution - what is the resolution of your monitor?

There is a hidden option to go to a level of your choice - press 'R' 5 times to get the hidden menu option. I should probably write that down somewhere. And I should probably revisit the opening scene and make it a little less bland.

Regarding the player bullets, I have tried a few options and thought this was ok, but I will try a few things again. thanks.

I let the level continue for two reasons, one is to let the player regroup before retrying if needed, second is to let them see a bit more of what's left. But I can understand if that makes it a bit weird.

To be honest it is basically just a POC. I haven't received a lot of feedback on the game so haven't really planned on adding more polish or extending it. Your feedback is appreciated because it gives me some ideas on how to improve it.

I didn't really want to add as much bullets as I could because I was afraid it would completely frustrate anyone who played. Earlier prototyping stages had more[0] bullets. But maybe I'll add another level with more interesting pattern.

[0]: https://www.youtube.com/watch?v=qh62jESSRT0&t=0m28s

Check out this list of applications written in Haskell:

https://github.com/soupi/haskell-study-plan#a-few-cool-open-...

And don't forget first class records with row polymorphism!

Interested readers might want to Try PureScript[0] for a quick demonstration.

[0]: http://try.purescript.org

> There are many ways of writing wrong C code, but you only need to make sure what you write is correct and in defined behavior, that’s all about C programming.

But this is a something that even experts fail to do.

Matt Might's article is really good:

http://matt.might.net/articles/intro-to-make/

Alexis King covers some of the benefits in one of her blog posts about Hackett[0] and in her talk Languages in an Afternoon[1].

[0]: https://lexi-lambda.github.io/blog/2017/01/05/rascal-is-now-...

[1]: https://youtube.com/watch?v=TfehOLha-18

Hey thanks!

Alternative opinion (self plug):

https://gilmi.me/blog/post/2018/07/24/pfgames

The Haskell wikibook[1] is a better free resource.

[1]: https://wikibooks.org/wiki/Haskell

Nighthawk looks very nice!

However, I found out that for me tui is where it's at for music players. Using cmus combined with a drop down terminal such as tilda or a tiling windows manager is the most comfortable i've been with music players.

When a language designer takes their project seriously: http://docs.racket-lang.org/hackett/index.html