ericjmorey

Any thoughts on how to get this up and going?

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.

What would we need to do on our first meeting together?

Discuss the questiona you've raised here.

What things would you want to learn in this course? It seems to me that many of us are already quite literate in sub-domains of what we are interested in. Maybe a teacher carousel routine could be adopted? Where we adopt a general “roadmap” curriculum, and, in an ad hoc fashion, assign people to be the instructor for the desired lesson?

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.

It's copies everywhere

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?

I like Ladybird more than any of those alternatives.

Federation issues are sneaky

I'm fascinated by Raku myself.

It didn't make any sense to me when it was originally announced, it still doesn't. I don't understand the project's goals or how it's supposed to reach those goals. The mission statement is incomprehensible to me.

My keycard didn't work.

Sounds like your project is building arrays in different dimensions and multiplying them.

Maybe give polars and pandas a try.

Definitely check out SciPy

People keep telling me that scrapy is the best for scraping but I haven't had time to try it yet.

Entirely depends on the project you want to build

That awesome!

There are always many ways to deal with workflow annoyances you run into. Most people go looking for plugins or write a plugin or remap some keybindings, but many forget to read the manual to look for builtin solutions. In the case of using d, you can assign the deleted text to a register other than the default register for yank/delete commands.

dd will delete a line and send it to register "

"xdd will delete a line and send it to register x

p will put the text from register " after the cursor

"xp will put the text from register x after the cursor

Use any lowercase letter for a register. There's always more beneath the surface of simple vim features.

Relevant sections of the User Manual:

You'll own nothing and you'll be happy - Ida Auken

Chris Warwick doesn't post to his blog often, but when he does he's thoughtful and informative.

The author mentioned limitations only vaguely at the end of the article.

Consider using https://www.fossil-scm.org/

Although I understand if you don't wish to stop using git.