sethaurus

The first `await` is waiting for the response-headers to arrive, so you know the status code and can decide what to do next. The second `await` is waiting for the full body to arrive (and get parsed as JSON).

It's designed that way to support doing things other than buffering the whole body; you might choose to stream it, close the connection early etc. But it comes at the cost of awkward double-awaiting for the common case (always load the whole body and then decide what happens next).

That was once the case, but no longer. Third-party WatchOS apps can work without a phone present, up to being installed directly from the watch's app store. They can definitely do independent networking, but there are still some restrictions, eg they can't do it when backgrounded, and websockets are pretty locked down (only for audio-streaming as per Apple policy).

I reckon the lack of general-purpose websockets is probably the issue for a system based on Phoenix LiveView.

Dependencies and code are both liabilities with maintenance costs. Devs chronically underestimate the cost of both, myself included.

Other than quibbling over the word "template", how does that differ from what TFA is describing?

You've misunderstood. The parent was making a specific point — if you want an SVG of a penguin, the easiest way to AI-generate it is to get an image generator to create a (vector-styled) bitmap, then auto-vectorize it to SVG. But the point of this benchmark is that it's asking models to create an SVG the hard way, by writing its code directly.

Yes, preventing the app from running in the background (entirely) would prevent it from listening on a port and collaborating with websites via this exploit.

As for the second part: no, logging out of the apps would not necessarily be enough. The apps can still link all the different web sessions together for surveillance purposes, whether or not they are also linked to an account within the app. Meta famously maintains "shadow profiles" of data not (yet) associated with a user of the service. Plus, the apps can trivially remember who was last logged in.

These days that's pretty well-supported in the base language:

    const updated = { ...existing, someKey: someNewValue };

You mention nesting. That starts to look messier:

    const updated = { ...existing, someKey: { ...existing.someKey, ...someNewValue } };

There's a whole cottage industry of little libraries to make this ergonomic/fast in the general case (copying immutable objects with nested changes). `immer` is a popular choice. But the reality is that it gets complicated to do this generically; in my view it's usually better to just use the base language where possible, even if it means sprouting some util functions for the various kinds of updates you end up doing.

Apologies if I'm missing a joke, but Pocket used to be called "ReadItLater". Instapaper still exists and I imagine they're about to get an influx of Pocket refugees.

At the risk of unbearable pedantry, there's never been an iPhone 9. (There was never a 2 either; there was kind of a 3, although it was really called the 3G.)

For anyone finding em-dashes too small, behold the majesty of U+2E3B, the triple-em dash: ⸻

It's transport-agnostic in the sense that it works locally (over stdout), not just remotely. It's not just for web-services. That's why HTTP isn't baked into this.

> What happens in this C proposal if you put a defer request inside a loop? Is it a compile time error, do they somehow to try to give it meaningful semantics, or is it undefined behavior?

The action runs at the end of the loop-body, before the next iteration. It does this because the loop-body is the enclosing block, and a defer will always run when its enclosing block ends. As described in the article, this is intentionally-so and makes it possible to acquire a mutex inside a loop while automatically releasing it before the next iteration, something which is easy to get wrong in Go.

VC-funded startups go out of business because they are unable to grow fast enough.

Bootstrapped startups go out of business because they are not profitable.

As a customer, knowing that a vendor is already profitable and sustainable is a big green light.

Forgive me for being obtuse, but what exactly are you claiming here? Are election results being faked?

That's true of the compilation step, but type-checking always uses `tsc`. They're no TS spec, so it's very hard to build a fully-compatible competing implementation. Erasing the types syntactically is a lot easier.

At that time, what would have been the distinction between "programmer" and "developer"?

I'm struggling to understand how this is a bad look for Typescript. Do you mean that the specific choice of Go reflects poorly on Typescript, or just the decision to rewrite the compiler in a different non-TS language?

If it's the latter, I think the pitch of TS remains the same — it's a better way of writing JS, not the best language for all contexts.

There's a quite comprehensive list of them here:

