[-] [email protected] 1 points 1 week ago

Just a little. Big corporations ruin the working class just to eat more profit. I wish they had received less love.

[-] [email protected] 1 points 1 week ago

I wouldn't use windows either

[-] [email protected] 1 points 1 week ago

By the way, I am an apple hater because I tried apple after years of using Linux and it was a true mess. Here's a story: I had to make an app building CICD pipeline and guess what? We had to run a macbook as a server because they fucking cannot share at least a VM for building. A CLI command brought up a GUI confirmation. How should I automate something that brings up a GUI. Garbage. Package management is horrible. Command line utilities was outdated. Case insensitive filesystem. Then Ruby...

And it's not enough that they are shit, but they are actively holding back innovation. They held back PWAs for example. And they shit on open-source. They are the definition of vendor lock-in.

They look good though.

[-] [email protected] 1 points 1 week ago

It works between android and any linux distro through kde connect. It let's me do more than just clipboard sharing. e.g.: I could remote control my laser engraver through it.

[-] [email protected] 4 points 2 weeks ago* (last edited 2 weeks ago)

Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:

  • The Request and Response types are auto-inferred from the endpoint you write
  • Because the types are in Typescript you don't need to generate a client, you just simply use it with @cuple/client and get instant feedback.
  • You don't have to learn another language. It's just typescript.

Practically it means less boilerplate and it let's you focus on the feature you write. Cuple is also not a query language, you get what the server sends you, it's more likely a type-safe FFI binding. With Cuple you can build a REST API, or anything similar to that with HTTP method, header, path, query, body, and you can use it type-safely.

18
submitted 2 weeks ago by [email protected] to c/[email protected]

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

[-] [email protected] 2 points 4 weeks ago
271
submitted 1 month ago by [email protected] to c/[email protected]
[-] [email protected] 4 points 2 months ago

I deleted /lib64/ld-linux-x86-64.so.

I did it because valgrind had a problem with it. I thought I can fix it with reinstalling the package. I tried to lookup which package is it from, but the command I used was wrong and I didn't get any result. So I thought, what if I created it, maybe I just forgot it.

the moment I deleted it everything stopped working. It was fixable only from a pendrive.

[-] [email protected] 7 points 2 months ago

That's fair. Typescript has to cook with the existing js ecosystem.

[-] [email protected] 2 points 2 months ago

there won't be two pointers, but multiple devices are supported

[-] [email protected] 3 points 2 months ago

I would imagine it as lemmy. It would be a free, ethical software which is indirectly funded by the government. Everybody uses facebook so that's a good reason to turn it into a public property. We could make it without anti-features. Made for people, not for profit.

1
submitted 3 months ago by [email protected] to c/[email protected]

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)

145
submitted 3 months ago by [email protected] to c/[email protected]

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!

3
submitted 7 months ago by [email protected] to c/[email protected]

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.

view more: next ›

fxdave

joined 1 year ago