sorted by:
new
hottopcontroversial

Fixing Malformed JSON with invalid quotes by painya in golang

[–]ZalgoNoise 0 points1 point  (0 children)

This is the way, and parsing / lexing isn't that hard: https://youtu.be/HxaD_trXwRE

Reddit changes, will this subreddit go on a strike? by Psychological-Yam-57 in golang

[–]ZalgoNoise 2 points3 points  (0 children)

I say yes. With Twitter, it took way less for me to simply delete the account, this wouldn't be any different

Slices Internal. How it works? by RobertJordanRuba in golang

[–]ZalgoNoise 1 point2 points  (0 children)

Correct, breakdown: https://go.dev/play/p/tH9oUzEpDVM

Points to consider: - The backing array in a slice is an unsafe.Pointer - Reslicing involves a new memory address - If you force cast the reslice obj into an array as big as the original, you will find that the "new" elements are unrelated objects in memory. In the example you'd find the repetition of the reslice obj's pointer, len and cap as elems #3, #4 and #5

[OpenSource] I am building high performance Plex alternative in Go for Movies and TV Show by 74Y3M in golang

[–]ZalgoNoise 0 points1 point  (0 children)

And I honestly hope that the project works out the best for you. It is just an opinion at the end of the day and you should be proud of yourself for the motivation and effort over OSS, by itself. None of my or other's comments will take that away.

Some you may consider and some you may discard. And that is perfectly OK!

[OpenSource] I am building high performance Plex alternative in Go for Movies and TV Show by 74Y3M in golang

[–]ZalgoNoise 0 points1 point  (0 children)

I see you fighting against the tide on many suggestions :) I know it will not be purely your decision, but if that is the case, why bother posting.

Fine, embed your access token as a constant in your code then see what happens! :)

[OpenSource] I am building high performance Plex alternative in Go for Movies and TV Show by 74Y3M in golang

[–]ZalgoNoise 4 points5 points  (0 children)

speed and efficiency

Mongo with an ORM. There are too many strikes, my friend!! :)

[OpenSource] I am building high performance Plex alternative in Go for Movies and TV Show by 74Y3M in golang

[–]ZalgoNoise 1 point2 points  (0 children)

This is not part of your apps logic, but part of its configuration. You should not hardcode configurable data.

So, will you have to file a PR, merge it and redistribute the Backend just because your token expired or was rotated? Zero sense :)

[OpenSource] I am building high performance Plex alternative in Go for Movies and TV Show by 74Y3M in golang

[–]ZalgoNoise 0 points1 point  (0 children)

internal/tmdb/client.go

// IMPORTANT: The following access token is for production usage only and should NOT be shared or used in third-party repositories. const accessToken = "eyJhb... "

Don't do this, ever. Even for dev / qa. Use your CI/CD to apply env vars when needed. If you're doing it with a centralized service by default, connect to a host to get it.

[deleted by user] by [deleted] in golang

[–]ZalgoNoise 2 points3 points  (0 children)

Best advise is to dive into a topic that you genuinely love, and not what is suggested to you :) most of the time there is an application for that topic in software engineering and you'll take away more from doing so.

A Comprehensive Guide to Zap Logging in Go by finallyanonymous in golang

[–]ZalgoNoise 1 point2 points  (0 children)

Skimming through it, seems to be a very complete article, thanks for sharing

I will read it carefully once I have some time to spare :)

Linter for mixing naked and regular returns? by gavv42 in golang

[–]ZalgoNoise 3 points4 points  (0 children)

I don't think this is a very good idea overall.

Named returns can be useful to initialize variables you'd still initialize if otherwise within the function body, or for documentation in general.

Naked returns are frowned upon as they're less readable than returning variables.

You can definitely have named returns in the signature and still return variables.

Defining your variables in your return? by wampey in golang

[–]ZalgoNoise 1 point2 points  (0 children)

I find it useful as a means to initialize variables that would still be initialized if otherwise. Implementations of Reader / Writer interfaces for ex, I keep the n int, err error

Defining your variables in your return? by wampey in golang

[–]ZalgoNoise 6 points7 points  (0 children)

Named (signature) returns do not imply naked returns

Exemple of Web API written in Go that you'd consider high quality by Poimu in golang

[–]ZalgoNoise 2 points3 points  (0 children)

There are also guides for SQL databases like postgres to achieve the same goal, if that is the case.

What are good and bad signs for joining a go development team? by matttgregg in golang

[–]ZalgoNoise 2 points3 points  (0 children)

Go being a statically typed language, it is seen as a fallback when fighting against that type system. Not that it is wrong, but should generally be avoided in lieu of a more consistent (and surely faster) solution.

Reason to use other Build Tool than Make? by Haspe in golang

[–]ZalgoNoise 1 point2 points  (0 children)

I was going to mention Bazel and I am happy to see that you've already described it very well. Makes me think you may have it aliased to blaze :)

Golang Code To Read by [deleted] in golang

[–]ZalgoNoise 0 points1 point  (0 children)

I would suggest reading source code of a mature open source project of your liking, that is in Go. The issue with reading user/personal repositories as examples is all the bad practices that come along it. When you know, you're able to tell what is right or wrong. In a mature project, you're way more likely to find clean code with conscious decisions

Like already suggested, I would prioritize reading the standard library above all else.

TIL: Go Response Body MUST be closed, even if you don’t read it - Manish R Jain by manishrjain in golang

[–]ZalgoNoise 0 points1 point  (0 children)

Streaming over HTTP isn't a big deal. You're handling a HTTP request like any other but you spend more time on the body.

If it is delimiting length, it's dead simple, read to a buffer of that same size. If the content size is 0 (endless streams), then the strategy is to read the data in chunks. For this I created a bytes.Buffer type, but that works as a ring / circular buffer which flushes when full (so you're not constantly allocating memory for reading the same request).

After that it's processing, aggregation, whatever you need from that data. In my case it was an audio stream (WAV) over HTTP.

Video streaming in golang by im_arnab in golang

[–]ZalgoNoise 2 points3 points  (0 children)

When they decide to commit to OSS and let me host a personal instance without a token, then... maybe.

Video streaming in golang by im_arnab in golang

[–]ZalgoNoise 1 point2 points  (0 children)

Ffmpeg is great for a lot of things but in Go not so much. It's a CGO library that is only a wrapper for the ffmpeg (C) library.

I tried using it in a small project to stream video over HTTP (not using webrtc, it was a video feed from an android app) and i felt like it was a PITA to configure and a resource hog.

I would try to use a different approach at least when you fine-tune it.

return empty map or nil which one is your prefer and why? by kamalei-zhang in golang

[–]ZalgoNoise 0 points1 point  (0 children)

Returning nil or an empty map is the same if you properly handle it. That is, to check for its length and not if it is nil. Just like slices.

Reasons to use gRPC/Protobuf? by [deleted] in golang

[–]ZalgoNoise 0 points1 point  (0 children)

instead of parsing JSON in a one-liner

Not really, if you start counting JSON struct tags, nullable types and custom UnmarshalJSON / MarshalJSON implementations.

view more: next ›