u/QebApps

Nvidia ha presentato RTX Spark: SoC ARM, CPU Grace a 20 core, GPU Blackwell di classe RTX 5070, fino a 128 GB di memoria unificata. Sulla carta è la cosa più vicina ad Apple Silicon mai vista su Windows.

Il nodo, secondo me, è che Apple ha fatto funzionare la transizione perché controllava hardware, sistema operativo, toolchain e Rosetta 2. Nvidia controlla solo il chip. Il resto dipende da Microsoft (Prism) e dagli sviluppatori.

Windows on ARM ci prova dal 2012 (Windows RT, poi Windows 10 on ARM, poi Copilot+ con Snapdragon X) senza mai sfondare davvero. Cosa cambia stavolta?

• Il peso di Nvidia e di CUDA basta a convincere gli sviluppatori a compilare nativo?
• L’emulazione x86 è ormai “abbastanza buona” o resta il collo di bottiglia?
• Chi lo compra: gamer, creator o chi fa AI in locale?

Chi ha già usato Windows on ARM (Snapdragon X o simili), com’è l’esperienza reale oggi?

I've been thinking about where the big 90s technologies were actually created, and nearly all of them came from Unix boxes rather than Windows PCs.

The web was born on a NeXTcube: Berners-Lee wrote WorldWideWeb, the first httpd, HTML and HTTP on NeXTSTEP. Mosaic came out of NCSA on X Window. Linux was developed on Minix. Python started on Unix workstations. Java came from Sun's Green project on SPARC machines. PHP began as CGI scripts on a Unix web server, and Apache followed. Even Doom and Quake were written on NeXTstations and cross-compiled for DOS.

On the Windows side, the notable things I can think of are Visual Basic (1991), Delphi (1995), DirectX (1995), Unreal Engine (1998), Napster (1999) and XMLHttpRequest, which Microsoft created for Outlook Web Access in IE5. Apart from Borland, Epic and Napster, that's almost all Microsoft itself.

My guess at why: universities and research labs ran on Sun, SGI, DEC and NeXT workstations with native TCP/IP, compilers and source code at hand. Windows was a desktop environment on top of DOS until NT arrived in 1993, with paid dev tools and no serious shell. If you were building foundations, you used a workstation; if you were selling to end users, you targeted the PC, because that's where the market was.

What am I missing? Anything significant from that era that was genuinely born on a Windows PC outside Microsoft?

Sto muovendo i primi passi con opencode usando Qwen3.8 27B in locale via MLX, e vorrei capire se il setup è sensato o se sto sbagliando qualcosa di grosso.

Come prima prova gli ho dato un task semplice: scrivere un post breve, fornendogli due post precedenti come esempio di stile e un elenco di cosa è cambiato nell'ultimo mese. Poi ho dato lo stesso identico prompt a Claude.

Il risultato è stato molto simile in qualità. La differenza è nei tempi: opencode in locale ci ha messo circa un'ora, Claude 33 secondi.

Hardware: MacBook Air con chip M5 e 32GB di RAM unificata.

So che il confronto non è alla pari ma un fattore 100 mi sembra troppo, più sintomo di un problema di configurazione che di un limite fisiologico. Qualcuno con setup simile ha riscontri sui tempi? Suggerimenti su quantizzazione, dimensione del contesto o scelta del modello?

Grazie a chi vuole condividere la propria esperienza.

I've been releasing an update to my RSS reader, Newsairy, roughly every week since May - that's around 17 versions in a bit over three months. From the outside "weekly releases" can look like recklessness, so I wanted to share the part that actually makes it work: at any given time I have three versions moving in parallel.

• The version I just shipped is in the App Store.
• The next one is already in TestFlight, in testers' hands.
• The one after that is in alpha, or still being built.

By the time a version reaches the App Store, it's already had a full beta cycle behind it - the pace of releases is fast, but the pace of testing per version isn't compressed at all. It's just running three lanes at once instead of one.

The trade-off I keep thinking about: users get to see progress constantly, which I like - feedback loops stay tight, and nothing sits finished-but-unshipped for weeks. But it also means every week I'm context-switching between "polish this for release," "watch how testers use that," and "is this new idea even going to work" - which is its own kind of tax.

