castle-engine VS http-client

The Castle Game engine is not mentioned often, but it looks pretty mature from the screenshots and has been in active development for many years. Most recent news update was a few weeks ago. I have not gotten around to try it yet. Only started playing around with FreePascal a bit last year after not having used Pascal at all for some 25 years.

https://castle-engine.io/

This is a nice introduction. Apparently the author also implemented a full game engine in Object Pascal: https://github.com/castle-engine/castle-engine/. I wonder whether the performance is sufficient; according to available benchmarks (e.g. the CLBG) the code generated by FreePascal is about three to four times slower than C/C++; does anyone have experience with it?

Thanks to Eugene Loza, this is already in review: https://github.com/castle-engine/castle-engine/pull/471.

Trung Le (Kagamma) has been doing lots of work with CGE + FPC WebAssembly. His fork contains a branch wasm32-wasi-port with lots of active work. I absolutely expect that we’ll merge it to CGE webassm\platformer\test at some point, and then to master branch :)

The Castle Game Engine mentioned in one of the courses sounds interesting. https://castle-engine.io/

.2. With big thanks to Freedomax, our TCastleEdit now works with Windows IME much better. The IME popup appears at a proper place, and is thus visibly associated with the input box. This is great for languages relying on IME for input, like Chinese. See PR 457 for movie how it looks.

Delphi is a good language to learn. Compile fast to native machine code. C++ compiles slower and C# has garbagecollection which can cause hickups. Game engine in Delphi https://castle-engine.io/

Fortran-lang's role (as an open-source org) has been 4-pronged: Tooling (build system and package manager, testing, eventually compilers etc.), modernized and maintained libraries (stdlib, minpack, fftpack, etc.), community space (Discourse), and evangelism/marketing (website, Twitter, blog posts etc.). Some members participate in the standardization process of the language, but the groups and processes are separate and complementary.

It's true that one goal may be to pick an important race and try to win it.

Another goal, in my view more important, is to make Fortran more pleasant to use for people/Orgs who need it (there are many) and for people who love it (there are many).

I've found that more often than not, people/teams first like working with a technology, and then come up with technical arguments for why that technology is the best choice. Often the arguments are valid, sometimes they're made up, but ultimately underneath it all you either like it or not and that's all that matters. My goal with Fortran-lang has been to slowly and continuously increase the surface area of Fortran's likability. Fortran is not for everyone, but for people who think it may be, we can work to make it better and more pleasant to use.

As one example, we just released a small library to make high-level HTTP requests from Fortran applications: https://github.com/fortran-lang/http-client. This was a product of one of our Google Summer of Code contributors.