tinywm VS love

> Nobody's requiring Wayland.

Yet. Defaulting to it is one step on the path towards removing support for X and independent window managers forever.

I deeply, deeply care about running an independent window manager. A minimal X window manager is a page of code: https://github.com/mackstann/tinywm/blob/master/tinywm.c (yes, plus xlib); a minimal Wayland compositor is tens of thousands of lines of code.

> contrary to your statements, it's perfectly ready for prime time

These comments are full of folks mentioning issues. Wayland does not support my window manager; thus it is demonstrably not ready for prime time for me.

> Wayland is the way forward

It may actually be. I’m not as opposed to Wayland as I may sound! But do you understand how you and other Wayland advocates sound — like advocates? ‘Wayland is the way forward’; ‘there's no future for Xorg’; these things are arguably true, but they are also rather cruel to say (a bit like ‘inevitably you and everyone will die’: it really is true, but it’s also not at all a nice thing to say).

I do think that Wayland or something very like it may be the way forward, but it needs to be an evolution, not a revolution. I know that the party line is that that’s not possible, but I suspect that rather than not possible it is just very hard. It’s always easier to greenfield, and it is always hell to be 100% backwards compatible.

But that’s what it needs to be.

Hah. I didn't think this was quite HN worthy at this point - the code is still a mess, and has plenty of bugs. It was however the wm I actually use since I got frustrated with bspwm and did a very minimalist rewrite of TinyWM [1] in Ruby [2] and expanded it from there. It was painful the first few days until I'd had time to add multiple desktops and the start of a tiling mode. But at this point, it's "almost" pleasant for me.

The warnings are real, though, apart from the initial hyperbole - this is likely to break for you in all kinds of horrible ways still. I use very few applications beyond (my own) terminal, (my own) polybar replacement, (my own) file manager, and a browser, and so once Chrome and my own apps mostly started working ok I've had very little incentive to make sure it behaves nicely with anything else and I know the distinction between different EWMH window types is incomplete and broken - just not in ways that usually affect my own use.

[1] https://github.com/mackstann/tinywm/blob/master/tinywm.c

[2] https://gist.github.com/vidarh/1cdbfcdf3cfd8d25a247243963e55...

picking a random bare bones wm tinywm

Or Check out TinyWM. Its just a few lines of code.

TinyWM

I've built a few games with my son over the years. The fun part for us was all about fast iteration, and then laughing at the bugs together.

There are some other recommendations here for how to approach 3d, and he is specifically asking for 3d -- but I want to put in one more pitch for 2d: the fun-to-tedium ratio can be much higher.

I wonder if you could spend some time prototyping some of his ideas in LÖVE https://love2d.org/ -- if you show him the smallest sketch of something working, he might have an idea about what to add next.

Many years ago, on a flight, we went from 0 to game before we landed (with no experience).

* When a cell is born it randomly takes on the color of one of its (3) parents.

To try it out:

1. Install LÖVE for your device from https://love2d.org (~5MB and open source). (iOS requires building from source on a Mac, or installing the third-party Love2D Studio: https://love2d-studio.marknoteapp.com)

2. Install my Lua Carousel from https://akkartik.itch.io/carousel (~100KB). It includes all its source code and can be edited live on a computer as it runs.

3. Copy the ~100 lines of code from the bottom of https://akkartik.itch.io/carousel/devlog/651711/new-version-after-9-days and paste them into Lua Carousel.

Probably the most important piece of software we'll be playing around with is a game engine called LÖVE. Lua is well known around developer circles as being a good scripting language when it comes to making games, and this engine is one of the more popular. I'll be going through installation at the end of this post.

I got it – these are the steps I took:

1. Download Love from https://love2d.org/

libGDX is great, but I can understand if it's not for some people. This also applies to love2d, raylib and Monogame

You don't need to use git if you don't want to. Try downloading the 0.10.2 source directly here (the file you want is love-0.10.2-linux-src.tar.gz); I see you've tried this already but try again just to see what happens. Extract it to a directory (e.g. love-0.10.2-linux-src) and then run:

Love2d (MIT/C++/Lua) https://github.com/love2d/love

- Löve (doesn't have a separate page, but showcases a few games at the bottom of the page): https://love2d.org

The game, Wasp Escape, was built using the open-source Löve 2D game library for Lua.

love2d (lua) is a productive, fun, good docs, and most importantly proven / field-tested 2d game library, with easy to learn fast to compile and fast to run language - lua. while lua might not have a lot of features as python, the big bonus is that its much more focused language, which is important because otherwise you can get easily distracted on bells and whistles that other programming languages provide, i know that from experience