Skip Navigation
Jump
Data from deleted GitHub repos may not really be deleted
  • 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...

    4
  • Jump
    Obsidian can't handle several thousand of notes
  • 200 MB modern application built on top of Chrome can’t handle a few files.

    Emacs from the 70/80s can handle a thousand files. Something is wrong with computers.

    39
  • Jump
    Vinyl records outsell CDs for the second year running
  • It’s fake nostalgia of an era they never experienced. Vinyls always sounded like shit but we had no comparison except the better sound of movie theaters, but you couldn’t have that at home.

    Then the audio CD appeared and it was like the second coming of Jesus. The sound was really a hundred times better than vinyls, even with the same set of amps and speakers.

    One day they’ll tell us that VHS on a small black and white TV is better than a 4K movie on a giant screen.

    3
  • Jump
    We finally know what caused the global tech outage - and how much it cost
  • 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.

    4
  • Jump
    I spoke with Llama 3.1-405B
    • Medium sucks
    • Clickbait
    • After reading a few pages, what is the point of this article? There are hundreds of pages of conversation, WTF?
    16
  • cross-posted from: https://sh.itjust.works/post/19440902

    > 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!

    1

    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!

    10