We want to make sure it's not being written in Electron
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.
Readit Newstanaypingalkar commented on Revolt: Open-source alternative to Discord revolt.chat/... · Posted by u/adamnemecek
> the build times are pretty tolerable for what it's providing.
I think this is probably right, and I think just about everyone "tolerates" the build times (that is, I see very few people stop developing in rust because of the build times).
But when, for example, I run `rustup update` to get a new nightly compiler and have to re-compile everything, it's annoying to have to wait 20 minutes. I'll tolerate it, and if a magic wand could make it instantaneous I would love that. But it's still annoying.
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. :(
As a side note, looking at this block of code, the syntax is just so ugly and overcrowded. I don't get how a relatively new language ended up looking so messy so fast; it's like no one cared about readability.
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.
Deleted Comment
tanaypingalkar commented on The case for continuous documentation virtuallifestyle.nl/2021/... · Posted by u/morchen
I'm adamant that the documentation for a project should live in the same repository as the code itself. This is crucial for a number of reasons:
1. If the docs are in the same repo, a commit that changes the code can update the relevant documentation (in addition to the tests) as part of the same unit of work
2. This means it can be enforced during code review: if a developer forgets to update the docs they can be reminded before they land their PR
3. This also provides a version history for the documentation which is synchronized with the code history. This is really useful when looking at history and trying to figure out what changed when.
4. This also works great with branches, PRs and releases. New features can have their documentation developed alongside the code in a branch, which makes it easier to understand a proposed change. If your software is deployed in multiple places as multiple versions (or even just staging vs production) you have a way to view the correct documentation for each individual deployment.
5. Added together, all of this builds trust. A common problem I've seen with internal documentation is that no-one trusts it to be up-to-date. Making it part of the regular code development lifecycle can fix this.
6. If you do this, you can write automated tests that enforce aspects of your documentation! I call these documentation unit tests, and wrote about them here: https://simonwillison.net/2018/Jul/28/documentation-unit-tes... - even something as simple as a test that fails if a new API endpoint isn't mentioned in a markdown file using simple string matching can ensure no-one forgets about the docs when they add a new feature.
Is there any lib/way that automatically generate doc for api/endpoint. I think it is possible to create such generator for graphql api.
tanaypingalkar commented on Microsoft looks ready to launch Windows 11 theverge.com/2021/6/3/224... · Posted by u/throwaway888abc
Windows 11 will r.i.p like windows 10x maybe.
tanaypingalkar commented on The right tag for the job: why you should use semantic HTML localghost.dev/2021/06/th... · Posted by u/tmfi
If the browser would make the semantic elements actually look good out of the box a lot of developers would use them by default.
You can reset your css
Nice tool it will be more nicer if it have graphql.