

In go you can call, debug.Stack()
at any time to get a stack trace. And it’s trivial to build error handling wrappers that can do this for on logging of an error.
In go you can call, debug.Stack()
at any time to get a stack trace. And it’s trivial to build error handling wrappers that can do this for on logging of an error.
I can only speak from personal experience but for me they jacked up the price significantly after year one and then sent my domain straight to auction after I decided not to pay. I respect that there are reseller-focused providers out there but they aren’t for me.
On the other hand, I’ve had nothing but quality service from namecheap for the best part of a decade.
Extremely cool. I feel like your natural next step is to do a conference talk about this tool using this tool, but don’t tell anyone for the first few slides.
They’re self-hosting Tangled on their server. The BlueSky part only relates to the protocol used for communication between it and other nodes. Definitely a confusing title though.
Namecheap. Avoid Dynadot.
I’m using memos in a docker container.
I like it because it has few features but they all work well. It’s great for taking quick notes or writing whole journal entries.
Awesome, love the design - something new for the homelab!
Sure buddy, have a good one.
No I’m not saying that, it seems you didn’t understand what I said at all. Let’s put that pin back in and not “derail” any more, eh?
All good, I did read the links you sent so I could see some of the “feedback” you received. It seems we both want Lemmy to be a nice place with constructive conversation so we’re very much on the same page there.
That said, I don’t think gatekeeping others with “you can only talk about the thread topic” is a healthy way to do that, so we diverge there.
I’m not going to stop doing it and, if you look around, you’ll see plenty of others doing it too, so I’m in good company there.
It’s nicer if we let conversation flow naturally and don’t set arbitrary constraints - the mods can do that via the community rules if they want to but, again, you won’t find many examples of that either.
Had to look this one up, very cool stuff. Terrible naming but I’ve come to expect that from Apache!
I don’t particularly like being lumped in with a bunch of jerks who’ve treated you badly tbh, but equally if you’re feeling harassed I’m happy to put a pin in this.
Derailing a conversation? That’s a bit dramatic… And now you are doing it by your own measure. I was just having a conversation, in a comment thread man. Chill out.
I was intrigued and thought it might spark a conversation… Why do you think that’s so wrong? What a massive overreaction.
Good chat
You … license your comments?
Too late, I switched to Floorp.
Because of privacy stuff? No. Because of repeated drama? Yes.
I don’t have time for this stuff. I don’t have time to track every minute twist of the knife that Google’s funding drives Mozilla to embark on.
I’m bored of using software and watching it go through “death by a thousand minor dramas”
So now I use a web browser that has a name so stupid I don’t even recommend it to other people. Brilliant.
Slow down satan
SELECT few FROM people WHERE gets_joke = 1
It will be where the error happened if you conventionally pass your errors to a logger that then prints the stack trace, which is virtually what Python et. al. are doing anyway.
Go is not a language I’m a huge fan of tbh, but this mild inconvenience is not one of the things I would criticise it for. What you’re describing w.r.t control flow for errors absolutely is though.