1,081 karma · joined August 9, 2018
I did this in 2021 in GO and Ebitengine and I was blown away by the performance the screen was mostly white with pixels, how easy it was to get the context running, and how many pixels I could move on the screen at 60fps... I was truly impressed. I've been using this approach for the last 30 years I guess ;-) We're a long way from moving a few hundred pixels on a 16 bit CPU per frame... greybeard out
However some of the downsides included DLL hell and requiring 3rd party components for functions like TCP/IP (IP-Works) and more advanced UI elements and so on. I remember investing quite a lot in such components - I recall componentsource.com as being a key marketplace. I think one of the main issues was OS integration, hooking into Win32 required all kinds of incantations. Decompilers were also an issue.
It brings back memories of a much simpler time in terms of development, especially the UI editor - it was so fast to just draw a few forms and hook them up to code. I used it a lot for statistics type interfaces, and CRUD type systems, however I wrote a P2P communication tool back in 2000 that even had VOIP. I also recall writing a game that wrapped OpenGL and running it on my SGI520 Windows NT box. So much fun.
I transitioned to .NET and C# and didn't look back or bother with VBScript.
However I recall at the time feeling so abandoned by Microsoft, having to learn another complete system from scratch - existing projects didn't come across cleanly.
Anyhow... just a bit of a greybeard rant about the 'good old times'...
Just as an aside - after playing around with BBC Basic during covid, I was so impressed how OS calls were implemented in the language. If VB integrated with Win32 to the same level BBC basic integrates with RiscOS it would have been pretty much the perfect tool in my opinion.
However in my opinion (at risk of getting everyones ire) - I think the ace is the "1" card.
Things I like: - builds for web, works on mobile
- crazy fast build times compared to unity
- animation timeline feels better than unity, calling code triggers etc. I remember it took me a while to learn Mechanim - with Godot I could instantly understand how it worked.
- GD script is surprisingly fun to code in, yet has features I wouldn't expect (i.e. calling a function by it's function name - stored within a string)
- everything just seems to work - I've only had two minor issues, one with calling code from the animation timeline within the editor (which doesn't work) and also some issues with muting master audio bus
- the two problems I've had were pretty easy to solve, unlike with unity - right from the beginning in version 1.0 I always seemed to be the guy sending strange tech support stuff and finding new bugs that required insane work-arounds to solve. Just unlucky I guess.
- I love the fact that it's open source
However... just for balance here are my two concerns:
- v4.0 seems to be a rewrite, and this scares me - because Unity went down this track and at the end when starting a new project one had to choose between many different versions of unity. Choosing the right version depended on what features you needed vs. stability and compatibility with previous assets that might be in your library
- no... really that's it.
So... my experience with Godot has been a lifesaver! My new projects kicks-ass and turned out much better than it would in Unity - and it's been a pleasure to learn and develop in .... maybe I just needed a change?