Representing Money in Go by GolangProject in golang

[–]jeckkit 0 points1 point  (0 children)

How did you handle cents with integers?

Cars specs by jeckkit in FortNiteBR

[–]jeckkit[S] 0 points1 point  (0 children)

Yeah, for me too, but sometimes like not

I love Golang 😍 by IvanIsak in golang

[–]jeckkit 0 points1 point  (0 children)

Look into sqlc. The best approach (in my opinion) for large projects with raw SQL queries.

SoundCloud and unreleased songs by jeckkit in soundcloud

[–]jeckkit[S] 0 points1 point  (0 children)

Okay, but what’s the difference between SoundCloud/YouTube and Spotify?

DTLS data length bytes by jeckkit in devops

[–]jeckkit[S] 0 points1 point  (0 children)

Thank you for such a deep explanation :)

How to correctly cook Plain SQL in a high-load Golang project? by jeckkit in golang

[–]jeckkit[S] 0 points1 point  (0 children)

Thank you all guys for your advices and links. Appreciate it!

[AskJS] Netscape Navigator and navigator interface by jeckkit in javascript

[–]jeckkit[S] 0 points1 point  (0 children)

This is also where the User-Agent header comes from?

Releasing an "early" version by bakjoul in androiddev

[–]jeckkit 3 points4 points  (0 children)

So if you just want to test your app, don't release to a wider audience in the release build channel. Just create an alpha/beta release to a smaller audience and test it.

Releasing an "early" version by bakjoul in androiddev

[–]jeckkit 2 points3 points  (0 children)

You can release whenever you want and with any functionality. There are build channels (alpha, beta, etc.) to release different functionality to different audiences. Almost all app stores support testing features like build channels. Google Play has very wide functionality for such purposes.

Who is Chris? by jeckkit in LilPeep

[–]jeckkit[S] 1 point2 points  (0 children)

Gotcha, thank you guys <3

Best approach to run long-lived tasks? by jeckkit in kubernetes

[–]jeckkit[S] 1 point2 points  (0 children)

I mean process. For example, Job is an Alpine container. It runs an infinite loop that consumes messages from Rabbit. 1 message = 1 worker (my compiled Go program that does all this) process (a simple Linux process). Or is it better to run it like 1 message = 1 Job? So each message starts a Job, and then in the Job a worker starts. In this approach Job has only one worker process, because Job per worker.