orangea

It probably has more to do with the fact that formalizing chess in such a way wouldn't be particularly interesting. Chess is mostly studied because of its historical significance, and if you change the rules then the game no longer is as connected to its historical significance.

I mean... is it not obvious that in a he said she said scenario like this they have to simply side with the buyer? I struggle to understand your mentality, assuming that you have no way to prove (to Amazon or to a court or whatever) that their negative feedback was fraudulent.

The first half of the article says "namespaces, cgroups, and seccomp aren't 'security boundaries' because if the kernel had a bug it could be used to escape from a sandbox". Then in the second half it says "use gvisor and do all this other stuff to avoid these problems." This presentation feels kind of dishonest to me because the article avoids acknowledging the obvious question: "well what if gvisor has a bug then?" I mean, sure, another layer of sandboxing that is simpler than the other layers probably increases security, but let's not pretend like these are fundamentally different approaches.

If the successful people you meet in real life are nice and you see lots of meanness on the internet, it probably just means that anonymity causes meanness.

We already know many useful things to do; there are already 10,000 startups (9789 out of YC alone, 4423 of which are coding-related) doing various ostensibly useful things.

I don't think you meant "ostensibly".

See also, for comparison: https://www.val.town/

Learning homological algebra is a long way away from learning about varieties and ideals in any sensible order in which to learn material. You have to do a lot of work in between in order for homological algebra to seem motivated. Sounds like you ought to try an introduction to algebraic topology.

Why not read the source and decide for yourself? Here's a blog post linked in the article, as a start: https://world.hey.com/dhh/as-i-remember-london-e7d38e64

Well, dhh considers torrents outdated (I’m not kidding, check the tweet), so it’s only officially being offered as a single download from a Cloudflare server. Which sounds cool until you’re on a weak-ass connection in constant danger of dropping halfway through the download.

That has nothing to do with bittorrent vs http; use a download manager instead of a browser.

Asahi is useless to me, and I would assume many others, without USB-C display support.

Don't you think that the vast majority of dangerous human drivers would be perfectly capable of changing their behavior during a driving test? Even without any malicious intent most people would be more careful during a test.

targeted specifically high ticket items (jewelry, luxury)

My immediate instinct upon reading this is "of course those businesses wouldn't be interested". They are selling a brand and image first, and if it looked like they wanted people to download some new app and put in their bank details to make a purchase instead of swiping a credit card it would cheapen the brand. Luxury stores are all about a streamlined experience and the appearance that money is no issue.

At least this is a topic that the average HN reader is likely to be able to understand and which is closely related to software. Several years ago there was a period where there were periodic posts about things like homotopy type theory and research-level algebraic geometry which inevitably spark only inane misunderstandings and uninformed speculation in the comments. I can only attribute it to some kind of fetish for the frontiers of pure math.

When something costs $1/year, the primary barrier isn't being able to afford it, but having a valid payment method. Depending on the requirements, it can be an issue if you don't have a credit card, don't have a bank account, etc. And not having those things is slightly correlated with poverty. In addition, it makes it harder for children to sign up (not necessarily a bad thing, just saying).

- Doesn't allow installing multiple versions of packages at the same time

- In practice, requires being installed to /usr/local

- Hard to uninstall in practice, leaves files scattered behind

On the other hand, the F key has a bump on it on every keyboard I've recently come into contact with, which could provide an anchor.

I suppose with ESDF you have the two keys Q and W where otherwise only tab would be.

You could also just find a way to rebind caps lock, which would accomplish more or less the same thing.

Another bought a laptop by taking out a stablecoin loan on a DeFi platform when no bank would lend to him.

Could someone explain this to me — I thought that loans on cryptocurrency platforms had to be collateralized by cryptocurrency? How could someone buy a house with a crypto loan if they didn’t already have enough to buy one in the first place?

That is almost certainly possible with github actions.

IMO symbolic math is Mathematica's strength and I wouldn't recommend it unless you are using it for that.

If you use open source you are accepting the license that says that there is no liability.

The article directly contradicts this:

What if an open source project is used directly by consumers, and causes them harm? The public policy is clear: they must be compensated. Does it matter if they signed a license or didn’t pay someone? Their business is bankrupt, their files are in a hacker’s hands, or their own customers are suing them. Someone should be strictly liable.

- Truly open source, presumably without the caveats that VS Code has such as a few "features" (extensions) being closed source and the extension marketplace being closed to de-microsofted builds

- Designed from the beginning to support an extension API with a richness comparable to VS Code's (unlike Sublime, Jetbrains etc)

- Presumably aiming to put performance as a higher priority than is usual

In the "on top of WASM" case, I imagine that the advantage of Python and JS will be exactly the same as the "not on top of WASM case". Namely, mainly development convenience at the cost of performance.

Here is a specific example, again using Python, of how a programming language not designed for WASM might not be ideal: suppose you are writing a Python script which is to be compiled to WASM and needs to import a function. How do you specify that in the script? There could be some Python function like `wasm_import("my_function", "u32", ["u32"])`, which allows the programmer to specify a function to be imported... and the problem with that is that in Python everything normally happens at runtime, but the compiler which is turning your script into a .wasm file needs to know in advance what functions you are going to import. So you face a dilemma: either you mess with the fundamental assumption of Python that everything happens at runtime, or you add new syntax which allows specifying metadata, or you use magic comments, or do some other hacky thing.

This might seem strange to those who are used to today's dominant WASM paradigm, where the programmer usually controls both the VM and the .wasm program — such as website developers who create a .wasm file and then also write the Javascript to load it into the browser. But one of the most exciting things about WASM, to me, is the potential for domain-specific execution environments in which the code which loads and executes the WASM is written much earlier and by a different entity than whoever writes the WASM.

When I see "powered by WebAssembly", I take it as a sign that the language is going to be designed around WebAssembly's VM interface rather than the implicit standard of the C memory model and POSIX-like API which basically all popular programming languages are designed for. Even languages like Python have the concepts of stdin/stdout/stderr, a filesystem, threads, and a single globally accessible heap baked into their design. It would take a lot of work to amend Python's design to be able to easily use features that are somewhat unique to WebAssembly like the various things a .wasm file can import or export. As it stands, languages like Python can be run on WASM, but they use inelegant hacks in order to be able to replicate the execution environment features that their interpreters require such as malloc, and usually it is assumed that the target will be WASI. A language that is designed for WASM from the ground up would make it so that WASM can be used to its fullest potential as a lightweight execution environment that makes extremely minimal assumptions about what interfaces are going to be provided to the program.

In common usage of the terms, "reference counting" and "garbage collection" are completely different.

If you got hit by one of these then you wouldn't feel anything. The energy is about 50 joules, or about 1/2 of the heat that a human body produces in a second.

Note that such a baseball with the same energy as this particle would still have much more momentum than the particle. So getting hit by the particle wouldn't "leave a bruise".

That doesn't mean getting hit by this particle would feel like a punch, since what you feel when you get punched is a transfer of momentum rather than a transfer of energy.