eptcyka

Futures would be less of a problem if async was implemented as effect handling instead of coloring functions - I am truly miffed about e.g. not being to use `or_insert_with` with a fallible async function. That and build sandboxing are my 2 pie in the sky dreams for a rust edition far, far away.

Not only that, the charger thing also implies charging it weekly if not more often. I got a pebble watch because I can wear it for 2 weeks without charging. Would hate to have to charge a ring.

Managing a very public project that advertises Zig and doing so poorly is a matter of fact, is it not?

What about debugging?

What is the behaviour that Jarred was called out for that was not related to Bun?

Only if you live in metropolitan cities.

One might argue that these people will not understand the code they write if they use LLMs. I would counter that with my observation that plenty didn’t understand the code they wrote before LLMs too.

By definition you can't protect yourself from the entity that provides you the software you use, because you have now way to guarantee that they aren't going to backdoor you.

But with repro builds and system transparency, hiding backdoors is impractical.

You can run it on an encrypted volume on a VPS. Technically, it is also possible to use confidential VMs, but I have not at all kept up with those developments these days. Confidential here means that the SoC/CPU provides the ability for VMs memory to be encrypted with a key that the host never has access to. There's also remote attestation for it. I personally like e2e encryption at the application layer in some applications, but I personally do not think that it'd be practical for immich unless they also do confidential compute for the classifiers and identifiers. That is something Apple can do because they have the capital, not an open source project.

Large file uploads are non-resumable. That is, if you have any videos at a decent bitrate and resolution, you need to be able to upload the whole file in a single session. iOS doesn't make this easy to do via background uploads. I uploaded everything by keeping the app open overnight.

And having someone less experienced can also bring perspectives and criticism to assumptions that can and sometimes should be challenged.

If there is something to be said, I have to ask. What specifically is there to be said?

What's the reason we can't use heat pumps here to turn that waste heat back into electricity?

Since this is but an iPhone crammed into a laptop, could this behaviour stem from the fact that iPhones generally need not render a cursor?

Isn't that still cheaper than the 100 or 200$ plan that Anthropic wants from you?

Sure, but maybe this is a different battle? First party Linux support is orthogonal to games not using kernel level anti-cheat solutions.

Tangentially, I wouldn't use kernel level anti-cheats, but if Valve's solution is indicative of the SotA in userspace anti-cheat solutions, there's a lot of room for improvement.

Gamers are more than just people playing DOTA and Counter Strike and COD and Destiny.

Nix also forces builds to be sandboxed. Now you actually need to run an infected build output to be affected.

Have you ever touched grass? You could also argue that posting in an online message board is linked with right wing extremism because there are right wing extremists posting stuff online.

You made the association. You literally brought them up yourself.

You brought it up, what do you mean? If one were to bring up allegations of you associating with unpopular movements, would you not clear your name? Having checked your post history, I have to genuinely ask if you're a troll account.

I like the hardware, cannot stand needing to run another machine just for management.

Can I use it without running some inane management VM?

Gamergate has nothing to do with the SKG initiative.

I can understand that this a somewhat practical solution to the problem of codebase is all C and all I have is a C compiler, so there is merit to using the static keyword here. But it is also unwieldy and used rarely, so I do not think it is comparable to Rust’s borrow rules in any meaningful sense.

`int x[static 1]` isn’t exactly intuitive when one wants to define a reference to an integer. Nor is this practical given a dynamic array of integers. Or a single integer field in a struct.

Ye, sure, but Rust won’t compile a `foo(std::ptr::null())`, if the function is defined as `fn foo(b: &Baz)`. C doesn’t get that luxury. That is the point of the article.

Except CDNs, where it is.

There are states that require cars to be crash tested with the dummies without seatbelts. This then encumbers auto designers to cater for that crash test. Some cars will never be homologated in the US because of this, loads of other cars could be more spacious and safer if it was not for this requirement. And it is just 3 states.

If you condition yourself to be OK with 15-25 fps, it's almost fine. If you run a game at 60FPS generally, then an occasional hiccup of 100ms will really throw you off. Similarly, the gameplay must be designed differently between low and high FPS games - you don't want the player to feel like they'd have been able to play the game differently if it was running smoother.