We didn't get locking until npm v5 (some memory and googling, could be wrong.) And it took a long time to do everything you'd think you want.

Changing the main command `npm install` after 7 years isn't really "stable". Anyway didn't this replace versions, so locking won't have helped either?

You can’t replace existing versions on npm. (But probably more important is what @jffry mentioned – yes, lockfiles include hashes.)

> Anyway didn't this replace versions, so locking won't have helped either?

The lockfile includes a hash of the tarball, doesn't it?

It does, the answer to my question was no.

vscode came along with a thriving extension ecosystem. That made up for any pitfalls really.

Reading how the keys trigger, I don't know if this is interesting or not but that how high end paintball markers work, with lots of adjustability.

> But it became a general purpose programming language pretty early, right?

IMO what we've seen learnt from ChromeOS and later their stab at firefox OS is the merit in treating the browser as the system. For that there was a lot of wisdom in making rust that capable. Seeing oxide make their stack is incredibly validating.

I just think £360 for an IP camera is too steep, half would be a no brainier over ring. Their new Lite switches replace stuff that was rack-mountable, not there's no ears are far as I can tell.

The gateways are awesome value.

I got into Ubiquiti due to their APs being effectively enterprise level features for consumer level prices. Their coverage and quality was a cut above the TP-Link gear I'd used previously (which was, in turn, better than the D-Link and Netgear stuff that I'd tried).

So I am confused by their Camera prices being so high.

I went with Reolink on cameras and NVRs and don't regret that decision. Probably spent a third of what it would have cost for Ubiquiti. There must be some benefit to the extra cost, but I don't think it's one I'll miss.

I have a couple sites with both types of cameras. And I really love all the customizability with my Frigate / Reolink site. But UniFi can command the premium on the camera hardware because of all the features they give you on the software side of their NVR. It's far better than what you get out of the box compared to something like Reolink in terms of detection and set-it-and-forget-it mentality.

I have a site that has 8 cameras and 2 of the 8 are original cameras that are >5 years old still getting firmware updates. Reolink does not do this and I have had much higher failure rate with them as well. Especially in outdoor cameras that have to handle snow/ice/extreme cold.

You have to get pretty high in their product range before you hit £360 for a camera. The G3 Instant is probably the closest to a Ring competitor (Wifi, 2K video) and it's £78.

The £360 camera is the G5 Pro, which is a 4K camera with 3X optical zoom. I'm not aware of any Ring camera with optical zoom. If you don't need the zoom, the G6 Bullet is a 4K camera without zoom for £190, and the G5 Bullet is 2K for £126. As far as I know, Ring's highest resolution camera is 2K.

But Unifi isn't really trying to be a Ring competitor -- Ring caters to home users with little knowledge of networking, Unifi is more for small businesses (who use an integrator to install their system) or prosumers with more advanced network knowledge.

Especially when they die after 2 years. Bought 3 G4 Pros direct from Ubiquiti and two are dead. Apparently it's just the POE daughterboard but my RMA requests were rejected due to being out of warranty. My cheap Lorex cameras have been running for 8 years now.

They have a lot of camera models, including a lot of cheaper models, starting at €180 for the G6 turret/bullet if you want 4k or €80 for the G5 turret if you want 1080p.

Looking at the various options, £360 is on the upper end (until you get into the insane DSLR lens one)

I'm baffled you can't clone internal/private repos with anything other than a developer PAT. They have a UI to share access for workflows, let cloning use that...

SSH also works, but I’d love to be able to just use git-credential-oauth [0] like for any other repo.

[0]: https://github.com/hickford/git-credential-oauth

I use GitHub apps for this, it’s cumbersome but works.

Use a GitHub app, that’s what it’s for.

what with actions/checkout@v4, hows that documented?

https://github.com/actions/checkout/issues/567#issuecomment-...

GH has a `permissions:` entry and this mechanism already for internal repo action sharing. And thousands of our dollars per month.

Yes but they will rerender from where the context was created not where it's used, so you can get a lot of UI renders.

I think the new memo compiler address' this in the most complicated way possible.

That's simply not true.

  function MyProvider({ children }) {
    const [value, setValue] = useState()
    return <Context.Provider value={value}>
      {children} 
    </Context.Provider>
  }

In the above example, the Provider re-renders, but it's children remain unchanged.

> Yes but they will rerender from where the context was created

Wow that's really bad and make it basically useless.

A re-render in React is not as heavy as you'd think it is. It's painting the DOM that takes resources, and people conflate the two. But if your whole component re-renders because of a change in context, yet nothing on the page changed, you will likely not notice the render even on low-end devices.

I still think Zustand is the simplest state management, while staying efficient. It's similar to the old Svelte stores. But I have used many state management tools and the re-renders were not the problem when it came to speed.

not if the compiler stops the unneeded re-renders.

A "compiler" to solve the issues the library created, awesome. It doesn't solve many re-renders tho, as React re-render full components, not only the HTML/Text Nodes that changed.

yeh if you can't shove numpy in there its not really useful.

That is how the EU will do that.

That's not how literally anything works, or has ever worked.

I used mercurial in anger for about 9 months or something, with a gitlab fork too. when git goes wrong there's forums, blogs, books and manuals. When hg does it's a python stack trace, good luck.

When I've had mercurial issues, I went to the mercurial channel on libera, or to their manual. But then, haven't ended up with a stack trace yet.