HN user

nerdile

288 karma
Posts0
Comments70
View on HN
No posts found.

tests showed that for environments with one CPU (or fewer)

Article seems AI generated. Is there an official announcement we could be discussing instead?

B2B is just businesses fighting over the value chain.

Blacksmith can send as many invoices as they want.

If the other business doesn't think it's worth the cost after the free trial, they don't have to pay the invoices.

It is different when you have a billion customers, all with different setups. At that scale, you notice real defects through product telemetry, support ticket volume, or trusted channels. You receive a high volume of bug reports that are due to user confusion, misconfiguration, or misbehavior of other software on the device - where solving an issue for one customer doesn't result in improvements for the other billion. Triage, filtering, and winnowing are necessary here.

Reneging on an offer means revoking it after it has been accepted, and that's poor form.

Turning down an offer puts you into a small category of "people we would hire if we had the chance" and the recruiters or hiring managers will follow up with you for some set period of time just in case something changes on your side. They already have decided you would be a good fit, after all.

Title is slightly misleading but the content is good. It's the "Safe Rust" in the title that's weird to me. These apply to Rust altogether, you don't avoid them by writing unsafe Rust code. They also aren't unique to Rust.

A less baity title might be "Rust pitfalls: Runtime correctness beyond memory safety."

The software license terms for Word and all the other desktop apps does not include such a clause, no. https://www.microsoft.com/en-us/useterms

The Microsoft Services Agreement applies to your use of their online services, like OneDrive and SharePoint, as you say, and there's an explicit consent in the app and a giant off switch there. They employ dark patterns to push you strongly to use their online services, but it's still optional.

It should be readily obvious that choosing to use online sharing or storage features or submit reviews require the data you enter to be sent, shared, or stored thusly...

I don't have to grant Word a license to what I type in it. This is a highly unusual clause that other software doesn't have.

When software has to "phone home" to deliver the functionality you requested, then two things happen: One, a number of privacy regulations kick in, and they need to get you to agree to send your data to them. Two, they now get to move your data out of your control. I mean, you trust them today, so here's hoping they don't ever get hacked or hire someone untrustworthy?

It's sad when even to use the basic features of a web browser, you need to agree to send them your data. It's not fundamentally necessary to send your data to Mozilla or their partners in order to load and render a website. It's a dark pattern to obtain consent to collect your data "when it's necessary", and then rewrite your app to make it necessary.

Summary: The UK has some Online Safety Act, any websites that let users interact with other users has to police illegal content on its site and must implement strong age verification checks. The law applies to any site that targets UK citizens or has a substantial number of UK users, where "substantial number" is not defined.

I'm going to guess this forum is UK-based just based on all the blimey's. Also the forum seems to have been locked from new users for some time, so it was already in its sunset era.

The admin could just make it read only except to users who manually reach out somehow to verify their age, but at the same time, what an oppressive law for small UK forums. Maybe that's the point.

As a former Windows OS engineer, based on the short statement here, my assumption would be that your programs are IO-bound, not CPU-bound, and that the next step would be to gather data (using a profiler) to investigate the bottlenecks. This is something any Win32 developer should learn how to do.

Although I can understand how "Please provide data to demonstrate that this is an OS scheduling issue since app bottlenecks are much more likely in our experience" could come across as "denying and gaslighting" to less experienced engineers and layfolk