Live data from Hacker News

Buying an iPad Pro for coding was a mistake

technicallychallenged.substack.com

511–520 of 533 posts

Re: Buying an iPad Pro for coding was a mistake

#511
post #460
post #291

Earlier quoted context omitted.

Mainly DOS/Windows user from ~1992-2000. Mainly Linux 2000-2011. Mac since. > The moment macOS is shackled any more I hadn't really noticed it being "shackled" at all. What do you mean?

If you don’t have an Apple developer account and you give a program you wrote to someone else, their computer will refuse to open it unless they go into System Preferences and whitelist the program.

This is intentionally misleading. Running any unsigned package requires the end user to open the program through system preferences for the first time, as a “did you really mean to run this potentially pwning software”. It’s a good security practice, and less intrusive than windows UAC by far.

Re: Buying an iPad Pro for coding was a mistake

#512

Earlier quoted context omitted.

Between $500 and $3000 perhaps, like most laptops.

my main computer is a Lenovo Duet 5 tablet/laptop hybrid. It gets more than 24 hours of battery life and is completely silent, runs cold and has an excellent OLED screen. I honestly don't know what more I could ask for. its $500 and includes the kickstand and keyboard I did mention in my previous comment that the m1/m2 are still faster than other arm64 devices but for the web development tasks that I'm doing a chrome…

Thanks. That’s an interesting device. I ignored devices running ChromeOS. Of course it’s a lot slower than a M1 on the paper but I believe you when you say it’s good enough.

Re: Buying an iPad Pro for coding was a mistake

#515

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…

> Boggles the mind why people still fall for the iPad Pro as a serious work machine beyond writing meme

Depends on your definition of “serious work”. I don’t write much code anymore, but I can definitely do my entire job using my iPad Pro. I have pretty much done my job for the last couple weeks while managing a family medical situation with multiple back and forth to hospital each day using my iPad. Built in cellular, a small and very light form factor even with the Logitech folio touch case I added, which is completely comfortable to work on…and I can pull it from my sling bag and be up and running in about 3 seconds.

Frankly if I needed access to my main rig back on my desk, Parallels Access is more than sufficient to accomplish that need, but I rarely finding myself needing to use it.

Re: Buying an iPad Pro for coding was a mistake

#516

Earlier quoted context omitted.

my main computer is a Lenovo Duet 5 tablet/laptop hybrid. It gets more than 24 hours of battery life and is completely silent, runs cold and has an excellent OLED screen. I honestly don't know what more I could ask for. its $500 and includes the kickstand and keyboard I did mention in my previous comment that the m1/m2 are still faster than other arm64 devices but for the web development tasks that I'm doing a chrome…

Thanks. That’s an interesting device. I ignored devices running ChromeOS. Of course it’s a lot slower than a M1 on the paper but I believe you when you say it’s good enough.

its really on the cheaper/slower end of the spectrum but chromeos is also super lightweight.

a joy to use! I hope to see something similar from apple in the future, I've heard whispers of oled ipads?

Re: Buying an iPad Pro for coding was a mistake

#517

Earlier quoted context omitted.

Are you saying apple is lying? Because they publish both weight and battery life numbers. Hint: "less" means the number is smaller.

I'm saying you're arguing in bad faith, and are thus probably not worth engaging with further.

Just to recap: your "even if" was very rude. I called you out on it. Instead of apologizing, you now insult me.

Re: Buying an iPad Pro for coding was a mistake

#518
Awhile ago, my employer was indicating their intent to deploy a mobile app for time tracking and scheduling, and so I created a "work account" on my personal Android phone. Unfortunately they somehow forgot to enable the Play Store for my account, so I can't install anything other than the stock Google apps.

So one day I tried to "do work" on my phone and it was a comedy of errors. Chiefly I use three apps: Slack, Google Docs/Sheets, and our internal website. Slack and Google Docs were slow as molasses in the Chrome browser. It was clear within 3 minutes that I would never get anything done if I was ever restricted to "work" from my phone.

As a counterpoint, I determined that my employer's software requirements are so simple that they allow me to use a Chromebook, so I purchased a middlin' Chromebook and it's working great! Of course, Chromebooks are definitely more of a notebook computer than a mobile device, but they are often pooh-poohed as underpowered or "toys" because they don't run all the apps. I think it's an undeserved rep now, seeing how far they've come.

Re: Buying an iPad Pro for coding was a mistake

#519
post #487

Earlier quoted context omitted.

Yes, this is part of the genius strategy that most people don't see. There is an entire generation of people growing up where iPhones and iPads are the computer. Many of them also don't even know that there is a difference between a mobile device and an iPhone. Android is this weird sort of alternative that nobody uses, and Windows is this "PC" thing which they've never used but they hear that some people use for gam…

Android is only used by 80% of the rest of the world, but who's counting anyway.

To a subsection of people, "the rest of the world" is a mythical place that doesn't exist.

Re: Buying an iPad Pro for coding was a mistake

#520

Earlier quoted context omitted.

i like how we are talking about an OS that initially released in 2007, and only got support for "opening files in place" in 2015. What a time to be alive, we can open files in place and all.. gotta give apple credit, while the rest of the world is reduced to lowly CopyOnWrite, they took it one step further, with CopyOnRead.

What next? Are you going to complain about Windows not supporting more than 8.3 character filenames until 1995?

i would, but thats a bit more forgivable :)
Post reply on HN