demi56

6 ms·

1.
by demi56 2y ago
> Sorry, but no - putting the burden on the developer to detect whether they are running in a container or not and then determine and adjust to cgroup settings is far too high an encumbrance on the service developer. Because there’s no o
2.
by demi56 2y ago
> ...includes support for a soft memory limit. This memory limit includes the Go heap and all other memory managed by the runtime, and excludes external memory sources such as mappings of the binary itself, memory managed in other langua
3.
by demi56 2y ago
> As an example, the Go runtime does not honor container resource limits That’s no longer true for Go 1.19+
4.
by demi56 2y ago
I would say the leaders(could be the creators) of the language plays the most important role in its infancy the decisions they make defines what decisions the community are gonna make and the was what Go made right, Java been a business ori
5.
by demi56 2y ago
But you see nobody really wants to be “different” if there are 100 people and the first 90 went right the probability of the remaining 10 going right will be higher. Java was designed to be business oriented and I think this is why Go and J
6.
by demi56 2y ago
So the community influences the language, not the language that influence the community that explains everything
7.
by demi56 2y ago
Yeah, some dev usually don’t put safe guards especially when the user input is directly linked to file operations
8.
by demi56 2y ago
Oh, the community is the reflection on how the language is being maintained
9.
by demi56 2y ago
Does shell scripting really need to go hand in hand with the language flexibility ?
10.
by demi56 2y ago
Systems Programming is kinda generic category and it ultimately depends on the individual to define what’s system programming and what’s not, is it performance, security or access to hardware
11.
by demi56 2y ago
Nobody enjoys writing Go but there’s a reason do code in Go and we can’t ignore it
12.
by demi56 2y ago
Basically the type system, most rust projects usually don’t come near “The advanced Reason there’s rust” and if they do need that there’re hardcore libraries for that, an ecosystem like that usually suffers from exhaustion cause no dev will
13.
by demi56 2y ago
You can’t just compare a library from another language, because they’re different, if all flag parsing library were inspired by Clap it’ll be a living nightmare for language that isn’t rust
14.
by demi56 2y ago
You don’t have to worry people have been saying this for more than a decade now and I see no action about it
15.
by demi56 2y ago
Not gonna lie am also getting 200% triggered whenever he states gVisor Syscall costs lol
16.
by demi56 2y ago
From my experience the reason $GOPATH has pkg, bin src directory was they wanted to limit spread of affecting the filesystem, I could zip my go directory put it in another computer and still works as good as before, I hated Python because i
17.
by demi56 2y ago
> and b) configured using a YAML-based DSL. Go devops HATE YAML-based DSL we just put it there cause there’s not alternatives, json ?, don’t wanna go there fortunately there’s CUE lang but moving all these project to accept cue isn’t tha
18.
by demi56 2y ago
Damn that’s a comeback that’s not complicated
19.
by demi56 2y ago
Dude you tried, there’s no need for 50000 word essay against a sentence
20.
by demi56 2y ago
Dude if the 70% don’t care they don’t care besides it’s open source
21.
by demi56 2y ago
> The huge volume of boilerplate makes the code harder to read, and annoying to write That may be superficially true but don’t forget our brain is structured to optimize every repetitive work or some boilerplates, we can basically use “s
22.
by demi56 2y ago
Sooo what’s the new 2025 way?
23.
by demi56 2y ago
You’re just complaining because the compiler isn’t complaining
24.
by demi56 2y ago
> I have nothing against Go, it's a tool that does its job fairly well and has very interesting qualities (fast compile time, self-contained binaries, decent performance out of the box), but the religious worship of “simplicity” is
25.
by demi56 3y ago
As a language that’s focused on backward compatibility than features oriented this is the best and optimal way to reduce some of Go’s loopholes. The problem of using developer tooling to solve the innate problems is that they lack awareness
26.
by demi56 3y ago
Basically proves his point, I hate JavaScript but am pretty sure my children is gonna write some code in JavaScript
27.
by demi56 3y ago
What makes you think that Google has active authority over Go development?,
28.
by demi56 3y ago
Or you could use a 3rd party error package that’s not a good excuse because the standard don’t have it as a priority
29.
by demi56 3y ago
Let python be python, let Go be Go, let Rust be Rust it has never worked well for any language trying to be like another language
30.
by demi56 3y ago
Blame that to glibc not the container

More ›