https://github.com/GSA/govt-urls

This is the core trick in the Fast Inverse Square Root[0], as made famous by the Quake III source code.

It uses a shift (equivalent to dividing) and a subtraction in integer-land to estimate x^(-0.5) in float-land.

[0]: https://en.m.wikipedia.org/wiki/Fast_inverse_square_root

> Why is the option to use the AirPods in “normal” mode being removed?

I'd challenge the idea that off/passive really is the "normal" mode, from the ordinary user's POV or Apple's POV. The headphones just don't sound good in this configuration, with neither the background nor the audio sounding clear. They aren't engineered to give good sound isolation OR good background pass-through without active support, and until this post, I didn't even realize that the active modes use more battery life.

The messaging to users is also unclear. Without understanding how ANC works, what does "off" actually mean? It's not turning off the audio playback, and it's not turning off the background noise. It IS however turning off the (newly-advertised) active features like Loud Sound Reduction, which users would expect to be working whenever they are wearing the headphones (or at minimum, whenever music is playing).

In typical Apple style, it makes perfect sense for "off" to be treated as an advanced feature; the problem is that they already shipped it a long time ago, and then removed it without any explanation.

It's always fascinating to discover a comment on Hacker News arguing against using network services in any way without the written permission of their owners and operators. We'd have a very different internet today if people had been following this advice for the last 30 years. A much worse internet, to be clear.

What are the typical password requirements in the Chinese and Arabic writing worlds? Given how rarely English-first websites even accept non-ascii characters within passwords, I honestly have no idea.

Those of us who find calorie-counting easy and effective are the blessed few. Most people appear to find it even harder than other behavior-change approaches to weight management.

From a legal point-of-view, yes, Reddit had control of the data and chose to alter the deal. And the app developer did have an exit plan: shutting down the app and refunding subscribers. The developer appears to have weighed his options, considered the strategy Reddit was communicating with the rollout of their API changes, and concluded that this was no longer a viable market.

Many people expressed strong opinions about what the developer should do, but he appears to have remained calm and rational throughout the experience, and chose to walk away when it made sense.

However:

> The content is what the users wanted - and Reddit had the content...

> ...in exchange for Reddit's content...

> ...operating businesses based on someone else's data (moat)...

Let's not fool ourselves: the data was created by and for the users, and it never belonged to Reddit in any moral sense. It's a regrettable externality of our legal framework that Reddit was able to withdraw their free API and prevent the community from accessing its own data how it saw fit.

How does one pass a lambda to a CLI tool? Outside of using a regex or equivalent pattern syntax, I'm struggling to understand what you are proposing here.

For anyone else unfamiliar with this initialism:

> Cost of goods sold (COGS) refers to the direct costs of producing the goods sold by a company. This amount includes the cost of the materials and labor directly used to create the good. It excludes indirect expenses, such as distribution costs and sales force costs.

You've gained the convenience of not round-tripping through your email client every time you want to login/authenticate with the service!

The same is true of passwords, of course; if there's an email-based password-reset mechanism, then your email is your real proof of identity; the password is a shortcut.

Passkeys are a shortcut too; they just pick a different set of tradeoffs (less portable, less user-visible, more secure, harder to get phished, less stuff to remember). IMHO, these tradeoffs turn out to better-match the threat model of the modern web.

> IVR menu

i googled this; looks like it means "Interactive Voice Response" menu, describing automated phone systems where the user navigates a series of options using either their phone buttons or their voice.

This is very common feature of rich-text (and markdown) editors. GitHub comment boxes do the same thing even though they are not WYSIWYG. Confluence and Notion do too.

The grandparent is implying that "Taylor Swift" and the "Evil Manager" are two sides of the same coin; they don't need to even be different people. The system lets a (big) artist extract value while keeping their public image clean. It's a shell game, and Ticketmaster plays the role of bad-guy-as-a-service.

Of course, their insane monopoly means they also get to take advantage of smaller artists, venues etc. None of this is good.