Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iPadOS

apple.com

Post reply on HN
Print view View original

381–390 of 393 posts

Re: iPadOS

#381

Post by diffeomorphism »

mistersquid wrote: post #372
diffeomorphism wrote: post #357

Earlier quoted context omitted.

That is a distinction without a difference. "iPadOS (then still called iOS) update".

Differences among operating systems as identified by name and version are very important. My original specification was a small, but my response to you makes a larger point. iPadOS did not (publicly) exist prior to yesterday. Before its release, iPadOS was definitively not “then still called iOS”. Up until its release, iPadOS did not exist (publicly). EDIT: add preposition to first sentence.

> Differences among operating systems as identified by name and version are very important.

Version sometimes, names no. iPadOS=iOS 13 for iPad.

Or are you going to tell me that Windows 10 is much better than windows 8 because it is called windows 10 and not windows 9?

Re: iPadOS

#382

Post by smush »

I wonder if this is partly so Apple doesn't have to keep licensing the term "iOS" from Cisco. Now that they have a premium market, it could be cheaper for them to migrate to iPhoneOS/iPadOS and no longer have to pay Cisco for the license to use the term "iOS".

Re: iPadOS

#383

Post by thirdsun »

yodon wrote: post #348
mwarkentin wrote: post #318

Earlier quoted context omitted.

They added mouse support with this release. It’s an accessibility feature, and it moves a “fake finger” as your control rather than a precise mouse pointer but apparently it works.

It "works" but an actual mouse pointer would have been much better for normal users. The accessibility feature is unfortunately not actually what people who want mouse support actually want.

I'm pretty sure Apple wants to avoid interfaces that target a real mouse pointer and aren't easy to use with finger input. And I think they are right about that: Every UI should be accessible with finger input only.

Re: iPadOS

#384

Post by throwaway413 »

son_ngu wrote: post #380
throwaway413 wrote: post #301

Earlier quoted context omitted.

Here's my setup: 1) iPad Pro 256gb 11" 2) Apple keyboard case 3) Apple magic keyboard 2 w/ number pad (when I need to really get into it) 4) DigitalOcean VM instance 5) Termius ssh iOS app 6) Neovim on the VM, or sometimes I pull out VS Code via code-server [1] and exposed via #7 7) Custom domain name w/ nginx serving up my projects and services from the VM 8) AirPlay via my Apple TV to any connected displays [1] htt…

For your use, what instance size did you get for your DO instance?

I pay for the $40/mo droplet, just because I am able to afford it and I host several active, multi-user prototype projects out of that box and sometimes end up using the power. But I could probably get away with a much more lightweight instance.

Re: iPadOS

#385

Post by zmk_ »

ogre_codes wrote: post #147
zmk_ wrote: post #105

Earlier quoted context omitted.

Microsoft supported Windows XP for 12 years, Windows 7 for 10 years (+4 years if you are willing to pay for extended support). During the lifespan of XP the Moore's law was very much working.

The big difference here is Windows XP and Windows 7 had nearly static feature-sets over their lifetimes (or in the case of XP, SP 3 quickly became the baseline). For the vast majority, Windows XP that shipped with your computer was the same for the lifetime of that product. iOS changes features every year, often quite significantly. The challenge is whether the next version of Windows supported your hardware and this…

The OP said that Apple doesn't have to support older devices because they are antiquated as far as performance goes. So I gave an example where software was supported for far longer during bigger increases in performance.

You are saying that as long as the OEM updates drivers for components support is possible. I agree. This is a reason why Android is often not updated even in the modding community (Qualcomm is not releasing drivers). If only Apple was responsible for both the software and hardware... Oh wait...

Re: iPadOS

#386

Post by nvrspyx »

whynaut wrote: post #358
layoutIfNeeded wrote: post #175

Earlier quoted context omitted.

Nah. Unresponsive = the app’s main event loop is not processing events. On macOS this is when the beach ball cursor is shown. In fact there’s a built-in watchdog in iOS that’ll kill your app after 10 seconds if the main thread is not processing events. On the other hand an app can break in a variety of ways which won’t involve blocking the main thread, e.g. by simply opening a popup that can’t be closed, or getting s…

