Anecdata: my workflow has been working on the same personal projects for months now with Codex. I cannot anymore finish my daily/weekly code with 4.8 anymore.
I was dividing my work between Codex and DeepSeek. Now I barely use DeepSeek, or never because Codex quota is enough after Sol
OMG, yes, please, get rid of all those composers, all that mess that people are doing. X11 is 40 years of battle testing. Wayland in 22 years (it already has 18) will be 100x worse than X11.
A Dockbar I am working on https://github.com/edumucelli/docking/ is a pain to build on Wayland. It already supports a lot of composers and even mutter/gnome with that Gnome shell extension, but at what cost ...
Not sure about the consensus, but during an entire week I have done every task on my workplace with both Opus 4.8 and GPT 5.5. GPT won hands down. I would even sometimes copy the plans and solutions (using different Git worktrees) from GPT and paste it on Opus and itself would say GPT plans were better. At that point I have migrated. Fable is not enabled in our workspace so I have not tried.
Claude lost my trust around February this year when the plan would say nonsensical things as "delete this method" that was clearly a key method on that part of the codebase.
For personal projects I am using Codex 20$ plan and when that is over I use DeepSeek which is insanely good for the cost.
A Linux dockbar with tons of applets and support for x11 and Wayland. Works on Gnome and KDE. I always wanted to write one as I have been involved with several open source ones, but it is a lot of time to go from scratch. I use it everyday, and I am enjoying it so much!
Been using Linux as sole OS for 25 years now. I will stick to X11 no problems, I am sure it will be just fine for my usage. When we thought Gnome 2 was gone, MATE fork appeared, X11 will be there for a long time. I am also going through the struggle of porting a software I maintain (github.com/edumucelli/docking) to Wayland and it is awful: "this compositor do this part, that one does that part, no compositor does this :shrug".
Very heavy indeed, people will confuse the durability that Temporal provide with all the other properties a distributed system needs. They will then think that Temporal will solve all their problems.
Tested today, most of it works using XWayland. Some applets won't like windows killer as it uses xkill, also some feature like window preview as Wayland do not give access to other screens, but also features like having the dock follow the mouse across different monitors.
I do not have a bar that I can put everything I want, so I created it, as many other developers have created a dock bar, just like MacOS has its own, etc, et.
To be honest, I am not sure, I will be working on those as the next big thing for Docking. I am uncertain of how much I can achieve on Wayland. Looking forward.
Yes, indeed. The next I will be working with is Wayland. Let's see how hard that will be. I am sure there will be applet that I will never be able to port like Window killer that users xkill, etc.
That is simply not true! Use of mechanical farming and fertilizers/pesticides can be beaten in productivity by permacultural practices. One example in France that has been followed by researches (and has produced several papers [1]) is the Ferme du Bec.
It is able to produce multiple times more and more qualitative (organic), for the same area than the national average mechanized production in France.
The pesticide industry and mega farmers want you to believe that what they are doing is to produce more food, but that does not stand the fact check of initiatives like permacultural ones.
It is laughable talk about "Don't Repeat Yourself principle" on a strongly biased towards Golang article. A language that took 13 years to add a simple method (Index) that helped the programmer to find an element in an array (slice). Before that you had to write a for loop every time you wanted something from an array. Talk about "DRY" ... That is everything but "simple" as described in the article.