• 0 Posts
  • 85 Comments
Joined 9 months ago
cake
Cake day: April 4th, 2024

help-circle
  • logging_stricttoBashHow does this code work?
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    it’s a bash community as long as bash is the right tool for the job. For text manipulation, not so much. In Python can also do some really stupid things. Then will get advice. They’ll say, just don't do that

    Which is what i’m doing here.

    just don't do that



  • Have read thru the Fossil web site. Fossil and git are nothing alike. Fossil is not Github in a box. That’s misleading.

    It’s ok to place the key/value pairs merkle tree into an sqllite database AND NOT change the philosophy away from what we are used to with git.

    Fossil makes me more sold on git. I want the PRs, i want to be able to rebase. I want to be able to fork projects away from it’s parent.

    Fossil needs to rewrite if it wants to attract git users. My main thing is portability of PRs and Issues. So when fork a project, the PRs and Issues are also forked. When the original author disappears would be nice to not have to rename the repo, while losing the PRs and Issues.


  • I read all 3.

    The critic has been tricked. He is naive nice person. And therein lies the rub. He is dwelling on rebutalling the bullshit not realizing it’s purpose is to distract away from real issues.

    He’s argued twice based on nostalgia rather than on legal merits.

    People may have legitimate reasons to want different terms in an open source license. The critic rejects this.

    If the critic has nothing to add to the conversation, he should go pound sand. The adults are capable of ripping systems apart and understand how to pieces fit back together and can customizing them without deviating from FOSS and OSD philosophy.

    Go with aGPLv3. FUTOs nonsense nonpoints don’t help in the least.

    Real issues like pay only in Monero to the maintainer without any KYC. Not in encumbered methods requiring our time and risk of not being able to receive the funds. No NPOs. No middlemen that take cut.

    Devs needs to unionize or form gangs. Society is currently telling us to get a job rather than maintain the packages world+dog relies upon. That’s malicious, suicidal, has real consequences, and thus should be our #1 political issue. And we have to change society’s focus by causing a rukcus, not submitting more resumes to create more web sites and smartphone apps or cloud services. Which is just purposefully pushing us towards a job creation program rather than a means to maintain world+dog’s tech base.

    There should be a systematic way for companies to pay towards those maintaining their tech stack. Lacking this, the companies can just say they are confused on how to go about paying devs. I can see their POV. That infrastructure needs to exist.

    None of these points, violate open source philosophy one bit.

    None of these points require yet another license. It’s more about what direction tech community has to take moving forward.












  • The chef was screwing a FOB white girl so he’s honorary American, not authentic Japanese.

    Gotta ask these things up front, “no pork” and “are you or have you ever screw an FOB”?

    Otherwise it’s not authentic Kobe beef from a Sannomiya station cow. JR not hanshin and definitely not Hankyu.

    (in a low suspicious voice cuz never discussed in loud voice) Or that local subway that goes who knows where