Live data from Hacker News

Buying an iPad Pro for coding was a mistake

technicallychallenged.substack.com

421–430 of 533 posts

Re: Buying an iPad Pro for coding was a mistake

#421
post #379

Earlier quoted context omitted.

If it is only "very nearly", wouldn't something larger like an s8 ultra be better? Also "by a mile" is a stretch. It might be better but all $1000+ tablets are reasonably close enough to be happy with any of them.

I've used a lot of Android tablets, low end to high, and developed software for them. They're awful. Crashy, glitchy, bad battery life. I don't think we'll see a true iPad competitor until/unless a new OS enters the market—Android's had a long time to get its shit together, and evidently just can't. Wish someone would give it a shot, because I'd love to see that market better-served.

5 years ago I would have mostly agreed with your statements about android tablets, but since then Samsung has created a family of very acceptable tablets imho.

Re: Buying an iPad Pro for coding was a mistake

#422

Earlier quoted context omitted.

People are also using the iPad for running audio programs. There’s a ton, and they work together by routing audio from one app to another (so you don’t need a VST / AU host). Then there’s all the people running ProCreate or something similar. The horsepower is getting used.

There are definitely ways to leverage the horsepower natively. Having toured with musicians pretty recently though, I'd be lying if I said I saw a single person using an iPad for performance purposes. Everyone uses a laptop, and I don't think Logic Pro on iPad would have changed much. People want Ableton Live and Omnisphere with deep audio hardware support in the drivers and a proper file manager. The iPad makes a va…

I'm not exactly at the highest levels of industry. I generally agree with you- I much prefer hardware or a laptop.

However, as a musician, I wouldn't perform with one, but I use forescore literally every day.

As an sound tech, I've mixed a while lot of shows on glass both as a monitor engineer and FOH for smaller stuff. My iPad is a great tool for that work. They are pretty ubiquitous amound sound techs, at least at the levels I work at.

Re: Buying an iPad Pro for coding was a mistake

#423
post #157

Earlier quoted context omitted.

The Google Nexus 7 is from 2012, so 11 years ago, and is still perfectly usable with a battery upgrade (possible because it's not glued/soldered) and a custom ROM (possible because the bootloader is open).

Hmm I would beg to differ. I have some N7s and they are too slow to even run as a panel for home assistant. Apps have really got much heavier since then. Of course they are running only a mid-range SoC from 2012 so that makes sense.

I have a N7 with Ubuntu on it. It's my distraction-free writing box. Runs vim great.

Re: Buying an iPad Pro for coding was a mistake

#424
post #268

Boggles the mind why people still fall for the iPad Pro as a serious work machine beyond writing meme. The fact that Final Cut launched on it recently and while its exporting you have to sit there leaving the app open you can't go do something else is the punchline of the decade for the lie that this is a serious machine. This is before we get into the comical evolution from "You just need the touchscreen" to "Actual…

Yes, iPadOS has deep, lingering deficiencies as an OS for professional use. But their ads and keynotes are convincing, so I can't blame people falling for it! There's this weird juxtaposition of a terrible productivity machine combined with some mature, amazing and easy to use software in the demos, and Apple makes it look like iPads can be deeply embedded in your workflow and people have fun and laugh as that tiny d…

I'm somewhat convinced that Apple wants to remove the notion of a Unix filesystem (there are files and directories of files/directories and they have owners/permissions/etc) from their users' understanding of how to use a computer. Both out of ideological purity ("what is a computer?") and so that their users can't use a different device that has an entirely different mental model for interaction.

I already see this with juniors/students/kids that grew up using nothing but mobile devices, tablets, and chromebooks with GSuite. They don't know what a file is.

Re: Buying an iPad Pro for coding was a mistake

#426

Earlier quoted context omitted.

Out of curiosity, what are the "good writing apps" on windows? When I last checked windows seemed to have exactly one note, android like 2 apps and iPad like 3 apps.

OneNote Concepts is good for some things too.

Concepts looks nice and I hadn't heard of it before. The freemium and/or subscription seems like a potential dealbreaker to me, but might be worth a try.

Re: Buying an iPad Pro for coding was a mistake

#427

Earlier quoted context omitted.

People are also using the iPad for running audio programs. There’s a ton, and they work together by routing audio from one app to another (so you don’t need a VST / AU host). Then there’s all the people running ProCreate or something similar. The horsepower is getting used.

There are definitely ways to leverage the horsepower natively. Having toured with musicians pretty recently though, I'd be lying if I said I saw a single person using an iPad for performance purposes. Everyone uses a laptop, and I don't think Logic Pro on iPad would have changed much. People want Ableton Live and Omnisphere with deep audio hardware support in the drivers and a proper file manager. The iPad makes a va…

It's all CoreAudio/CoreMIDI under the hood, in both iPadOS and MacOS. I don't think MacOS does anything "deeper" but there is some 3rd party stuff like PT HDX/UAD, etc.

The limiting factor is the performance software (Mainstage and Live) aren't on iPadOS, yet. Live has some bigger lifting to do to get there.

Re: Buying an iPad Pro for coding was a mistake

#428
post #379

Earlier quoted context omitted.

I've used a lot of Android tablets, low end to high, and developed software for them. They're awful. Crashy, glitchy, bad battery life. I don't think we'll see a true iPad competitor until/unless a new OS enters the market—Android's had a long time to get its shit together, and evidently just can't. Wish someone would give it a shot, because I'd love to see that market better-served.

Yeah, yeah and you literally died. This is HN and not reddit, you are better than that.

I have exactly no clue what you mean.

Re: Buying an iPad Pro for coding was a mistake

#429

Boggles the mind why people still fall for the iPad Pro as a serious work machine beyond writing meme. The fact that Final Cut launched on it recently and while its exporting you have to sit there leaving the app open you can't go do something else is the punchline of the decade for the lie that this is a serious machine. This is before we get into the comical evolution from "You just need the touchscreen" to "Actual…

People are also using the iPad for running audio programs. There’s a ton, and they work together by routing audio from one app to another (so you don’t need a VST / AU host). Then there’s all the people running ProCreate or something similar. The horsepower is getting used.

Yep. There's a lot of guitar player youtubers who use iPads for amp modeling and effects. Seems to work pretty well.

Re: Buying an iPad Pro for coding was a mistake

#430
post #424
post #268

Earlier quoted context omitted.

Yes, iPadOS has deep, lingering deficiencies as an OS for professional use. But their ads and keynotes are convincing, so I can't blame people falling for it! There's this weird juxtaposition of a terrible productivity machine combined with some mature, amazing and easy to use software in the demos, and Apple makes it look like iPads can be deeply embedded in your workflow and people have fun and laugh as that tiny d…

I'm somewhat convinced that Apple wants to remove the notion of a Unix filesystem (there are files and directories of files/directories and they have owners/permissions/etc) from their users' understanding of how to use a computer. Both out of ideological purity ("what is a computer?") and so that their users can't use a different device that has an entirely different mental model for interaction. I already see this…

The Plan9 discussion from a few days ago shows that quite a few people here don't know what a file actually is either.
Post reply on HN