HN user

veltas

1,762 karma

veltas.co.uk

Posts12
Comments722
View on HN

The original joke for anyone who doesn't know or remember, Michael, the manager, asks his accountant to explain what a surplus is like he would to an 8 year old. Michael doesn't understand this and asks for how he would explain it to a 5 year old, which Oscar does a very good job with explaining and Michael finally understands.

Later the security guard is called upstairs to break a tie on votes for what to spend the surplus on, and Michael starts reciting Oscar's 5 year old explanation, and the guard cuts him off saying he knows what a surplus is.

I have to imagine this is sort of a joke about the audience too as inevitably the writers were considering that audience members might not know what a surplus is, and this kind of joke is an opportunity to explain it.

My young children both love the lawn and I can tell they get a lot from interacting with it, playing on it, etc. It is a little bit of accessible greenery in my small back-garden and I don't need to water it, just mow it occasionally.

With standards it helps to reconcile existing behaviour, rather than create new unproven syntax.

Likewise creating a new syntax for something that already exists means you are just adding to the heap of stuff that needs support on mainstream servers, and as I already said it will probably create compatibility issues as the old deprecated/illegal syntax is removed. This is unnecessary friction.

And really what is the advantage of a new syntax? That needs explaining.

The other issue with adding a separate supported way to do what people did with GET+body is that we will probably see servers slowly drop support for the GET+body approach when QUERY gets widespread support/usage, and then a ton of other stuff will break.

Unless you're really going to improve things or the existing practices are really too painful, standards should follow convention. Even though GET+body is not handled the same everywhere, it's easier to make that the standard than it is to make a new syntax the standard.

Deno Desktop 1 month ago

Last time I checked there's a small industry of gstreamer contractors, so it's not that simple.

As a consumer who has only tried honest chargebacks within their 'consumer rights' and has never won them, apparently you can fight them, and apparently companies deem them worth fighting.

There is this weird attempt to claim YouTube isn't social media from Google and others, but it's literally called "You Tube". It was designed as social media from the start, it's impossible to separate this without changing the name and everything about how it works except the films and series available to pay for.

To be clear: they are not shadow puppets at all, they are not being displayed in the traditional way, but they are being captured with a camera.

In many scenes characters entirely change their shape in a natural or fluid way, because the cut-outs are being wholly replaced with different cut-outs from frame to frame, to simulate a natural/fluid motion. This is one of many techniques used in the film possible with stop-motion animation and impossible with shadowpuppets.

I watched the film and was quite impressed with the animation techniques used, although this isn't really novel but not because of puppets, animation actually goes back much further than film. It's a beautiful film though, and I can see why people preserved it.

https://www.theguardian.com/artanddesign/jonathanjonesblog/2...

I like to think there's a solid argument against dark forest that even if you can destroy other intelligent systems, then hidden intelligent cautious systems may exist and see evidence of what you've done, so there's a potential consequence to destroying every intelligent system you identify.

And then also (maybe this is absurd) isn't there something intrinsic in intelligence to want to avoid conflict and desire peace?

Lowering demand doesn't always lower price. Assuming the industry is competitive, and capable of supplying all demand, which it usually is, the loss of demand mostly means less money for the producer, and more money for the former consumer to spend on something else.

Very nice work for how small the source code is, and this is a relatively good design for the language.

I will say to criticise that I started scratching my head when I got to the standard library. The functions should really just be C's standard library. I know there's lots of baggage but e.g. remembering that 'print(s)' will print with a newline and 'printn(s)' won't, this is just putting a barrier to entry that's not necessary. Sure, have some new functions for slices, but if you can help it use more conventional names from C.