lemmeBe

joined 2 years ago
[–] [email protected] 2 points 1 week ago (1 children)

How do they compare?

[–] [email protected] 2 points 2 weeks ago

Same scenario as mine.

[–] [email protected] 2 points 1 month ago

How to pick a pod? Based on what criteria? Is there a better or a worse pod, similar to pros and cons of different Lemmy instances?

[–] [email protected] 6 points 1 month ago (6 children)

What do you use instead of Mullvad now?

[–] [email protected] 47 points 1 month ago* (last edited 1 month ago) (5 children)

~~Again~~ Another elitist Linuxer. 🙄

The guy has over 100 million subscribers on YT, and has been hugely popular for 15 years.

Endorsement from such figures could get us closer to the mythical year of Linux. Why shun it...

[–] [email protected] 9 points 1 month ago

Try JetBrains Mono.

[–] [email protected] 1 points 1 month ago

Come as you are.

[–] [email protected] 2 points 1 month ago* (last edited 1 month ago)

Had similar experience with snapshots. Restore to the last working version just to find the same issue that's been bothering me.

Then went back to the classic approach with 👻 images and Rescuezilla.

With NVME drive, it takes 7min to backup 60Gb, and 3min to restore it.

[–] [email protected] 3 points 1 month ago

The moment I saw "Rad", first association was RadRacer. 😄

[–] [email protected] 2 points 1 month ago

Yeah, they'll do that... 😆

[–] [email protected] 14 points 1 month ago

Maybe we will, maybe we won't, but at least it's tech news for a change. 😄

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

view more: next ›