the JPEG-XL team at Google is teaming up with Firefox to make browsing experience safer and smoother.

why should you care? they're replacing the heavy decoder (100k+ lines of C++) with a lighter one built in Rust. this means faster load times and a more secure experience for all image-heavy sites (especially if you're like me who spends time on image-heavy sites). less bloat, more speed—it's a win a win! hope it gets shipped

#JPEGXL
@Mi_Ra_Ch

make nested conditionals one-dimensional! use early returns from a function rather than if/else chains. this is essential not only in the aspect of Go, but also in any language.

take a look at the following code snippet:

```
func isValidPassword(password string) bool {
isValid := true
if len(password) < 8 {
isValid = false
} else {
if !containsUppercase(password) {
isValid = false
} else {
if !containsLowercase(password) {
isValid = false
} else {
if !containsNumber(password) {
isValid = false
}
}
}
}
return isValid
}

func containsUppercase(str string) bool {
// ... implementation ...
}

func containsLowercase(str string) bool {
// ... implementation ...
}

func containsNumber(str string) bool {
// ... implementation ...
}
```

the above code adds cognitive load for someone who's reading ur code (the number of entities they need to think about is a lot, so they might be lost in ur code).

but take a look at the more idiomatic approach to the code:

```
func isValidPassword(password string) bool {
if len(password) < 8 {
return false
}
if !containsUppercase(password) {
return false
}
if !containsLowercase(password) {
return false
}
if !containsNumber(password) {
return false
}
return true
}

func containsUppercase(str string) bool {
// ... implementation ...
}

func containsLowercase(str string) bool {
// ... implementation ...
}

func containsNumber(str string) bool {
// ... implementation ...
}
```

it uses early returns (guard clauses) and provide a linear approach to logic trees

#tips #code
@Mi_Ra_Ch

the bandwidth usage literally sky-rocketed ? glad that it turned out to be useful for people

here's the full version of the song btw ? AI song artists be rocking

have a blessed day y'all

some contributions require a conventional commit messages to help maintain a clear and organized commit history. some of them defined by Conventional Commits, and i found useful:

- feat: Introduces a new feature to the application.

- fix: Patches a bug or addresses an issue in the code.

- chore: categorizes changes that do not directly affect the application's functionality or fix bugs

- docs: Documentation-only changes that do not affect the code.

- style: Changes that do not affect the meaning of the code, such as formatting, whitespace, or missing semicolons.

- refactor: Code changes that neither fix a bug nor add a feature, focusing on improving the code structure.

- perf: Changes that improve performance, making the application faster or more efficient.

- test: Adds missing tests or corrects existing tests to ensure code quality.

- build: Changes that affect the build system or external dependencies (e.g., gulp, npm).

- ci: Changes related to continuous integration configuration files and scripts.

- revert: Reverts a previous commit, indicating that a change is being undone.

#tips #git

I take calculated risks but i am bad at math ?