Curious how others here think about this. Do you deliberately stagger releases like this, or find it more sustainable to batch bigger releases less often? Genuinely asking - I don't think weekly is obviously "right," it's just what's worked for me so far.

https://preview.redd.it/vxqfgukte4lh1.jpg?width=3200&format=pjpg&auto=webp&s=11c9766fa2c5d274ab4fc23e6e22766c11d722f4

I built Newsairy because none of the readers I tried fit me exactly - so the whole app is built around adapting to how *you* read rather than making you adapt to it: theme, font and size in the reading view, sort order, swipe actions, all yours to set.

It's under active development. I ship updates roughly weekly, and next up is more control over the list's layout and density itself. There's a public roadmap if you're curious where things are headed.

Answer - What problem does it solve?

Newsairy is an RSS/Atom/JSON reader that syncs natively over iCloud across iPhone, iPad and Mac - no third-party sync server, no account to create. It's for anyone who wants their feeds, folders and read state to just follow them between devices, with a reading experience they can actually tune to how they read.

A few things I built specifically because I couldn't find them elsewhere in one app:

• Smart Feeds for the last 24 / 48 / 72 hours, the last 7 days or this week, so I can catch up on what's actually recent
• Custom Smart Feeds: keyword-based feeds that gather matching articles from every source at once
• Read History, sorted by when you read them, for when you remember reading something and can't find it again
• Three independent retention rules (how far back to fetch, how long to keep unread, how long to keep read) instead of one blunt "delete after X days", so the database doesn't grow forever
• Choose your theme: Automatic, Light, Dark or Sepia
• A fully customisable article list: thumbnail size, favicon, unread dot, and 0–6 preview lines
• Flexible sorting: sort any list Newest first, Oldest first, or as a Daily timeline

Privacy-first: no ads, no tracking, no third-party analytics.

Better - Why is it different?

There are a lot of good RSS readers in the App Store.

My previous ones were Reeder (Classic) and NetNewsWire. While the newer Reeder seems to focus on combining RSS with other kinds of sources, like social media and podcasts, Newsairy is more focused on RSS feeds specifically.

NetNewsWire is great and free - I'm not trying to beat that on price. Newsairy is just a different flavor: I built it for the features and customization I wanted - keyword-based Smart Feeds, a Sepia theme, an article list you can tune (thumbnails, preview lines, unread dot), and more. If none of that is something you're missing, NetNewsWire is a solid pick.

Cost

Free: up to 6 local + 6 iCloud feeds, every feature unlocked.

Newsairy Pro is a single one-time purchase - $2.99 / 2,99€, no subscription - that removes the feed limit and adds sync with TheOldReader, Miniflux, FreshRSS, Feedbin and Inoreader, so you can bring an existing setup over instead of starting from zero. Pay once, it's yours.

----

App Store: https://apps.apple.com/us/app/newsairy/id6760046985

More info: https://qebapps.statichost.page/newsairy

I'm in the middle of moving from an old Intel MBP to a new MBA with M5, both on macOS 26, sitting side by side on the same desk.

At some point I noticed the cursor on the other machine was moving. 🤯 Then I realised I was steering it with the trackpad of the first one. I genuinely thought I was losing my mind for a few seconds, so I stopped and tested it properly - and yes, one trackpad, two Macs, pointer sliding from one screen to the next like they were a single machine. Same for the keyboard. Not screen mirroring, two real Macs!

Turns out this is Universal Control, it's been around since Monterey, and it's on by default (Settings → Displays → Advanced). This is the first time I've had two Macs on the same desk, so I'd simply never run into it.

A quick search filled in the rest:

• both devices need to be signed into the same Apple Account, with 2FA
• Bluetooth, Wi-Fi and Handoff on, and the two within about 10 metres
• the macOS versions don't have to match - anything from 12.3 up works, so an old Intel Mac and a brand new one get along fine
• it also works with an iPad, and with up to three devices at once

You can drag files straight from one screen to the other as well, which is quietly making this migration a lot easier than I expected.

I'm in the middle of moving from an old Intel MBP to a new MBA with M5, both on macOS 26, sitting side by side on the same desk.

