spikespaz

Your argument for "as native as most apps” falls apart pretty quickly though.

I'm not saying it's a bad app. I'm just saying it's a badly made app, because JavaScript was a joke 30 years ago, it's a joke today. (ThePrimeagen)

Most apps aren't native, so being "as native" as the baseline average or better isn't even saying much at all. They're all using V8, and I'm slightly less disgruntled if they use something like React Native or whatever instead of Vue and virtual DOM stuff. This was brief but you get the idea.

Also, Xamarin and Flutter/Skia do exist.

Why would everyone need a pi?

You have much to learn Young Padawan. If you're wanting to make a desktop app in Rust it behooves one to avoid embedded web environments. For performance reasons of course.

If your Nixpkgs input uses a specific Git branch, such as nixpkgs-unstable, it needs to be a supported release branch.

Don't like this. Some projects are only intended to use nixos-unstable. And it wouldn't make sense to expect users to override the flake's nixpkgs input with .follows, if they use unstable, because often there are significant differences between code that uses stable and unstable. If the flake targets stable and this is overridden, it's likely things will break.

Your Nixpkgs input must have been updated in the last 30 days.

Seems reasonable.

If your Nixpkgs input is a GitHub repo, it needs to have the NixOS org as the owner. In principle, you could have a Nixpkgs input owned by someone else, for example inputs.nixpkgs.url = "github:EvilCo/nixpkgs".

The reasoning behind this is valid but what if it is a project that needs a fork? This is probably rare, so I guess I'm okay with it.

All in all, I think these are the wrong checks to be doing. There are probably many other assurances that could be made, like correct output attributes (what is known of the official schema plus ones made standard by precedent), validate the values, and suggest making tests for certain common outputs.

The project makes me think that if it gains popularity and people start following these guidelines, you'll see badges on repositories that make newbies think that's the sanctioned way to do things. But there is no sanctioned way to do things yet, flakes are supposed to be freeform.

I think these checks need to be thought out more than they have been, and I think especially the first check has the potential to fragment the community more.

For businesses using Nix, maybe it makes sense.

That's pretty cool, I'll dig around in that later. Was looking for a better way to do nftables.

Yes. The format is widely accepted by the community and generally everybody's preferred way of organizing and sharing code.

Fuck PWA. I want a native, fast app with no JavaScript.

I'll have to try Liftoff.

Sent from Sync Ultra for Lemmy.

I've been using sync as long as I've used reddit. Tried all the apps for Reddit back in the day and Sync was the best. Remember being mad it wasn't FOSS I'm a dev who donates time, and mad respect for others who do too, but also respect to the dev of Sync who is providing a great service. The app is beta and it's already better than most others. It is a familiar experience.

I'm paying, happily.

That's my stance.

But the comments aren't. They're spot on. Lots of voting happening on my end, in favor of paying a fair price.

He didn't go too far. It is a broad and overbearing, but generally accurate statement.

I hate your name