2,162 karma · joined August 14, 2020
It is going to be a huge 24 months for RISC-V. My biggest concern is that everybody will have already placed their bets before then.
Remember, many people feel that neither ODF or OOXML are sufficient and reach for things like LaTeX.
I think LibreOffice also supporting Markdown is a nice nod at simpler open formats.
Perhaps you have not dug into the problem deeply enough.
ODF is certainly better than OOXML at any rate.
Sorry, I responded to the wrong comment.
Also, it is essentially an ext2 filesystem as it does not support journaling.
We did a UI refresh at one point. It looked much nicer. People hated it. We had to hastily redesign it again and it looked far more like the original.
There is a certain amount of truth to that I think
I do not think anybody was “smarter”. There were smart and less smart people then and now.
But the “typical” practice changes. And that changes what you get. I think your “typical” programmer is more productive today in terms of what they can accomplish. But that work is going to be built at a higher level of abstraction and likely a lower level of run-time efficiency. As a percentage, fewer people understand or take into account the lower level details.
It is not just about new tech. After all, I can write all my code in RISC-V assembler. And I can manually allocate memory and manipulate pointers in C#. It is just not what people normally do these days.
The first thing you want to ensure is that you avoid unsafe in YOUR code. That is, after all, where you are going to create your bugs.
Ideally, there is no unsafe code in the crates you use. If there is, at least there are more eyes on that code to catch problems. You can inspect and debug that code, and others can do it for you. Others may battle test it and stress it far more than you will.
And at least the unsafe code is isolated to a few areas in the supporting libraries. Less to inspect. Less to debug. Fewer places to introduce memory related regressions.
It does not at all follow that, given an unsafe block, we may just have well used C++.
Also, I am pretty sure that SumatraPDF is available for Linux as well. I am not at a computer but I think it is in the AUR.
If you write software using GTK, Qt, or FLTK then you are writing Wayland software.
The majority of Linux desktops are Wayland at this point. Nobody writes software for them?
The Steamdeck uses gamescope which is Wayland. GNOME, COSMIC, Budgie, Niri, and Hyprland are not just Wayland but Wayland only. KDE will be Wayland only soon. Cinnamon is switching to Wayland. XFCE is writing a Wayland compositor.
What percentage of Linux desktop users are not using one of the above? 10 at most?
MAUI is Open Source but Microsoft does not provide a Linux back-end. This is a non-Microsoft effort to bring Linux support to MAUI.
I may be in warmer weather but I would say I probably charge 15 minutes to go 250 km or more. Given that the family also wants to stop to eat, go to the bathroom, or just get out for a bit, it mostly feels like we are stopping when we want to and not for much longer. Typically, stretches of driving are longer than 250 km. We can go over 400 km at a time (but rarely do).
To be fair though, we have great charging infrastructure. There is going to be fast charging in the next town pretty reliably.
At home, day to day, we charge at home and the car is basically magic. You drive as much as you like every day and never think about “fuel” at all. The thing just works. Going back to the non-EV SUV is daily “range anxiety” as it always seems like I am late for something and wondering if I have enough fuel to make it without having to stop.
Don’t get me wrong. Faster charging would be great and I am not saying we have never wanted to leave 10 minutes sooner from a charging station. But I have not found it anywhere near as bad as you are saying, even now.
North America imports cars in large quantities from every car making region in the world (that is not banned). What parts of the world sell high volumes of NA vehicles? They are not banned, just unwanted.
But already a majority of Linux desktop users have stopped using it. And it will be 90% in the next 2-3 years. GNOME, KDE, Budgie, and COSMIC are effectively Wayland only now and XFCE and Cinnamon will be Wayland native before then.
The GTK5 devs do not have to “kill off” X11. But it is not really worth their time either.
Keep using Xorg, or Xlibre, or Phoenix. It should keep working.
But don’t mind if the rest of us keep building on Wayland.
By the way, I use Niri, a very cool and absolutely non-corporate Wayland compositor. Not sure how that fits into your narrative.
Or build on River as this article suggests.