fxdave

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.)

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:

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:

1. 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.
2. 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.
3. 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/plugins and 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)

cross-posted from: https://lemmy.ml/post/7885746

I created a lib for designing cabinets. I'm not a woodworker, but I can design some for myself and I found this lib useful enough to share. So enjoy.

I created a lib for designing cabinets. I'm not a woodworker, but I can design some for myself and I found this lib useful enough to share. So enjoy.

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!