I set up Visual Studio Code to save files every second



is this

(A) Too much
(B) Too little
(C) Just enough
(D) I should use manual save instead

Chiroyce wrote:

I set up Visual Studio Code to save files every second

https://assets.scratch.mit.edu/get_image/.%2E/1d5cf15a54627d8205f7b4875384e8c5.png

is this

(A) Too much
(B) Too little
(C) Just enough
(D) I should use manual save instead

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

I have a feeling two milliseconds will wear out the SSD.
I use 2500 milliseconds in my VSCode installation.

A.

god286 wrote:

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

I have a feeling two milliseconds will wear out the SSD.
I use 2500 milliseconds in my VSCode installation.

That way, it'll save as soon as changes are made.

9pfs wrote:

god286 wrote:

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

I have a feeling two milliseconds will wear out the SSD.
I use 2500 milliseconds in my VSCode installation.

That way, it'll save as soon as changes are made.

If you are using a tool such as Tailwind JIT or SvelteKit (or anything that watches files) you will know that it will stress the script.

god286 wrote:

9pfs wrote:

god286 wrote:

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

I have a feeling two milliseconds will wear out the SSD.
I use 2500 milliseconds in my VSCode installation.

That way, it'll save as soon as changes are made.

If you are using a tool such as Tailwind JIT or SvelteKit (or anything that watches files) you will know that it will stress the script.

Good to know.

god286 wrote:

I have a feeling two milliseconds will wear out the SSD.

Yep that's wayy too much.E

dhuls wrote:

A.

What's the recommended time then?

Chiroyce wrote:

god286 wrote:

I have a feeling two milliseconds will wear out the SSD.

Yep that's wayy too much.E

dhuls wrote:

A.

What's the recommended time then?

100ms

9pfs wrote:

100ms

That will wear out the SSD.

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

Nano has auto save?

Chiroyce wrote:

9pfs wrote:

100ms

That will wear out the SSD.

9pfs wrote:

Go for 2 milliseconds. If that doesn't work, try nano. Much easier to save.

Nano has auto save?

No, but it doesn't let you close without saving.

Chiroyce wrote:

What's the recommended time then?

Maybr 5-10 seconds?

9pfs wrote:

No, but it doesn't let you close without saving.

VSCode also warns you when you close without saving.

god286 wrote:

9pfs wrote:

No, but it doesn't let you close without saving.

VSCode also warns you when you close without saving.

It does? Well, I use killall to close gui apps.

I have Autosave enabled for Visual Studio Code to whatever the default is and it works fine for me. I would definitely recommend having it enabled because I at least find it very annoying to have to save my program manually every time I want to run it.

Personally, I never auto save my coding. This is because I do a lot of work with github, and there have been several occasions where auto saves mess up my commits.

If you're used to your code always being saved, there isn't much of an issue

A

Some things would be annoying with auto-save, especially if you didn't make any changes. Like running a svelte dev server, as it would reload all the time while you were trying to test it. Or an Electron reload thingie, like what Ninetails has.

NFlex23 wrote:

(#18)
Some things would be annoying with auto-save, especially if you didn't make any changes. Like running a svelte dev server, as it would reload all the time while you were trying to test it. Or an Electron reload thingie, like what Ninetails has.

For me, actually I use 2500 seconds autosave when working with Svelte and other tools, works for me.

god286 wrote:

(#19)

NFlex23 wrote:

(#18)
Some things would be annoying with auto-save, especially if you didn't make any changes. Like running a svelte dev server, as it would reload all the time while you were trying to test it. Or an Electron reload thingie, like what Ninetails has.

For me, actually I use 2500 seconds autosave when working with Svelte and other tools, works for me.

Oh, maybe it doesn't reload the page if there are no visible changes. I didn't actually test it.