10
It's copies everywhere
I'm hopeful that there's some progress they can share even with their primary focus on COSMIC DE. Both projects feel like a big step up for the company.
I've read that. Defining a supplier as someone with whom you have a direct business relationship with seems intentionally narrow in an unhelpful way that just further muddies the waters around the issue at hand. Making something generally available to others means that you're supplying others with that thing. While it's true that you may have no further obligations to those that receive your software, the person receiving the software needs to evaluate their risks around using and depending on that software regardless of the existence of a business relationship with the supplier. Hence supply chain risk evaluation is always necessary. That risk evaluation, or lack thereof, can result in a security problem. These problems can propagate widely within a software ecosystem. This is true with and without the existence of direct business relationships between suppliers and recipients of software.
The whole article can be summarized by saying if you want support services related to the software written by others, negotiate a support agreement related to that software. That has nothing to do with taking a wide or narrow interpretation of the word supplier.
You might be onto something here.
Developers should think about what libraries they trust, but it seems that most of the time they'll choose whatever is most convenient for handling the immediate problems they're working to solve.
I'd be nice to be able to read that article with more than one sentence appearing on the screen at time.
Would you mind sharing some details around what you learned?
13
I like Ladybird more than any of those alternatives.
Federation issues are sneaky
I'm fascinated by Raku myself.
Entirely depends on the project you want to build
view more: next ›
Someone is going to need to pull a lot of weight in planning, organizing, and leading these meetings, presentations, and projects.
I find that unless you communicate the time and financial cost expectations to participate in groups like this, you'll get a lot of people who are marginally interested and attached to the group and it's purpose. Which may or may not be important in a successful endeavor.
Discuss the questiona you've raised here.
This is a what I mean by someone pulling a lot of weight, a teacher carousel has a slim to none chance of working out. One person is going to need to define and implement the vast majority of the curriculum. They'll need to do a lot of research and work in advance.