… the only language where 90% of the world’s memory safety vulnerabilities have occurred in the last 50 years
Yeah… That’s a shit post alright.
I’m not a C developer myself, but that’s just a low blow. Also, uncited ;).
… the only language where 90% of the world’s memory safety vulnerabilities have occurred in the last 50 years
Yeah… That’s a shit post alright.
I’m not a C developer myself, but that’s just a low blow. Also, uncited ;).
I’m going to try to help explain this, but i’ll be honest it feels like you’re coming from a place of frustration. I’m sorry about that, take a break :)
(I’m not a language expert, but here goes)
var test int < bruh what? :=
These are the two forms of variable declaration and the second one is a declaration and initialization short hand. I most commonly use :=
. For instance:
foo := 1 // it's an int!
var bar uint16 // variable will be assigned the zero value for unit16 which is unsurprisingly, 0.
func(u User) hi () { … } Where is the return type and why calling this fct doesnt require passing the u parameter but rather u.hi().
This has no return type because it returns no values. It does not require passing u
. It’s a method on the User type, specifically u User
is a method receiver. You might think of this akin to self
or this
variable in other languages. By convention it is a singke character of the type’s name.
If that function returned a value it might look like:
func(u User) hi() string {
return "hi!"
}
map := map[string] int {} < wtf
This is confusing because of how it’s written. But the intent is to have a map (aka dictionary or hashmap) with string
keys and int
values. In your example it’s initializd to have no entries, the {}
. Let me rewrite this a different way:
ages := map[string]int{
"Alice": 38,
"Bob": 37,
}
Hope this helps. In all honesty, Go’s language is very simple and actually rather clear. There’s definitely some funny bits, but these aren’t it. Take a break, come back to it later. It’s hard to learn if you are frustrated.
I also recommend doing the Tour of Go here. My engineers who found Go intimidating found it very accessible and helped them get through the learning code (as there is with any language).
Good luck (I’m on mobile and didn’t check my syntax, hopefully my code works 😎)
If you look deeper at the recorded PR commit, comments, and package description it’s clearly straight up mean-spirited.
Zenos. Zenos. Zenos.
I cannot update this enough. Just completed the Endbringer MSQ, and holy hell. His entire character, premise, every stupid monologue, every cutscene, his entire arc. Banal and awful. Felt like some 6yo on DBZ crack wrote his entire plotline.
I just searched for any reference of Zenos and I’m glad you posted this. His existence serves zero purpose in the story. Zero.
That is all, thank you!
Aww, I’m sorry! I meant it with love.
Being someone who moved to Wisconsin, the number of bars everywhere is a bit surprising when ya start noticing it.
They probably forgot to sample Wisconsin.
My issue with FF’s auto update is that the behavior is how painfully the auto-update works with multiple profiles.
I’ll have one window (well three) open for some (measurable in days) time.
I have to shut it (all?) down to get it working again.
I don’t know how Chrome handles this so I cannot compare. TBH still worth using FF over that adware!
For sure! I was just thinking of a species that’ll outlive humanity. :D
I thought roach myself.
Yeeap. My FreeBSD box has such pain with 'em. Because unfortunately *bsd is not in Python’s precompiled wheels. So one is almost building from the source.
Now every time I pip install something there’s a high likelihood I’m going to end up having to install the rust tool chain and burn so much time on building libraries. I get why the project made the switch, but man does it hurt being downstream of it.
Every time I see a project decide to use rust I groan knowing my build/packaging time is about to skyrocket. Case in point, the Python cryptography project.
And given cryptography’s importance in the Python ecosystem what used to be an easy pip install of a package now almost always going to include is an enormous and horribly slow rust build environment.
Seeing a rust libraryjust makes me sad now 😭
My gods. I think this just gave me flashbacks to this week.
I was recently battling node’s import/require shenanigans trying to figure out how to import a typescript module in my basic program. I feel this so hard.
I walked away utterly hating the language and its ecosystem. Utterly defeated, I gave up.
My partner in the same size. NGL, it’s glorious.
Metamucil Bulk Fiber
All the generics are awful in taste or consistency (for instance not being as finely ground it seems). And weirdly in Kirkland Signature’s case, foamy.
Stupid expensive for what it is. But the effect is worth it.
Edit: sigh, autocorrect, you are the worst.
Omg, I laughed so hard. This one was quite good.
It’s a glorified autocorrect. Using it for anything else and expecting magic is an interesting idea. I’m not sure what folks are expecting there.
But I don’t ask it to explain things or generate algorithms willy nilly. I don’t expect or try to have it do something that’s not more than simply auto-completion.
I honestly like it, even if I strongly dislike the use of AI elsewhere. It’s working in this area for me.