They can use tauri. A new fresh tech and it is efficient also. They should consider it as the title of this post says revolt is written in rust. So they can try more rusty ways making revolt.

I have a low spec machine but i still patiently wait for 200 crates to download.Because it is cached. But the most annoying thing is that when I am using any frameworks like gui and game. The second compilation also takes a minute to start the app. I have ended up with them. :(

I think rust syntax is more readable and self explains. Having syntax more minimal, more use of symbols, spaces and tab make them beautiful but they are really hard to get if it is written by someone else. I personally noticed it's more easy understand other rust project than other langs project.

Is there any lib/way that automatically generate doc for api/endpoint. I think it is possible to create such generator for graphql api.

You can checkout Swagger and OpenAPI, there are libraries to annotate the endpoints in the code and then generate interactive docs out of that.

Windows 11 will r.i.p like windows 10x maybe.

You can reset your css

For some elements, yes. Many others have certain attributes that are completely unstylable, a lot of browser-specific attributes and selectors (not just prefixed attributes but also whole pseudoclasses), or both.

Nice tool it will be more nicer if it have graphql.

Hey, glad you asked. GraphQL queries are actually just POST requests to a GraphQL endpoint. Although the experience is not something I'm proud of, it's indeed possible to hit GraphQL queries in the following manner:

    POST https://api.github.com/graphql
    Content-Type: application/json
    Authorization: Bearer github-personal-api-token

    ={query: `
    {
      repository(owner: "appsmithorg", name: "appsmith") {
        releases(orderBy: {field: CREATED_AT, direction: DESC}, first: 20) {
          nodes {
            tagName
            name
            url
            descriptionHtml: descriptionHTML
            createdAt
            publishedAt
            isDraft
            isPrerelease
          }
          totalCount
        }
      }
    }
    `}

Know more about this way of running queries at http://localhost:3045/docs/guides/templating/.

its(not, that, hard)

but why clojure have this, reason? i am not criticizing it but i just want to know why clojure take this decision.

The syntax becomes small, predictable and, crucially, is in itself a data structure. This means that everything composes in the same way, without special cases, and it lends itself well to meta programming when necessary.

isnt it why clojure is called clojure I guess. That the reader can take closure look of there code.

True, you cannot do that in useEffect, it will throw you error. And probably your linter will tell you. You can't even use your own or third party hooks in side useEffect. This also throw error I don't know why?

Because you could be nesting hooks, which would bring all sorts of weird behavior.

Why you have concerns with native dependencies, it is just a transpiler and a dev dependencies. How it affect your project?

It affects me and other people working on it. I have to make sure the systems running the dependencies have an appropriate Python and C(++) toolchain installed. If they use Node bindings, they will probably need to be updated for newer versions of Node.

When I come back to the project after some time, the first thing I need to do is update dependencies. I often had colleagues on whose devices some dependency would just refuse to compile for one reason or another.

Sure, this isn't the greatest problem in the Node ecosystem right now, but it's painful enough that I would rather not deal with it.