> Unresponsive = the app’s main event loop is not processing events > an app can break in a variety of ways which won’t involve blocking the main thread I’m not saying you’re incorrect, but for the vast majority of users, any input that doesn’t yield an immediate response = unresponsive.

But that would mean that one thing is unresponsive, not the entire app. The original comment even specified a frozen app.

Re: iPadOS

#387

Post by cujo »

wayneftw wrote: post #239
wayneftw wrote: post #156

Earlier quoted context omitted.

You can’t think of any limitations that macOS has, that others don’t? Not even the really, really big obvious (and recursive) one?

I don’t believe that this much willful obliviousness actually exists here, but I’ll state the obvious anyway: the big one that you failed to realize is about the hardware. And, it’s recursively limited because of the limited choices even within their own lineup. Enjoy your censorship I guess!

Honestly, I just wanted to know a real world case where this person had a mac, didn't know the limitations, discovered the limitations, and then switched.

Your sarcasm is misplaced.

Re: iPadOS

#388

Post by eugeniub »

Abishek_Muthian wrote: post #201
eugeniub wrote: post #198

Earlier quoted context omitted.

> But many of the exploit chains did use public jailbreak exploits and Semi-unthethered jailbreaks exist for 32-bit iOS devices running up to iOS 10.3.3. Apple released iOS 10.3.4 on July 22, 2019 for iPhone 5 and iPad 4g.[1] So it's not completely unheard of for Apple to release iOS updates after officially dropping iOS support for old devices. From the Apple website:[2] > iOS 10.3.4 addresses an issue that could im…

Unlikely, if it was a security update then iPhone5C should have received it as well. iPhone5C didn't receive 10.3.4 update because its GPS hardware supposedly was an updated one than the iPhone5. Also, Google Project Zero article(link in parent comment) gives the clear timeline of the attacks and that the exploits were updated to mitigate patches with every new OS updates; so even if 10.3.4 had security patches older…

Well it's listed under "Apple security updates".

Re: iPadOS

#389

Post by wayneftw »

cujo wrote: post #387
wayneftw wrote: post #239

Earlier quoted context omitted.

I don’t believe that this much willful obliviousness actually exists here, but I’ll state the obvious anyway: the big one that you failed to realize is about the hardware. And, it’s recursively limited because of the limited choices even within their own lineup. Enjoy your censorship I guess!

Honestly, I just wanted to know a real world case where this person had a mac, didn't know the limitations, discovered the limitations, and then switched. Your sarcasm is misplaced.

Well, I am that person. I can go through a ton of other limitations that macOS has if you want…

But you moved the goalpost on me because first you just asked for a limitation and I gave you probably the largest one. You didn’t say anything about it being an unknown limitation before I got started using it… You said “I’ll bite“ as if you could not think of one limitation of the platform. I knew about the main limitation, that you can only run it on Apple hardware, before I bought it but I decided to go forward anyway because I want to compile an app for iOS and I decided that it would be much better than trying to maintain a hackintosh.

There was zero sarcasm in my response. Not even the part where I said “enjoy your center ship I guess”, because Apple fans seem to love making my text disappear for others if I don’t gush over Apples products. If you really want to know about all of the limitations that I did not know about before I purchased into the platform I’ll be glad to do that.

Here’s a big one: you simply cannot operate the entire OS with just a keyboard unless you add some third-party usability-correction utilities. It’s impossible. And those utilities are suck and they don’t work well and there’s a chance that Apple will take them away from you or cause problems with them in any given update. That’s why Stephen Hawking always used Windows, same as just about every other disabled user in the world.

Re: iPadOS

#390

Post by tonyedgecombe »

robohoe wrote: post #15
cfors wrote: post #10

Cool, but nothing about any focus on making the machine realistic for development. My current MacBook Pro is getting a little long in the tooth and after suffering through the 2016 and later versions at work, I will not be buying one of those until the keyboards are fixed. If iPadOS has first class terminal support I would consider making it my full time machine. Looks like the waiting game will continue.

Blink shell on the App Store is a fantastic terminal that works wonderfully on iOS/iPadOS. Highly recommend it even with its steep price of $20. It supports mosh out of the box and has ability to store/import private/public keys. Multiple terminals can be opened as well. It even has a limited native shell which you can use to SCP files from your iPad to servers.

I wonder if there is any other profession that thinks $20 is a steep price for its tools.
Post reply on HN