At some point I noticed the cursor on the other machine was moving. 🤯 Then I realised I was steering it with the trackpad of the first one. I genuinely thought I was losing my mind for a few seconds, so I stopped and tested it properly - and yes, one trackpad, two Macs, pointer sliding from one screen to the next like they were a single machine. Same for the keyboard. Not screen mirroring, two real Macs!

Turns out this is Universal Control, it's been around since Monterey, and it's on by default (Settings → Displays → Advanced). This is the first time I've had two Macs on the same desk, so I'd simply never run into it.

A quick search filled in the rest:

• both devices need to be signed into the same Apple Account, with 2FA
• Bluetooth, Wi-Fi and Handoff on, and the two within about 10 metres
• the macOS versions don't have to match - anything from 12.3 up works, so an old Intel Mac and a brand new one get along fine
• it also works with an iPad, and with up to three devices at once

You can drag files straight from one screen to the other as well, which is quietly making this migration a lot easier than I expected.

I'm moving from an old Intel MacBook Pro with a 2 TB drive to a new MacBook Air (M5, 1 TB), and I'm trying to decide how to set it up.

My first instinct is to NOT use Time Machine or Migration Assistant. A few reasons:

• The drives are different sizes. My old 2 TB is almost full, so it wouldn't even fit on the new 1 TB anyway.
• My most-used project folders are all under git, in repositories on my NAS or in the cloud, so those are easy to bring over. I just clone them again.
• Honestly, it also feels like a good excuse to get rid of a lot of stuff I don't use anymore. Years of apps, files and leftovers I keep saying I'll clean up and never do.

So the plan would be to set the Air up from scratch, reinstall only the apps I actually use, and copy over just the files I need by hand. I'm also going from Intel to Apple Silicon, so I figured a clean start might be cleaner anyway.

Is this a good idea, or am I underestimating how much of a pain it is to rebuild everything manually? For those who did the same, is there anything you wish you had migrated the normal way instead of doing it by hand? Any hidden stuff that's easy to forget?

Thanks

I'm an indie dev with a small iOS app, and I keep a press kit: a simple web page with screenshots, a feature list, version history and so on. Every time I ship a release I go and update it, and lately I've started wondering whether that effort is actually worth it.

Here's my current one for context: https://newsairy.github.io/presskit/ (and the app site, if useful: https://qebapps.statichost.page/newsairy/). Honest feedback on either is welcome too.

So I'd love to hear how you handle it:

• Do you keep your press kit updated with every release, or just once in a while?
• Does anyone actually use it? Have you ever had a journalist, blogger or reviewer pick something up from yours?
• Or is a press kit basically pointless these days, and I'm polishing something nobody looks at?
• If it does help, who do you actually send it to? Review sites, YouTubers, newsletters, individual writers?

Just trying to figure out where to put my limited time. Curious to hear your experiences, thanks!

I'm a developer, both at work and as a hobby, and context switching is becoming my biggest problem.

At work I write code, but I also have meetings at fixed times and constant interruptions from colleagues, so I'm always jumping in and out of focus. In my free time I have my own side app to take care of: marketing, user emails, a bit of research, coding. Every switch has a cost, and by the end of the day my head is all over the place.

Is there an iOS app that could actually help with this? I'm not even sure which category it falls into: focus, task manager, notes, something that pulls everything for one "context" into one place. I know iOS has Focus modes but I've never really set them up, so maybe I'm missing something obvious.

Curious to hear what you all use. Thanks!

I have -Xfrontend -warn-long-function-bodies=275 set in Other Swift Flags, and one of my views recently tripped it hard: the body came in at around 506ms. Compile times were getting annoying.

I did not rewrite anything. I just pulled pieces out of body into separate computed properties: the main content, the transition, and the sheet modifier. Same code, same behaviour, just moved out of body.

The warning went away.

What surprised me is that there was no single monster expression to blame. body was just long, and the type checker seems to struggle with the accumulation rather than with one specific line. What helped was extracting one piece at a time and rebuilding, instead of refactoring the whole view at once.

