jdee VS river

I think Emacs is great for programming. It has modes for almost every programming language. For LaTeX mode the AUCTeX package is incredibly useful. Besides LaTeX the languages I most often write code in are bash, Java, Tcl, troff, Octave, R, Clojure, Objective-C, and Scheme. Emacs has good modes for all those (in particular JDEE is what I use for Java). There are auto-completion packages for Emacs, though typically I use those only for the few times I write C or C++. Emacs also integrates well with most version control software.

I'm still using jdee. Because of the updates to how JDK after Java 8 locates core classes, I had to make an update to the jdee server backend that is used for things like finding import class names. Once I did that I'm able to use it with Java 8 on up. I believe that the github repo fo the server now has the same updates.

More info on the wiki https://github.com/riverwm/river/wiki

Here is the related github issue

If you can get past some minor wayland related annoyances, river is pretty easy imo, you can write a config in whatever format you want, it just needs to be an executable file, the most common type is a shell script. The actual configuration happens by calling the riverctl program from the file, which from what I've heard is a similar method compared to bspwm.

Coming from awesome you may find river more to your liking than sway.

River crashed everytime I closed Chromium. The developer fixed it in 5 minutes :)

I've written a plugin that implements the river-layout-v3 wayland protocol in Hyprland. This means you can run something like rivertile, river-luatile, rivercarro or kile as a layout provider.

Author here. And yeah, as of 0.6.0 it supports master stack - I just called it stack main. I was in fact inspired by river: https://github.com/riverwm/river. River is really promising but is still in very early development. Sway on the other hand has been around for a long time and I, for now, prefer that stability.

In my very specific case, I'd probably start by taking a look at how animations were previously implemented in river, and then I'd pay careful attention to that transform matrix at the end. I'm not super crazy about the implementation using timers to drive it (versus interpolating where the transform should be across a deadline), but I guess they were going for smoothness.

riverwm wayland compositor