darkgenesis blog comment

[utterances-bot]

Writing efficient markdown using GitHub Pages - DarkGenesis - indie development for the new world order

A guide to writing the best markdown you can get on your GitHub Pages site, using tricks and tools to help

https://simondarksidej.github.io/writing-efficient-markdown-on-githubpages.html

[SimonDarksideJ]

Comments are finally enabled, Time to get the feedback train running again

[klimcio]

After reading this article I am now doubting whether I should continue learning Godot, or MonoGame for my games :D (I'm already a .NET Developer, so it sounds obvious, and yet, it's not...)

[SimonDarksideJ]

I feel your pain @klimcio , the choice for what to follow is not always an easy path and must be based on several deciding factors which are unique to each developer/learner.

• Is the programming language used familiar to the developer (previous experiences), developers usually have a preference on a language they currently/prefer to use. With no previous experiences, options are more open.
• Do you feel more comfortable with GUI style development (with a visual editor) or do you "see the code", as to whether a GUI is important to you (some devs to only build their own GUI for parts of their game and dislike a general editor)
• Is the engine/framework too restrictive (have to do it their way) or offer enough openness and flexibility to extend how you like.

Ultimately there is no right or wrong answer unless you are embarking on a project which will require a lot of effort.

In the end, I say to give any engine/framework you might want to use a week, no more, definitely no less unless you hit roadblocks, and try and make a simple game roughly along the lines of something you will eventually want to build, be it 2D, 3D, VR/AR or more.

NEVER make decisions from other peoples views (unless there are a lot of negatives from experienced devs) because every developer is unique, what is not right for others might be perfect for you.

So give GoDoT a try and then try MonoGame, or Stride, or StereoKit, or others, then choose what you feel most aligned with.

P.S. I've seen some suggesting devs should just build their own engine in C++, which for developers already familiar with how engines work enables them to lock in what they need for their project. However, I've known many devs (who shall remain nameless) who switched to building their own engine and still have not released their game. It can be good but also has it's pitfalls. For new starters especially, use something existing to get a feel for what you want BEFORE thinking about just starting from scratch, just my 10 pebbles worth.

This is starting to feel like another article.

[badpotion]

Thanks for this post. I've been looking at branching out my framework knowledge and Monogame looks like a way better fit for me than I would have guessed. As some one that used to do code-centric dev back in the day long before Unity, there's a kind of full circle familiarity that I'm loving the look of.

Thank you for all the hard work!

[Xonatron]

Love your work here!

(P.S. Comments only show when you click to make a comment. Had I not, I would not have known this comment thread was happening!)