parminya

or the go one:

$ go run github.com/eliben/static-server@latest

JSX and PHP are actually seriously different. When you break out of PHP, you're just outputting text to standard output. When you're using JSX syntax, you're constructing Javascript objects that can be manipulated using standard javascript techniques. Anyone who believes they're comparable seriously doesn't understand the task that is before them.

Firefox on iPhone is Firefox on iPhone, but it uses WebKit instead of Gecko.

Chrome on iPhone is Chrome on iPhone, but it uses WebKit instead of Blink.

The reason this is important for you to keep in mind is because Firefox is whatever Mozilla says Firefox is, and Chrome is whatever Google says Chrome is. There's no reason to suppose the iPhone version of some product should share any code with the Android version of the same product.

Nix is also generally run as a daemon. It doesn't have a dependency on systemd and it does run on MacOS. I think also it runs on FreeBSD in principle.

The parent poster was probably conflating NixOS and Nix. NixOS is a way of using nixpkgs to build/configure and install/upgrade an operating system based on Linux and systemd. But you are not obligated to use systemd just because you're using nixpkgs.

NixOS uses sytemd for essentially the same reason other Linux distributions do: most user environments are now built with the assumption that systemd underlies them if Linux does as well. In principle you could fork nixpkgs and make all the necessary changes to remove the systemd assumption - managing a NixOS system and hacking on nixpkgs are basically the same skillset so it's not like managing an Ubuntu system where you would have to become familiar with how Ubuntu gets built. With nixos, the command is the same whether you're building an entirely new distribution based on a custom fork or whether you're just downloading builds of the latest security upgrades. Aside from the actual energy it takes to maintain a second system manager, you would only have to wait for the builds to complete rather than learning how to build everything. But so far no-one who has tried that has got enough traction - the cost-benefit just isn't there. Honestly, I think this is part of the reason people are offended by NixOS in particular using systemd: it feels like it should be possible for you to remove the systemd dependency, but you haven't done it.

The change in discussion quality has occurred because old Twitter had an objective to cultivate one particular quality of discussion, and Musk Twitter has an objective to cultivate a different quality of discussion. These goals were stated up front by the respective decision makers. Any particular technique is simply a tool for the job. If old Twitter or new Twitter thought a method would aid in their quality cultivation goals, then they would have adopted it: if it proved counterproductive, then they would drop it.

So there is almost certainly a correlation to the boost that is given to comments. But even if it is a causative correlation, the ultimate cause is not the bluecheck boost, but the desire of the decisionmaker.

It's much easier to label buttons when you work for a small company, because you know exactly who does what and exactly who is responsible for labelling the buttons and you know exactly what's going to happen to you when you label them, so you just do it and have that debate whenever it happens. Bystander effect, etc.

How is this not a breach of the constitutional protection for the right to freedom of assembly? A caucus, in particular, is literally an assembly. Surely for elections to be free and fair, the private associations who put forth candidates should be able to freely determine who those candidates are.

"Tire" and "curb" were once the normal spellings in the UK; "kerb" is an innovation whereas "tyre" is either an innovation that is coincidentally the same as an archaic spelling, or the restoration/repopularisation of an archaic spelling. The spelling "kerb" upsets me whenever I see it because it's clearly referring to the curvature of the kerb, but fortunately I almost never see it.

Likewise, spellings like "programme" are deliberate changes to mimic the French spelling. These have been rather more successful than they have any right to be, but some have completely failed (like "gramme") and a lot of people still use the older spelling.

-ize, also, used to be the standard spelling with -ise an alternative also found in the UK. In this case, it's clear that an understanding that -ize is used in the US and -ise is used in the UK became an understanding that -ize is the US spelling and -ise is the UK spelling which raised its currency. But I think they both remain in use in the UK (-ise has more-or-less chased out -ize in Australia though).

-or spellings like "honor" and "color" were once much more common in places where they are now rarely seen and vice versa. To an extent they follow the same story as -ize/-ise, with the US standardisation of one chasing its use out in the UK. In Australia, -or was much more common (than now) when the power to distinguish oneself from was the UK, but now that the main power one needs to distinguish oneself from is the US, -our has chased it out except in the name of the Labor party (because the paperwork was filed by someone who happened to prefer the shorter spelling in a time when both were current) and some uses of "honor" that are literally etched in stone. (The last general use was until about the year 2000, by "The Age", a Melbourne newspaper which used -or as its house style, but by then it was seen to be improperly American and they switched to -our.)

Generally, spellings and spelling variations remain open and subject to gradual change in all English-writing countries.

I don't think they're concerned so much by the people who don't know what a flat is, but by the people who do. There's more than a handful of bookreaders out there who are very protective of any difference between their national form of English and some other national form of English, who will get upset if a local publisher uses the foreign form.

How can you trust any company you pay to stay up even if you are their customer? I've used discontinued products before. Paid subscriptions to companies that merge with others and the service no longer really exists.

Me too, I wish the companies would obey the law without putting in the consent banner. It's not like there's any law obliging them to put in the consent banners. They freely chose to piss us all off even though they had the alternative of behaving like perfectly profitable pre-internet businesses and ... not tracking us.

Generally speaking ink printers are regarded as a decent option for someone whose printing is predictable. Its the people who print a bunch this week and then nothing for a month or so and then another burst, who benefit from laser printers, because there's no ink to dry up. It's not that hard to find yourself in this "sweet spot" where neither print shops nor ink printers are good value for money especially if you live in a country where bureaucracy is still paper-based.

Instead of directly exposing the server to the internet, you could keep it behind a VPN. That way you only need to keep the VPN secure, the VPN serves as a whitelist.

> Permanently losing access to an account sucks a lot.

But mostly that's all. Usually it's a minor inconvenience. Occasionally it sucks a bit. Rarely it sucks a lot. Almost never is anything of value lost. It can be wholly eliminated by good data practices e.g. backups. (No one backs up their Amazon account data. It isn't designed for it. Because the "webdevs" think of the data as their boss's - squarequoting "webdev" because the effective decision is the CEO's and the "webdev" is just taking some abstract, ill-thought-through decision and making the ramifications concrete.)

On the other hand, it also sucks a lot when your gratuitously collected private information is taken to the darkweb. As countries become more accustomed to dealing with databreaches, they are beginning to consider legislating harsh compensation requirements and painful fines. Once that's happened, almost all of the private data that the user has in their account? Let the user keep it. We webdevs and our mortal enemies in business/sales/product will have to innovate new decentralised databases - where each node is a users' computer. And yeah, some things will be harder or not even possible (for the user). Other things will become possible that aren't at the moment (for the user). And at least you won't go bankrupt when a state level actor decides your database is valuable.

It's completely correct. You can follow say @[email protected] from an account on say mastodon.nz.