Skip Navigation

Posts
73
Comments
910
Joined
3 yr. ago

  • GNU Hurd

    Microkernels project. In development since 1990, with varying activity.

    After years of stagnation, development picked up again in 2015 and 2016, with four releases during these two years.[18] Since then, no release was made, but distributions pick up snapshots to produce distribution releases. - Wikipedia

    Wikipedia lists six distributions; amongst them Arch, Debian, Gentoo, Guix

  • When I see that it's GNU, I can trust in it's license, and that it's backed by an org - whether actively maintained and developed or not. My impression is that the sources are not accessible to me, personally, mainly because of legacy tech stack but also they're typically in C or C++ which is often less approachable, and often they're Linux-only or -focused.

    The GNU label, (if confirmed by the project being on their official websites), gives projects an immediate boost in trustworthiness over random FOSS projects.

  • I suspect many don't enforce it via GitHub functionality, but do implicitly require or recommend reviews.

    How many contributors do these projects have? All multiple active?

  • If the original contract was for software without source code, you'll have to negotiate. I don't think it's helpful to look for options and licenses before knowing what they are ready to do and share and what restrictions they would require for that.

    They would be very well within their right to outright refuse. The vendor-lock-in may even have been an explicit business strategy. I assume they offer maintenance, at a higher price than you would cost?

  • What does this parallel work mean? Does the background agent work on the same codebase as you? Doesn't that cause conflicts and confusion?

  • I would rather not have my 20-60 work commits, possibly shifting solution design twice or three times, in the main project history, spanning days and sometimes weeks, invalidating earlier commits, and a hassle if not impossible to reasonably and efficiently document changes between them. And all those changes intertwined with my other work and my colleagues' changes.

    The key insight from Charity Majors is that speed and safety are not trade-offs -- speed IS safety. “Ship a single changeset by a single dev at a time, making it easy to isolate the owner of any problem, preventing the blast radius from expanding, and making it easy to fix while the intended effects of the code are fresh in their mind.”

    I really don't get how "develop in feature-flagged trunk" is supposed to come together with "single dev single changeset". Work evolves. Design evolves. Surely, multiple/many "single changesets" must come together to form new features and changes? This claim seems to assume issues are found before it's being changed again, and in a timely manner, even when it is behind a feature flag?

    Were pull requests really "created for FOSS"? I feel like, maybe assume, pre-merge reviews have been a thing before that [and unrelated to PRs].

    I feel like the article could have been structured a lot better, and made its point without a "it's like this" "but maybe not" digression. Feels like inflammatory bait into relativation. I guess I'll refrain from raising my other points and disagreements that I noted because by the end of the article, it wasn't really claiming it broadly anymore anyway.

    Outside of the irritation, I found the arguments interesting. I'll keep it in mind, but I don't see my team implementing it like that or to a higher degree. For various reasons.

    Despite the negative vote sum, I think it's an interesting alternative perspective. Even if I found it irritating to read, and even if people hate it, it's a good discussion in the comments. About how we work.

  • I hope Microsoft leaves GitHub alone

    I see no way of that happening. GitHub is a huge resource for Microsoft; in terms of market penetration, people platform, but especially now with GitHub Copilot and their push for AI. They can't let go of GitHub.

  • Are there docs / an overview of what it does and how?

    I remember Google marks their generated videos in some way. Is this based on similar or same published papers and approaches?

  • Thank you for the kind words :D

    I did not recognize it from macOS

    Are you saying it's not from macOS - or at least was not part of the macOS you've actually seen? This thing is many years old, so it wouldn't be a very recent thing.

    I don't use or see macOS, though, so my [historical] impression could be wrong (which is why I used subjective/uncertain terminology).

    Or by 'suggesting' did you mean you were joking?

  • I'm pretty sure that's originally a macOS thing. Then some design tools adopted it (probably because designers are in the macOS world). I took this from the screenshot in the linked pull request. No idea what they use, but I assumed macOS. Dunno if any Gnome or KDE themes adopt it.

  • True, and I think he makes it very clear that that's the case. I still found it informative. The whole thing speaks a lot more about the surrounding things. Mythos is just the intro.

  • Maybe a Colmi smart ring, versions ranging from 13 to 30 €?

    I got a Colmi Smartwatch for 13 €. It doesn't integrate into the standard Android Health thing but seemingly uses its own protocol or sth.

  • If the top left window actions can be one color each, then the bottom can too!

  • I inject an entire set of CSS rules into Jira and into Confluence 🫠

  • More than once Repeatedly, I used my mouse back button in an attempt to navigate back in the "file explorer", but instead navigated back in the webbrowser. 😅

  • Looks like the repeatedly mentioned https://code.overheid.nl/ is down. It launched at the end of April. It was a good run. /s

  • I found the sections before it too elaborate and repetitive for my taste, but the section 'The defenses, weakest to strongest' with technical details about runner security was interesting.

  • Nushell @programming.dev

    GitHub Actions Workflow for testing Nushell env and config files

    github.com /Kissaki/nushell-config/blob/main/.github/workflows/main.yml
  • Programming @programming.dev

    Edgio files for bankruptcy, Microsoft has to update some dotnet CDN URLs that used azureedge.net domain

    devblogs.microsoft.com /dotnet/critical-dotnet-install-links-are-changing/
  • Nushell @programming.dev

    Nushell 0.101.0 | Nushell

    www.nushell.sh /blog/2024-12-24-nushell_0_101_0.html
  • Programming @programming.dev

    Deno v. Oracle: Canceling the JavaScript Trademark

    deno.com /blog/deno-v-oracle
  • Programming @programming.dev

    How Did REST Come To Mean The Opposite of REST? | htmx

    htmx.org /essays/how-did-rest-come-to-mean-the-opposite-of-rest/
  • Nushell @programming.dev

    Nushell CLI command to download the highest-quality opus audio file through yt-dlp

    kcode.de /blog/2024/2024-03-12_nushell-command-alias-download-opus-audio-through-yt-dlp/
  • Nushell @programming.dev

    Nushell - A Great Shell (Command Line)

    kcode.de /blog/2022/2022-08-11-nushell/
  • Nushell @programming.dev

    Nushell 0.100.0 | Nushell

    www.nushell.sh /blog/2024-11-12-nushell_0_100_0.html
  • Programming @programming.dev

    Announcing .NET 9 - .NET Blog

    devblogs.microsoft.com /dotnet/announcing-dotnet-9/
  • Programming @programming.dev

    Announcing Deno 2 - Full npm compatibility, Stabilized Standard Library

    deno.com /blog/v2.0
  • Programming @programming.dev

    Steam 'Ada Lovelace Day' Sale - Coding, Automation, Engineering games

    store.steampowered.com /sale/AdaLovelaceDay
  • Programming @programming.dev

    Using the term ‘artificial intelligence’ in product descriptions reduces purchase intentions

    news.wsu.edu /press-release/2024/07/30/using-the-term-artificial-intelligence-in-product-descriptions-reduces-purchase-intentions/
  • Programming @programming.dev

    Opus 1.5 Released - achieves audible, non-stuttering talk at 90% packet loss

    opus-codec.org /demo/opus-1.5/