Over the years, although a tremendously valuable tool, IntelliJ IDEA started to feel slowed down, even on these latest M1 Pro machines. It’s become frustrating. I disabled as many plugins as not needed. However, it’s still not sufficient. I have discovered that you can improve the performance by switching IDEA to the latest JDK. JetBrains has its runtime with its patches for HiDPI supports, performance improvements, and bugfixes for running the IntelliJ family more smoothly.

My 8+ Years of Developing and Maintaining My Own Engine

Errors are a core part of almost every programming language, and how we handle them is a critical part of software development. One of the things that I really enjoy about programming in Go is the implementation of errors and how they are treated: Effective without having unnecessary complexity. This blog post will dive into what errors are and how they can be wrapped (and unwrapped).

When Go code propagates an error, the following pattern is very popular:
fmt.Errorf("failed to find a parking slot: %w", err) // Or fmt.Errorf("could not call mom: %w", err) These “could not”, “failed to”, “unable to” make sense when my mind is in the local context of the function, method or package. But, in most of the cases I have to deal with, it makes the resulting log message overloaded with informational garbage:
unable to ask about the cat: failed to call mom: failed to do request: Get https://: context canceled While discussing this issue with a colleague, we came up with the following “better” strategy:
only the logger should express its attitude to the facts, using words “error”, “failed”, etc the business code must operate only with facts, e.g. “call mom”.  err := CallMom(number) if err != nil { return fmt.Errorf("call mom (tel %s): %w", number, err) } This renders as following to the application logs:
error: ask about cat: call mom (tel 123): make request: Get https://: context canceled For a long…

technology blog about ruby, scala, java, golang, software engineering and programming in general

Contribute to notnil/chesscode development by creating an account on GitHub.

Ebiten is an open source game library for the Go programming language. Ebiten's simple API allows you to quickly and easily develop 2D games that can be deployed across multiple platforms.

From the "Go Time" podcast. Listen 👉 https://gotime.fm/209

Subscribe for more! 👇

Apple: https://gotime.fm/apple
Spotify: https://gotime.fm/spotify
Android: https://gotime.fm/android
Overcast: https://gotime.fm/overcast
Email: https://gotime.fm/email
Twitter: https://twitter.com/gotimefm

#golang #software #programming #podcast #a11y

GraphQL is a query language for HTTP APIs, providing a statically-typed interface to conveniently represent today's complex data hierarchies.

clickhouse client (wip). Contribute to go-faster/ch development by creating an account on GitHub.

Go is an open source programming language that makes it easy to build simple, reliable, and efficient software.

If you write a bug management system, with this PeriodLimit you can limit each tester can only assign one bug to you per day. :P

Contribute to iskaa02/qalam development by creating an account on GitHub.

Найти значительное узкое место в производительности стандартной библиотеки или зрелого приложения — это редкость.
Я был удивлён, когда в top10 списке CPU-профиля hugo при сборке digitalgov.gov на...

Go is an open source programming language that makes it easy to build simple, reliable, and efficient software.

Audit logs are very useful for retroactive analysis following a security incident, but what if they could also be used to proactively alert before a security incident occurs?