So now I am wondering about the threshold itself. 275 is just the first number I tried. Too low and you drown in warnings on a big project, too high and you only find out when builds are already painful.

What do you use, and did you land on it deliberately?

I have two apps on the App Store, both small, both mine alone.

Every time an update is ready I get this knot in my stomach. In fact it starts in App Store Connect, filling in the version, the what's new, checking the screenshots for the third time. I don't know why that part gets me. Maybe because it's the only part where a mistake is public and stupid rather than technical.

The funny thing is I test, I have unit tests, I have beta testers who have been on the build for days and told me it's fine. I use the app myself every day. Rationally I know it's fine. I still sit there staring at the button.

Is it just me? Does this go away with time, or do you just get used to it?

Heard rumors about possible price hikes, so I pulled the trigger on a Sky Blue MacBook Air without ever seeing the color in person. Went to an Apple Store afterward just to check, and luckily I'm in love with the color.

Delivery estimate is early August, though. In fact I went with 32GB RAM and 1TB storage instead of the base config. Anyone know if there's a decent chance it ships earlier than that, or should I just settle in for the long wait?

Hey everyone,

I'm a solo developer, and over the past few months I've been building Newsairy, an RSS reader for iPhone, iPad and Mac — mostly to fix a personal pet peeve. I follow a lot of feeds, and every reader I tried was missing at least one thing I wanted, so I'd end up either drowning in an endless unread list or missing what actually mattered. I wanted a reader that adapts to me, instead of one more I have to adapt to.

A few things I focused heavily on:

Smart Feeds: group your articles by time — Today, Last 24 / 48 / 72 hours, Last 7 days, This week — so you can catch up by recency instead of scrolling forever.

Custom Smart Feeds: build your own keyword-based feeds that gather every matching article across all your sources.

Flexible reading: sort any list Newest first, Oldest first, or as a Daily timeline; pick a theme (including Sepia); customise the article list and the reading font/size; and find things again in Read History, sorted by when you read them.

Privacy-first: no ads, no tracking, no third-party analytics.

iCloud sync, no account: feeds, folders and read/unread state stay in sync across iPhone, iPad and Mac using your own iCloud — no sign-up, no separate account.

It's free to try with up to 6 local + 6 iCloud feeds. A single one-time purchase (no subscription) removes the limit and unlocks sync with TheOldReader, Miniflux, FreshRSS, Feedbin and Inoreader, bringing your existing subscriptions, read state and starred items with you.

This is a Discussion post as much as a share — I'd genuinely like to hear how you deal with RSS/news overload: do you lean on time-based catch-up, keyword filters, folders, something else? And what's the one feature your ideal reader would have that most apps get wrong?

Home page

App Store

Quick update on Newsairy, the iCloud-native RSS reader I've been building. Version 1.07 adds Inoreader sync — one of the most-requested aggregators since I started.

You all know the drill, so I'll spare you the spiel: full two-way sync across iPhone, iPad and Mac, OAuth login. I mostly added it as the native, no-nonsense companion for people who already live in Inoreader on the web.

I didn't post here about 1.06, so to catch up: it added a Font & Size panel for the in-app reader — pick the typeface (a curated set, or any font installed on your device) and either follow system Dynamic Type or set title size, body size and line spacing by hand. Search also got much faster and no longer freezes the list, even with thousands of articles.

A couple of things already in the pipeline, if you're curious: 1.08 ("Reading Flow") adds Last 7 days / This week Smart Feeds, per-feed and per-folder Mark All as Read, and article sorting — including a Daily timeline that reads each day oldest-to-newest. Then 1.09 brings Mark as Read on Scroll — which is on the roadmap because a couple of you asked for it right here on r/rss — plus cover images for feeds (Ars Technica and the like) that only expose them via media: tags rather than in the article body. Full roadmap's on the site.

For anyone who hasn't come across it: Newsairy syncs over iCloud across iPhone, iPad and Mac, and Pro adds sync with TheOldReader, Miniflux, FreshRSS, Feedbin and now Inoreader. One-time purchase, no subscription, no ads, no tracking.

I have a long todo list, but I'm always open to suggestions — if there's a feature or a use case you'd like to see, let me know.

App Store