… 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 😎)
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!
Okay, so I’m not the only one that has found this a problem. The first few times I didn’t realize it. But it started dawning on me, it’s really quite bad at finding local businesses.
Quite literally my first thought. Great, but I can’t issue certs against that.
One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.
To folks recommending a private CA, that’s a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that’s the most persnickety, guests, where it’d be downright rude!
Being able to issue public certs is easily is great! I don’t use .local much because if it’s worth naming, it’s worth securing.