markdown-tweet-scheduler VS urho3d

RIP Markdown Tweet Scheduler [1], you worked great while you lasted.

[1] https://github.com/reidjs/markdown-tweet-scheduler

This article talks a lot about how to read Twitter and who to follow. I think it misses a very important part of Twitter, writing! I use Twitter as a microblog for publishing my dumb, half baked thoughts.

I even wrote some code so I could schedule posts without logging in https://github.com/reidjs/markdown-tweet-scheduler

Urho3D, an open source C++ game engine.

I believe Urho3d supports MacOS (see 'about' page on the legacy website).

Urho3D

If you're literally clueless your best bet is to first start learning with an existing clean-ish engine like Urho3D implementing whatever feature/screwing-around or start with a framework like nVidia's Donut that gets you your window and basic rendering in place.

I would recommend tracking through the gist of Urho3D's batch/batchqueue stuff as it's a reasonable setup that is very intelligible (if you speak C++), it's not the greatest thing on the planet but you should be able to roughly grok it in an afternoon. Doing draw batch-pumps greatly streamlines the final drawing code.

You could try Urho3D or its newer fork rbfx.

I use an engine called rbfx which is a fork of the Urho3D engine. A lot of it is just the fact that I've been using it for over a decade, so I am comfortable with it. I'm a programmer, not really comfortable with integrated editor engines such as Unity or Godot, and the easy C++ extensibility of the engine appeals to me. Plus it's decently powerful, and well supported on a lot of platforms (I build for Windows, WebGL, and very occasionally RPi for the most part) and is open source to satisfy that stubbornly libertarian side of my character.

You might be interested in Urho3D.

If you don't mind something experimental, there is a C# version of Urho3D that is in fairly active development. There is also a C#-scriptable branch of the Urho3D fork, rbfx, located here. Both of these projects are still pretty in-the-works, but are still pretty usable.