best_username_ever

joined 7 months ago
sorted by: new top controversial old
Data from deleted GitHub repos may not really be deleted in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 4 points 3 months ago (1 children)

How can such a wrong answer get so many points? Clones and forge forks are unrelated. First, GitHub or GitLab cannot and could not link clones together without analyzing the remotes of each clone.

FFS it's a tech community...

Data from deleted GitHub repos may not really be deleted in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 7 points 3 months ago (5 children)

Forks do not exist in git. It's a GitHub feature, and a massive blunder at the same time.

Is there anyone who can help me mod and style a community? Or do I need to do it on my own? in c/nostupidquestions@lemmy.world
Is there anyone who can help me mod and style a community? Or do I need to do it on my own? in c/nostupidquestions@lemmy.world
[–] best_username_ever@sh.itjust.works 1 points 3 months ago

Yeah. They only read textbooks to quiet kids, they do not have unpaid overtime at home for grading tests, and earn a million dollars every month. Lazy bastards.

Reddit blocking all major search engines, except Google in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 32 points 3 months ago (8 children)

Is there a downside? I’m confused.

We finally know what caused the global tech outage - and how much it cost in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 4 points 3 months ago

I don’t understand the downvotes. You’re right on all points. If the task is too big, it can take years from testing another solution to using it for real.

Why do so many people use NGINX? in c/selfhosted@lemmy.world
[–] best_username_ever@sh.itjust.works 23 points 3 months ago (1 children)

Back when Nginx started, Apache was the only alternative and a big pain in the ass. That’s how it became popular.

OpenAI: "We think there is room to make search much better than it is today. We are launching a new prototype called SearchGPT" in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 13 points 3 months ago (1 children)

That’s boring. Altman wants to save the world whatever that means, not solve the shitty problems that poor people have.

I spoke with Llama 3.1-405B in c/technology@lemmy.world
[–] best_username_ever@sh.itjust.works 16 points 3 months ago* (last edited 3 months ago)
  • Medium sucks
  • Clickbait
  • After reading a few pages, what is the point of this article? There are hundreds of pages of conversation, WTF?
Tesla accelerates plans for cheaper electric vehicles, but not the $25,000 EV in c/evs@lemmy.world
[–] best_username_ever@sh.itjust.works 11 points 3 months ago (1 children)

Cheap and expensive at the same time. I don’t think I’ve ever seen such a product.

Is it a crime to share my jellyfin library with only one friend of mine? in c/piracy@lemmy.dbzer0.com
[–] best_username_ever@sh.itjust.works 30 points 3 months ago

Having a “library” is already a crime in some countries so…

I think thread deletion is problematic and needs some consideration and changes in c/fediverse@lemmy.world
[–] best_username_ever@sh.itjust.works 10 points 3 months ago (1 children)

I even gave an example

You haven’t given an example. Where are your sources?

12
Is there a "markup language" to describe a debugging session? (sh.itjust.works)
 

I want to document my debugging sessions in a text file but I don't know if anyone did this before.

I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.

// When you click on the button
# [click button]
- A::f()
// - ... other method calls, don't document if you don't need to

# A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)

// <Class> is a fake template thing to show the possible types of an object
# <SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call
  v/=> SubStuffA::g()
  v/=> SubStuffB::g()

# SubStuffA::g()

# SubStuffB::g()

# Stuff::h(...)

I document methods in the order of appearance in the code.

If you have any good idea about a reliable way to document a list of function calls, I'm interested!

view more: next ›