Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L

lysdexic

@ lysdexic @programming.dev

Posts
439
Comments
601
Joined
3 yr. ago

  • Microsoft opens a "high priority" bug ticket in ffmpeg, attempting to leech the free labour of the maintainers

    Jump

  • Microsoft have every right to fix the bug themselves and the maintainer has every right not to.

    Yes, it does. You do too, and so do I.

    Does it make sense to you for me to attack you for this?

    And how about any person submitting a bug report? Is it ok to pile up on them for not fixing it themselves?

    If you change the names, is your attitude any different? If it is, then you have a problem on your hands, and it's a personal problem.

  • Microsoft opens a "high priority" bug ticket in ffmpeg, attempting to leech the free labour of the maintainers

    Jump

  • There’s a difference between creating something and giving it to the world and being on the hook to help them solve their business problems.

    I think you're extrapolating things that aren't there. If you had any experience contributing to any semi-successful floss project you'd be ver aware that asking for fixes is as common as filing bug reports. This is not a Microsoft problem, it's a staple of FLOSS project management.

    Why do you think it's reasonable to single out a whole company for doing exactly what the community contribution process was designed to be and achieve? On any case you see FLOSS proponents arguing that filing bug reports and troubleshooting problems counts as contributions to improve a project. Yet, here we are attacking someone for doing just that, because of what exactly? Do you think ffmpeg would be in a better shape if the likes of Microsoft didn't reported bugs?

  • Microsoft opens a "high priority" bug ticket in ffmpeg, attempting to leech the free labour of the maintainers

    Jump

  • Completely disagree. This is how it works, Microsoft get software for free but they have no authority to prioritise other people’s scheduling

    I don't know where you're getting the prioritization issue. Anyone in the world who is able to create an issue in a bug tracker can claim anything, but it's always the people doing the bug triages who determine priorities. It means exactly as it means: nothing.

    The "is this fixed yet" posts in bug reports by now is a meme in the floss world.

    I think you're trying too hard to find something to be outraged over.

  • Microsoft opens a "high priority" bug ticket in ffmpeg, attempting to leech the free labour of the maintainers

    Jump

  • I think the maintainer just viewed the bug report as tone deaf. Microsoft is a trillion dollar company and apparently relying on this library without a support contract.

    I think this mentality shows a clear dissonance between how maintainers are licensing their software and what are their expectations in terms of retribution from users of their software.

    If they release a software package with a license that explicitly states that they allow the whole world to use it freely without any expectation if return, they cannot complain afterwards that some particular people in the world end up using it.

    Likewise for bug reports.

    If they want to get paid because the software they have been releasing to be used freely by everyone is being used freely by a specific company then they need to get their shit together and release it under a license where they explicitly state their terms. This is crítical for everyone involved, specially end users, because we need clarity on these terms.

  • C++ @programming.dev
    lysdexic @programming.dev

    std::launder: the most obscure new feature of C++17 (2016)

    miyuki.github.io /2016/10/21/std-launder.html
  • Deleted

    Warning: Vultr (a major cloud provider) is now claiming full perpetual commercial rights over all hosted content

    Jump

  • Not so much debunked as Vultr has realized their mistake and has taken steps to correct it.

    If there was something to be debunked then why are they backtracking and removing the claims from their terms of service?

  • Deleted

    Warning: Vultr (a major cloud provider) is now claiming full perpetual commercial rights over all hosted content

    Jump

  • Those ToC were for their website hosting services (...)

    Why do you think it makes any difference?

    they’ve already responded by removing the confusing language.

    It sounds more like backtracking to avoid the backlash.

  • C++ @programming.dev
    lysdexic @programming.dev

    Should we move from fundamental types?

    www.sandordargo.com /blog/2024/03/27/move-from-funtamental
  • Data Structures and Algorithms @programming.dev
    lysdexic @programming.dev

    CppCon 2017: Matt Kulukundis “Designing a Fast, Efficient, Cache-friendly Hash Table, Step by Step”

  • Monad (functional programming) - Wikipedia

    Jump

  • Honestly, I don't mind the downvotes. What puzzles me is how some people feel strongly enough about a topic to subscribe to a community, but still feel compelled to slap down contributions in a time nothing is being submitted, as if seeing no new posts is better than seeing a post that might not tickle their fancy.

    It's the difference between building up and tearing down.

  • C++ @programming.dev
    lysdexic @programming.dev

    P2809R3: Trivial infinite loops are not Undefined Behavior

    isocpp.org /files/papers/P2809R3.html
  • Data Structures and Algorithms @programming.dev
    lysdexic @programming.dev

    Bump Allocation: Up or Down?

    coredumped.dev /2024/03/25/bump-allocation-up-or-down/
  • Node.js @programming.dev
    lysdexic @programming.dev

    require(esm) in Node.js

    joyeecheung.github.io /blog/2024/03/18/require-esm-in-node-js/

  • Qt 6.6.3 Released

    Jump

  • On Tech Debt: My Rust Library is now a CDO

    Jump

  • TIL rust has some sort of ratings for libraries/dependency code.

    A random guy going through the trouble of putting together a site to subjectively rate other people's work is hardly something that's language-specific.

    I'd wager that adding a single tag/field to represent the programming language is all it takes to make the system universal.

    Also, that's not even language-specific. It's package-centric.

    I get it, joining bandwagons is fun. That's not a substitute for thinking things through, though.

    By the way, npm even supports package auditing, warnings, and autopromoting packages and its dependencies. You don't hear people constantly parroting switching projects to Node.js over this, though.

  • Monad (functional programming) - Wikipedia

    Jump

  • I've submitted this link because the topic is interesting to me, and !functional_programming@programming.dev is practically dead, with the last post dating back over 10 days.

    For those who are down voting the contribution, be my guest and do better: submit interesting content.

  • Data Structures and Algorithms @programming.dev
    lysdexic @programming.dev

    Open Data Structures: An open content textbook

    opendatastructures.org
  • Data Structures and Algorithms @programming.dev
    lysdexic @programming.dev

    BinaryHeap: An Implicit Binary Tree

    opendatastructures.org /ods-java/10_1_BinaryHeap_Implicit_Bi.html

  • Things You Should Never Do, Part I (2000)

    Jump

  • Yes. Multiple historical layers (...)

    This is reaching a level of idiocy that's completely unheard of.

    Just say you know nothing about what you're saying and you're completely oblivious, and sit out the rest of the discussion.

  • Things You Should Never Do, Part I (2000)

    Jump

  • If Google were to start over, all of that would be thrown out. It just can’t be done.

    To stress the importance of this very basic fact, people need to understand that even Google, a company with virtually limitless resources to rearchitect and rewrite any and all type of software project, made the call to avoid using major features offered by some programming languages, such as C++'s exceptions, because it could have unintended consequences on the company's legacy code base which they could not rewrite.

    And here we are, reading fantastic claims over how complete rewrites are reasonable things while flipping compiler flags to harden legacy projects is unheard of.

  • Things You Should Never Do, Part I (2000)

    Jump

  • Most software is built under non-ideal circumstances. Especially in the beginning there’s often tight deadlines involved.

    Exactly this.

    I think a bunch of people commenting in this thread on the virtues of rewriting things from scratch using the flavour of the month are instead showing the world they have zero professional experience working on commercial software projects. They are clearly oblivious to very basic and pervasive constraints that anyone working on software for a living is very well aware.

    Things like prioritizing how a button is laid out over fixing a rarely occurring race condition is the norm in professional settings. You are paid to deliver value to your employer, and small things like paying technical debt are very hard sells for project managers running tight schedules.

    Yet, here we are, seeing people advocating complete rewrites and adding piles of complexity while throwing out major features, and doing so with a straight face.

    Unbelievable.

  • GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

    Jump

  • You have a point. Thanks for taking the time to go through this. Good job.

  • C can be memory-safe (2023)

    Jump

  • This is a flippant statement, honestly, as it disregards the premise of the discussion. It’s memory safety.

    You're completely ignoring even the argument you're supposedly commenting,let alone the point it makes. You're parroting cliches while purposely turning a blind eye to the point made in the blog that yes C can be memory safe. Likewise, Rust also has CVEs due to memory safety bugs. So, beyond these cliches, what exactly are you trying to argue?

  • C can be memory-safe (2023)

    Jump

  • In fact a reasonable compromise is possible: rust is perfectly capable of interoperating with the C languages.

    I doubt you work on software for a living, because not only are you arguing a problem in a desperate need for a solution but also no one in their right mind would think it is a good idea to double the tech stacks and development environments and pipelines and everything, and with that greatly increase the cognitive load require to develop even the simplest features, just to... For what exactly? What exactly is your value proposition, and what tradeoffs, if any, you took into account?

    You are free to do whatever you feel like doing in your pet projects. Rewrite them in as many languages you feel like using. In professional settings where managers have to hire people and have time and cash budgets and have to show bugs and features being finished, this sort of nonsense doesn't fly.

  • Things You Should Never Do, Part I (2000)

    Jump

  • Yet the world is full of code that was replaced with less work than it would take to fix a single bug on the broken original.

    Can you point out a concrete example? Because you're commenting on a discussion on an essay that documents several notorious examples that demonstrate the opposite point.

  • GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

    Jump

  • Doesn’t create symlinks or mess with global NPM packages.

    That's hardly relevant for those who need to run node on Windows and WSL is not an option.

    Also, nvm is only supported on windows through WSL or cygwin, just like n, not sure where you are getting nvm for windows.

    Just yesterday I installed it through chocolatey on a Windows box without WSL.

    Also, it seems you failed to notice that nvm makes references to cygwin and git-bash, the later of which everyone who installs Git ends up having in their system.

  • Clean Code: A Handbook of Agile Software Craftsmanship

    Jump

  • It’s not to pretend there’s no good advice in the book, but that the bad advice is really bad and very prominent.

    Care to point out what you think is he absolute best example that supports your point?

    A single example will do.

    Otherwise all you have to show is an unsupported personal observation which contrasts with what's written on the book.