HN Simulatornew | past | comments | lists | submit | danudey's commentslogin

Wow, there really are people running s390x. I kept wondering why we were building images for it.

They are unbelievably fast Linux machines. I’ve never seen anything coming even close.

And speed is not even the main design goal.


Agree. I was talking to a coworker the other day and remarked that I would be pretty content if we had five years of Claude stagnating in quality/capability but reducing in price/environmental/electrical impact.

It reminds me of when Apple switched to their own silicon in the iPhones and we had year after year of hardware with 1.5-2.5x performance compared to the previous year. We very rapidly got to the point where the processor in my phone was more power than I would ever need (unless apps got more and more bloated and inefficient, which they obviously did).


> which failed because of network effects

Not to nitpick, but Windows Phone also failed because Microsoft released the first generation of devices with Windows Phone 7, convinced a bunch of people to buy them, and then released a second generation of devices with updated Windows Phone 8, a version that the first generation couldn't upgrade to meaning that anyone who got in on the ground floor got locked out immediately.

When you go out of your way* to screw the people most interested in your new product it doesn't really engender large amounts of trust in what would have been your second wave of customers.

* Well, to be specific, WP8 was based off of the NT kernel and WP7 was based off of the WinCE kernel so it was probably 'the right choice' on some level, but making the entire first generation of a new product line EOL immediately rather than making an effort to ensure those people get... something... is still a dick move.


yeah they should have had a trade in program, that would have bought them serious brownie points all around.

But Windows Phone history is a long list of things they should have done


WP7 -> WP8 was rough (as was WM6.5 -> WP7), but WP8 -> WM10 was worse... while you could upgrade WP8 devices to WM10, IMHO, it wasn't worth it. Better to support old and new until the old ones age out. IIRC, WP8 had a big spec jump (single -> dual core, ram requirements, etc), so an upgrade probably wouldn't have worked...

The final build of WM10 was actually not awful... too bad it came 2 years after launch. :P

People talking about network effects killing windows phone probably don't know about how well WP8 sold low end phones in developing markets. Of course, WM10 abandoned that part of the market ... just another thing Microsoft could have done differently. :P


I don't open my e-mail until someone tells me on Slack that they sent me an e-mail.

Honestly most of my emails are either spam/marketing emails I haven't yet gotten around to unsubscribing from, or calendar invites which I generally ignore since they sync to my gcal and thus my slack cal.

If someone sends me an email, it will not get noticed. I think this is the general culture of most places I've worked at.

But even the slack alert channels get ignored by me because they're too noisy and we haven't yet prioritized denoisifying it. We aren't dealing with critical health alerts though


As others have said, averages aren't useful unless the behavior matches the average.

If those 147 4% drops actually happened every 100 days or so then it's not newsworthy or interesting, just an occasional correction.

If those 147 days happened all in a row that would mean the nasdaq dropped to 0.25% of its original value in about 4 months, which would be catastrophic.

The real answer is presumably somewhere in the middle, but the specifics are what determines if it's worth noting or not.


I'm paying ten bucks a month and I don't want to be paying for an API I don't use. If the options are raise everyone's prices to cover the cost of the searches that an extreme minority of people want to use or ask those people to pay a little bit more for that extra functionality I think the second option makes the most sense.

You're paying ten bucks a month for access to Kagi the web search, not Kagi the search API. If you want them to provide that service and scale it accordingly it makes sense for that to be a separate feature with a separate price.


You could argue that it also includes the assistant that I’m barely using at all… Why is this included in the sub while the main reason I use Kagi is the search, and the search itself is not included if performed via an agent?


Because they made a calculation that the assistant product has broader appeal. Including either product has the potential to acquire users, and retain other users, but they think their target market has a lot more people who might enjoy using the assistant, than they do people who want a search API as a free addon. Or that someone who starts using the assistant is more valuable (due to stronger retention) than someone who uses the search API because the latter is more of a commodity that you can replace in 5 minutes if a new startup offers a cheaper option.


I mean, presumably at some level you are using the search API - it's just a programmatic interface into the same underlying database calls. I don't know if Kagi web search uses the public API directly or if they share an underlying internal API, but I imagine there's not a lot of difference on Kagi's end.

The big difference is that API usage can be scaled up way quicker than web page hits and scraping can be, which is an understandable concern if you're trying to price your service for human usage and not for bots hammering away as fast as they can. But judicious use of rate limits could help here - have a subscribers API tier that allows only a relatively low volume of calls and do standard API pricing for all requests beyond that.

That said, I'm sure there are complexities here that I'm missing that make this easier to say than to do.


> this doesn't get reasonably full access to the App Store then it's a no-go for me

From their page:

"Additional apps. HomeView supports compatible third-party audio and video apps from your iPhone for a familiar experience across devices"

This implies that Plexamp could be supported, and possibly Messenger and Snapchat calls, but it's too early to tell.

> My house has a bunch of spots on the wall where an old intercom system used to live: it'd obviously be a budget buster to buy a bunch of these to fit in those slots but even if you did, you'd need Apple to provide an intercom solution (a la the Watch's Walkie-Talkie?) or you're...out of luck.

Apple Home already provides this. It's not a full voice chat, but you can tap a thing and say something and it'll broadcast it to the rest of the house; in my case, that's two HomePods Mini, but it's easy to assume it will include this as well.

If you're just looking to say "Hey kids, dinner's ready" or "We have to leave in 15 minutes" to the entire house then that circumstance is handled already; if you want to have a back-and-forth conversation with someone in another room, though, it doesn't do that (yet?).


The app story is a bit weird. Jason Snell talks about it here:

https://sixcolors.com/post/2026/10/third-party-homeview-apps...

> If you use apps that play audio or video and support CarPlay, though, you’re in luck: HomeView supports those apps, and just those apps, via projection from your iPhone. So if you’re a fan of Overcast or Spotify, you’re in luck.


It sounds like it'll be integrating with the call and widget apis. Right now, you can redirect any voice call that uses the system call UI to your homepod. Adding video, maybe?


Let's please dispense with the "trust me bro" paranoia takes. Link to something that demonstrates your point or you're just making baseless accusations that discourage people from trusting actual privacy and security research.


You can call Apple support and they can remotely take control of your entire phone. They have access to everything if they want it.


I mean, if your privacy concern is 'silicon can be backdoored' then you can't trust any technology anywhere, ever.


Yes? It's just a matter of time before governments figure out they can simply use AI to backdoor designs and insert themselves anywhere in the supply chain. If it isn't happening yet, it soon will be ...


>AI to backdoor designs

correction: AI to backdoor vibe-coded designs

if anyone has read the trusting trust paper, one will know you can theoretically create code where vulnerabilities are hidden in plain sight. But that would mean its designed and reviewed by people who don't understand it in the first place.


Given that even an AppleTV uses less power at maximum usage than an XBox does when it's asleep, I feel as though the power usage is not going to be too much of an issue.


That says more about XBox than about Apple.


it also says more about what's accepted by general audience.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: