afaik, fedora is the testing distro for RHEL. I also felt this way, when a new gnome version released much earlier than for Arch and it had an obvious bug that could be catched with little testing.
And many issues I found in Fedora's bug tracker was auto closed by the new release. Which is quite frequent. Reviewing the bugs is not that frequent.
That's also why I always use dev containers
You may see shorts in lemmy in the near future because of that.
Slack calls disabled for firefox users, but if you change the user agent to chrome it works...
I lost my Canon EOS M50 II. Basically my whole camera gear just spin off from a 3km tall mountain in Austria because I forgot to close my bag. I know...
After a month of mourning, I started to look again to the market, but It's hard to swallow. Prices are manually kept high. Affiliate links everywhere. Old gear is not cheaper. An average smartphone can record 4k video with in-body stabilization, but if you want it in a camera then the body will cost you a fortune. Lenses are not compatible with every body, technology exists for good lenses but they keep producing trash. And I have to buy the trash because of my price range.
Moreover, firmwares are proprietary. Smartphone sync apps are limited and proprietary (As a developer it's quite annoying, that they don't even let me fix their issues.) The raw format is only very rarely DNG but mostly proprietary.
I could list the injustices in the world we live in all they long.
But, I miss the image quality, and I need another one. What do you think, which brand is the least like above? What do you suggest for traveling?
(The photo has been made with my phone shortly after losing my camera, sitting there sadly, but somehow the land is so quite and calming.)
well, yes, but for e.g. I wrote a software piece that happened to be only a hotkey daemon. And I could write it with X. Now, hotkey daemons are no longer a separate thing unless the compositor exposes a grab API. Which never going to be in Wayland protocol, because they consider this client server architecture a problem.
There's hope. Thanks for letting me know.
Now instead of having Wayland covering everything, applications try to cover every desktops. In the good old times, it worked everywhere.
Why does flameshot need to handle different wayland desktops separately? Because simply the protocol doesn't do it's job. It doesn't cover everything. It's indeed not ready.
I think it kills the community. Making a Wayland window manager is so much harder to do than an X one. This monolithic solution solves the problems of Gnome, and KDE developers but less people want to be involved in windowing systems. I'm just being sad for X11, because, although it had nonsense features, it made linux desktop applications compatible with every desktop and we had huge variety of wms, compositors, desktop environments. Personally I'm still on X because of bspwm, but eventually there will be wayland-only features which will slowly kill X.
there are products that I would buy if I would know they exist but I don't because they don't have enough money to do advertisment. It's inherently an unfair competition. The only ads that I would like to see is a tematical search for all of the buyable products and services.
--- that might potentially sell
+++ that is pushed with money
If they want to fight hard, they just add the ads into the stream.
I liked this discussion. However, I think both of you have different axioms. It's a pro-socialism vs pro-capitalism debate.
In capitalism, we need innovation to create new value. Or you can pollute water to sell water bottles which will have value now. It's up to citizens to decide what to restrict that was publicly available or what to innovate.
In socialism, the innovation is only happening where it needs to happen carefully planned and funded by the government.
I'm rather socialist, so I'd defend it:
Having a software with inability to modify is injustice, It's the same as polluting a water to sell it. Even if we need to pollute the water to sell it, it doesn't justify pollution.
You can't make a law for everything evil that corporations do. Social democracy is flawed inherently. We need direct decision power of people in those firms. Never gonna happen though.
I recently installed Nix alongside with Arch. I feel the same. After years of using Arch I spent two days to get everything configured the same as in my Arch, and I haven't finished it yet.
Don't buy a Mac. That's more limiting than a Windows. But yeah install linux.
Hey, I'm not a fan of advertising libraries, but otherwise, nobody will know them. I think this package is really spot on and solves many issues with current web technologies.
I'd like to continue this project. If you found it interesting please give some feedback.
github.com/fxdave/cuple intro: The Missing Type-Safety for Full-Stack
I have a plugin trait that includes some heavy types that would be almost impossible to wrap into a single API. It looks like this:
rust pub struct PluginContext<'a> { pub query: &'a mut String, pub gl_window: &'a GlutinWindowContext, flow: PluginFlowControl, pub egui_ctx: &'a Context, disable_cursor: bool, error: Option<String>, } pub trait Plugin { fn configure(&mut self, builder: ConfigBuilder) -> Result<ConfigBuilder, ConfigError> { Ok(builder) } fn search(&mut self, ui: &mut Ui, ctx: &mut PluginContext<'_>); fn before_search(&mut self, _ctx: &mut PluginContext<'_>) {} }
Here is what I considered:
- Keeping all plugins in-repo. This is what I do now, however I'd like to make a plugin that would just pollute the repository. So I need another option that would keep the plugins' freedom as it is right now, but with the possibility to move the plugin out to a separate repository.
- I tried to look into dynamic loading, and since rust doesn't have a stable ABI, I'm okay with restricting the rust versions for the plugin ecosystem. However, I don't think it's possible to compile this complex API into a dynamic lib and load it safely.
- I'm also ok with recompiling the app every time I need a new plugin, but I would like to load these plugins automatically, so I don't want to change the code every time I need a new plugin. For example, I imagine loading all plugins from a folder. Unfortunately, I didn't find an easy solution for this neither. I think I will write a build macro that checks the
~/.config/myapp/pluginsand include all of them into the repo.
Do you have any better ideas, suggestions? Thanks in advance.
(For context, this the app I'm writing about: https://github.com/fxdave/vonal-rust)
Hey everyone,
Just wanted to share my recent experience with gaming on my laptop. While playing CS:GO was manageable, CS2 was a different story. My laptop kept hitting thermal limits, causing frustrating performance drops. So, I decided to do it myself and repaste it.
I wrote a simple script to monitor my temperatures and frequencies: thermalog script.
The results speak for themselves: thermalog results.
I wasn't even near to thermal limit even when I played in 2K instead of FHD.
I used Arctic MX-6. (I bought liquid metal also as a backup plan, but luckily I don't need it). I'm more than happy with the results.
My laptop is four years old, I highly recommend giving it a go if you're facing similar thermal issues.
Happy gaming!
We decided to test whether the car can handle long ranges by going to Austria next week. It's a large country with numerous places, so I want to ask your help. Have you ever been to there?
EDIT: Thanks the suggestions for everyone, they were really useful!