Urgent.News

What's breaking now, across thousands of outlets.

Tech

Here’s the likely reason the iPhone Ultra isn’t getting an Apple Pencil

A report yesterday suggested that Apple considered making a special version of the Apple Pencil for the upcoming iPhone Ultra before deciding against it . Bloomberg suggests that there are three reasons behind this decision, one of them being a desire not to conflict with the position adopted by Steve Jobs when launching the original iPhone. However, this was almost certainly not the deciding…

Here’s the likely reason the iPhone Ultra isn’t getting an Apple Pencil

A report suggested that Apple contemplated a specialized Apple Pencil for the upcoming iPhone Ultra, only to abandon the idea. Bloomberg cites three reasons for this decision, with the third factor being the most likely cause. Steve Jobs' original iPhone launch stance might have played a role, but conflicts were likely not the primary consideration. Apple's reluctance to compromise the display's durability on a folding iPhone is the most convincing reason.

Written by urgent.news from 9to5Mac's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at 9to5mac.com →

More in Tech

bibliograph: An AppView for interfacing with bibliographic information on ATProto

An ATProto AppView that provides information about books for other apps to build on top of. First user of it is https://livtet.olamaelcu.net/ Comments

  • Bibliograph is an open-source appview for ATProto bibliographic info
  • Uses methods like book review search and TAP ingestion for discovery
  • Prometheus monitoring available at http://localhost:9090 with 7-day TSDB

Meilleures pratiques de gestion des erreurs des API REST : Codes d'état, RFC 9457 et erreurs réessayables

Concevoir un contrat d’erreur robuste pour une API REST Les réponses d’erreur de votre API font partie de son contrat. Les clients les analysent, les mécanismes de réessai s’appuient sur elles et les…

  • Use appropriate HTTP status codes for error responses, not body content
  • Follow RFC 9110 families: 4xx for client errors, 5xx for server errors
  • Indicate retryability and avoid sensitive information leakage in error responses

More from Monday 31 August →