haskell is pretty much the best managed language you could ask for as a game dev.>immutable datareally helps with concurrent / parallel code as well as networking>good C bindingsyou can use C++ libs for physics, graphics, etc>functional stylegreat for writing business logic without it becoming a fucking chore>FRPreactive programming done right. several implementations available in haskell
>>101213648Why use hashkell if lua and its dialects can do 99% of all things that hashkell does + more? Or why not use hashkell with lua since it has some bindings to it i think.
>>101214561uhwat
>>101214593Lua is also functional , also has c bindings and is already a popular game language. Haskell is niche and struggles on it own thus making haskell + lua an idea worth considering.
>>101213648idk make a game and showcase it to convince me op
lol
>>101213648cool, post 10 popular games written in haskell
>>101214233why are mpv devs like this?
>>101214848hrt can fuck with your emotions at times especially if you are already unstablespeaking from experience
>>101213648Have fun with the garbage collector or porting your game to anything that isn't desktop. Also have fun getting libraries working on Windows.I've written a rather simple game in Haskell and I speak from experience.
>gc lang for gamedev
>>101214890Almost forgot, also have fun with space leaks and countless hours of optimizing and making functions strict.
>>101214916so our only choice is rust?
>>101214929C++ or C with raylib if you're basedC# if you're indian
>>101214929If you don't want the language and tooling to get in your way you write it in C. I don't even like C all that much but realistically it's one of the best choices for a game. The language gives you enough guarantees to enable you to write software that works, unless you're retarded. Memory isn't even an issue if you understand that you're not supposed to be allocating and freeing every single thing in the game every frame, instead just reuse memory through pools. You can also always add tests to guarantee certain things about your code if you really need to.Oh yeah, that's another downside of Haskell, have fun trying to reuse memory. The language doesn't even allow it, not even through the C FFI because it still creates garbage. You literally have to modify GHC to add a way to be able to reuse memory. At least this was the case years ago but I haven't checked if they made improvements in this regard.I personally write everything in Forth these days but I wouldn't recommend it to anyone who doesn't enjoy Forth and just wants to write a working game. Simply because tooling is almost non-existant and you have to be skilled enough to write your own tooling or even your own Forth implementation if you want to port it to something that doesn't already have a Forth with the features you need. You can port Forth to anything, so as long as you write relatively portable Forth, you can get it working on anything if you have the time and skill. For instance, you could trivially write a Forth implementation in Java and have it interface with Android. If it would be fast enough is another question, but for more performance you would need to write an ARM Forth implementation and then interface with Android, which isn't as trivial as piggybacking on a high level language like Java.To put things into perspective, you can write a fully functional Forth that runs in any high level language within a day or three, but performance may be an issue.
>>101214929>>101215179thanks but im sticking with rust desu
