splat VS node

This is a simple Service Locator for Dart and Flutter projects with some additional goodies highly inspired by Splat. It can be used instead of InheritedWidget or Provider to access objects e.g. from your UI.

I read through the PR discussion in question as part of reading Rob Mensching's post before I came across this discussion, and thought that she'd overstepped. However, after watching Tim Corey go through the same discussion, I realise that not only did she overstep, she appeared to actively (and publicly) fight with the current maintainer. Her actions appear (to me) to be completely arrogant, selfish, uncaring, and frankly dangerous to the project.

Head of .NET Foundation creates and merges a PR for a change they made to a project where they hadn't been active for several years. When confronted by current maintainers, their response was at the very least, hostile and poorly thought out.

Many projects joined the .NET Foundation after it was created. It didn't really do anything, but it wasn't harming anyone either.

The .NET Foundation asked for owner access on a repository (for their CLA bot). The author declined and a workaround was organized.

Years later the .NET Foundation asked for owner access on a repository (to allow them enforce Code of Conduct across all repositories. The author declined.

The CLA bot stopped working. The author was told it would work if he gave it owner access. The author was annoyed because they previously had a workaround. They gave in and gave @dnfadmin owner access.

The author woke up and realized that the project had now been silently moved to GitHub Enterprise. The author states that projects in GitHub Enterprise can be entirely controlled by the owner of the account (the .NET Foundation). This transfer happened silently.

Independently, this happened to another project (who had coincidentally had an issue with a Microsoft employee and former contributor force a pull-request into their project: https://github.com/reactiveui/splat/pull/778).

People are upset because of how tone-deaf all of this is. They would like the .NET Foundation to stop trying to gain complete control over the member projects. They would like Microsoft employees to not force pull requests into their projects.

> I am not versed in all the details here

You should probably read the conversation in the PR: https://github.com/reactiveui/splat/pull/778

> there is a dire need for professional communications training among these programmers.

Maybe, but probably not why you think.

Once you've read the PR's conversation you'll see this isn't about someone just merging a PR which wasn't approved. This about someone submitting a PR, a maintainer asking for discussion before merging it, ignoring the maintainer and just merge the PR, the maintainer asking why it wasn't discussed and then making a snide remark to the maintainer.

So I agree that the "Sorry for merging a PR" isn't going to cut it here. The merging of the PR was the least of the problem. It's a hollow corporate-style apology where someone is allowed to be called out for. It's like saying: "Sorry I hurt your toe" after you pushed someone of a cliff.

Library inspired by Splat from the React world again. Library is not so popular like previous and maintenance is also a little lower.

Before starting a new project in react, you need to make sure that you have NodeJS install on your system. You can download the latest version of node at https://nodejs.org. Follow the instructions on the node website to do the installation.

Installing Node.js: Download and install Node.js from nodejs.org. Choose the version recommended for most users, unless you have specific needs that require the latest features or earlier compatibility.

You should have Nodejs installed on your laptop and if not, check the Node.js official website, and download/ install the latest and stable release.

[Nest] 60017 - 04/22/2024, 1:07:48 PM ERROR Error [ERR_INTERNAL_ASSERTION]: Error: BSONError: Cannot create Buffer from undefined at Object.toLocalBufferType at Object.toHex at ObjectId.toHexString at ObjectId.inspect at ObjectId.[nodejs.util.inspect.custom] at formatValue (node:internal/util/inspect:782:19) at formatProperty (node:internal/util/inspect:1819:11) at formatArray (node:internal/util/inspect:1645:17) at formatRaw (node:internal/util/inspect:1027:14) at formatValue (node:internal/util/inspect:817:10) This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues

Node.js

To install and run Ember.js, you'll need to follow these steps: Install Node.js and npm (Node Package Manager) on your computer. You can download the latest version of Node.js from the official website. Once Node.js and npm are installed, open a terminal window and run the following command to install the Ember.js command line interface (CLI):

NodeJS - Link

To get involved in the Node.js developer community, you can join community discussions or begin with learning if you’re new. The community discussion houses a GitHub list of issues related to Node.js' core features. If you want to chat in real time about Node.js development, there are Slack groups, and you can still connect with IRC clients or web clients when using the browser. Node.js has a calendar for public meetings.