Skip Navigation

spartanatreyu

@ spartanatreyu @programming.dev

Posts
1
Comments
105
Joined
3 yr. ago

  • COSMIC Epoch 2 and 3 Roadmap

    Jump

  • I don't understand comments like this

    It’s a wishlist of Open tickets. Wouldn’t necessarily even call this a commitment to a roadmap.

    Roadmaps are just wishlists with a committed to priority list, like an assembly line. Programming doesn't work like an assembly line and anyone trying to convince you to the contrary is bullshiting marketing.

    Every task has the potential to bring forwards new information that changes the order in which tasks should be completed, let alone which tasks even need to attempted. You only get all the information once you've finished.

    Instead of having an inflexible commitment, use a wishlist, and do the tasks in order of which one makes the most sense at the time.

    75% of Open tickets will never get resolved anyway.

    Based on what?

    You can clearly see that practically all tickets in their previous epoch were resolved: https://github.com/orgs/pop-os/projects/23/insights?period=max

  • Rust Coreutils Continues Working Toward 100% GNU Compatibility, Proving Trolls Wrong

    Jump

  • If I were a uutils developer, I would stay far away from all of these discussions because of how much hate is directed towards it.

    I only see the hate towards this project being either from anti-rust trolls, or misdirected hate from Ubuntu towards switching to a new coreutils implementation on an LTS release before full compatibility has been achieved. I don't see any hate in regards to licensing.

    If they do not adopt the license you prefer, would it be better for them to just go ahead and abandon the whole effort? Are there efforts really so valueless simply because they chose the license that they did?

    Their efforts have value, but the value is limited by its current license. MIT licenced projects have a recurring history of being improved privately without those improvements going back into the project. It leads to a lot of duplicated, wasted effort. There may also be the potential for patent issues with the licence. No one wants to deal with some litigious asshole or company going after the project turning it radioactive.

    Moreover, is dictating to volunteers what license they should be using for their code what you think this community should be about?

    I think bringing up issues with the project is definitely something that should be brought up. As for dictating which particular licence is used, that's up to the contributors, but that doesn't mean others can't give their input. It's also likely that most of the contributors will want a license that allows the project to safely continue into the future.

    You claim that it is important that people make tons noise in every single post on uutils because it will prevent a bad scenario down the line, but could you detail what that scenario is? Because people like to make allusions to such a scenario constantly but refuse to get specific and then engage on a discussion on the specifics.

    I thought the Redis example was a good example of this.

    I continue on this point further down, but I'm leaving this right now to stay on topic with redis.

    Incidentally, your choice of Redis is an example exactly illustrates my point that this license is not a gigantic deal it shows that the worst case scenario is… uutils being forked.

    The community was fractured. A report by an enterprise support company said 75% of existing redis users were motivated to seek alternatives. I'm not sure what number you would consider to be a gigantic deal, but Redis certainly thought it was, otherwise they would not have reverted back to the previous license.

    Heck, it can even be forked at any time with a copyleft license precisely because its existing language is permissive.

    It can be forked, but relicensing can mean needing permission from every contributor of the original, and/or removing all contributions from those who don't agree to the new licence. Not to mention the community fracturing, and legal issues. It's a massive effort that can be prevented by the original project choosing a better license earlier.

    You claim that it is important that people make tons noise in every single post on uutils because it will prevent a bad scenario down the line, but could you detail what that scenario is? Because people like to make allusions to such a scenario constantly but refuse to get specific and then engage on a discussion on the specifics.

    Well this comment is probably getting too long, so I'll simply point you towards the busybox licensing drama.

  • Rust Coreutils Continues Working Toward 100% GNU Compatibility, Proving Trolls Wrong

    Jump

  • So it needs to be commented on in every single article?

    Yes

    If so, is that going to change anything?

    Potentially.

    The alternative is not bringing up the concern and it goes forgotten until it is too late and we are stuck with the results of bad decisions for no good reason.

    Developers voicing their concerns is the only way things can change for the better.

    Here's two examples:

    1. Redis licensing rug pull

      1. Redis unexpectly changed its own licencing
      2. Developers demanded Redis return to its original (or similar) licence
      3. Redis said no
      4. Developers formed their own Redis clones from scratch with compatible APIs
      5. Developers switched to the new Redis replacements
      6. Redis returned back to the original licence in an attempt to keep existing users
    2. Google's JpegXL whiplash

      1. Google added support for jpegxl in Chrome
      2. Google removed support for jpegxl in Chrome in favour of inferior standards
      3. Developers demanded support added back
      4. Google said no
      5. Developers flooded every issue tracker and feature request with support for jpegxl, consistently, unrelentingly, for years
      6. Other browsers add support for jpegxl
      7. Creative industry adds support for jpegxl
      8. PDF association adds support for jpegxl
      9. Google forced choose between jpegxl or fall out of supporting pdf standard
      10. Google readds jpegxl support

    And there's plenty of other examples (e.g. Microsoft against linux -> WSL support, etc...)

    If developers don't voice their concerns, then things stop changing for the better.

  • Rust Coreutils Continues Working Toward 100% GNU Compatibility, Proving Trolls Wrong

    Jump

  • Licencing is a legitimate concern (not noise), even more so considering it's for the core utils

  • Locked

    Yes, Windows is the Problem.

    Jump

  • macOS has far better desktop applications across the board than Linux. What you get for free with a Mac is nothing to sneeze at:

    Counterpoint: The apple of yore is not the apple of today.

    Recent examples:

    At this point, the beginner-friendly linux distros (Linux Mint, Ubuntu, Kubuntu, Bazzite) are more sensible and logically consistent than either Windows or MacOS.

    Tangent: If you're looking at paid git clients on MacOS, I'd recommend fork over Git Tower or Kaleidoscope.

  • Help open the source of the myGov Code Generator app

    Jump

  • Not if the standards rely on dedicated hardware, for example: security enclaves.

    The whole point of using a security enclave on different hardware is so that its memory cannot be accessed or polluted by a process or side channel attack on the main hardware.

  • Help open the source of the myGov Code Generator app

    Jump

  • Counterpoint: Public funds pay for software used by military and intelligence services. Certain information becoming publicly available can lead to real harm. (e.g. A self-assessment on a country's own weaknesses, methods that spies deployed abroad can deliver information back, etc...) How do you manage the infohazard risk?

    all software paid for by public funds should be open source.

    Should probably be changed to: all software paid for by public funds should be open source so long as their is no or low foreseeable infohazard risk.

  • Help open the source of the myGov Code Generator app

    Jump

  • Counterpoint: A government portal needs to be extremely backwards compatible to support as many people as possible. That includes supporting devices that don't support the latest standards.

  • Wayland didn’t kill Linux desktops, but it did expose their weakest assumptions [EDIT: Warning, article likely written with AI assistance]

    Jump

  • That should be:

    People use used windows because it has had decades of backwards compatibility sort of.

    Nowadays: it has current compatibility sort of.

    Microsoft is a mess now, so it's no surprise that their current Windows version is also a mess.

  • Where is Linux not working well in your daily usage? Share your pain points as of 2026, so we can respectfully discuss

    Jump

  • App stores are always terrible no matter which distro you use.

    • Images don't load
    • Stuck waiting 30 seconds for a page in the app store to load (if it loads at all)
    • last rating is 7 years old
    • random utilities written 12 years ago are at the top of the page
    • "featured" apps haven't even been tested on that distro

  • Where is Linux not working well in your daily usage? Share your pain points as of 2026, so we can respectfully discuss

    Jump

  • There's a million different apps for this, and they add features on top like sharing one mouse, keyboard between devices, etc...

  • A nice CSS framework located between Pico CSS and Bootstrap?

    Jump
    • Bootstrap 2-5 sucked, but it was great for throwaway internal tools that will never become public.
    • Foundation died to bootstrap.
    • Pure was made by yahoo and went unmaintained so some other people wanted something like pure but they wanted to monetize it, then Pure got remaintained by it's community
    • Tailwind isn't great, it sold devs on a lie by limiting choices to limit mistakes, but limiting choices also restricted the features that devs needed to do their projects properly. They tried to figure out a way to add those features but suffered from gradual scope creep while trying to maintain it's original lie and has ended up more complicated than it needed to be while being less featureful than what devs needed. What they should have done instead of making everything a utility class, was keep the build system (lightning css), add a token system (e.g. open props, or their own version of it), allow people to add their own css instead of trying to shoehorn it into a class, then went out of their way to teach people how to make things as classless as possible.

  • A nice CSS framework located between Pico CSS and Bootstrap?

    Jump

  • Or if you need something smaller, simpler and more modular: purecss.io

    (Yes it's weird that they called a framework "pure" css, but it's been a solid go to for a long time)

  • You can apparently use Windows 7’s compositor in GNOME, and vice versa – or something

    Jump

  • Developer Claims Photoshop Installers Now Work on Linux Using Wine

    Jump

  • Why does everyone talk like Photoshop is the only program Adobe makes?

    It's because most professional creative jobs require raster image editing in at least some part of the production pipeline and photoshop fulfils that need in the adobe suite, so it's the most talked about product in that suite.

    For linux, we have great:

    • Video editing (Davinci Resolve)
    • 3d (Blender)
    • Digital Art (Krita)

    But raster image editing isn't in that list.

    There's things like GIMP, but it's always behind photoshop. It only got non-destructive editing less than a year ago (which is what most serious creatives need to use), but photoshop's had that since CS2 back in 2005!

    If someone actually wanted to beat adobe (e.g. the EU or wikimedia), they would have to pay for 20 developers to work on graphite and you'd probably have something better than GIMP or Inkscape after 7 years, something better than Affinity in 12 years, and something better than photoshop in 15 years.

  • Developer Claims Photoshop Installers Now Work on Linux Using Wine

    Jump

  • Well... Youtubers (and other creatives) are the main awareness funnel for everyday people to hear about linux in the first place.

    Creatives are typically stuck on windows because their workflow doesn't work on linux. And yes, they can change their workflow, but there's also a high time + effort cost to doing that which gets even higher for them since they still need to produce their works while switching.

  • The Birth & Death of JavaScript

    Jump

  • Yeah, I'm the lead on a bunch of websites that all have to be localised.

    There's a lot of weird footguns to watch out for, and a lot of retraining devs when they're used to only working on a single language/locale.

    Two biggest head scratchers I've had to deal with are computers treating "fr-FR" different from "fr-fr" (due to file system case-sensitivity differences between developers), and having to undo the coded assumption that languages and locales follow an [a-z]{2}-[a-z]{2} pattern (e.g. "en-gb") once we stumbled upon Latino Americano: "es-419".

    EDIT: My left ear really loves the Erlang talk.

    This fixes it:

     js
        
const audioContext = new AudioContext();
const audioElement = audioContext.createMediaElementSource(document.querySelector("video"));
audioContext.destination.channelCount = 1;
audioElement.connect(audioContext.destination);

  • The Birth & Death of JavaScript

    Jump

  • Ooh, I didn't know about that site.

  • The Birth & Death of JavaScript

    Jump
  • Software Gore @lemmy.world
    spartanatreyu @programming.dev

    Googling a message warning of potential corruption, confirms that corruption in an unexpected way.