czx4f4bd

The only factually incorrect claims here have come from you.

You claimed that the iPad lacks "any developer tools". That's factually incorrect, as you've admitted and repeatedly tried to walk back.

Because you're determined to be right, after you admitted that the iPad has at least some development tools, you tried to move the goalposts and say that the iPad doesn't have any IDEs, while in the same sentence admitting that it has text editors and cloud-based IDEs, which are developer tools. Now you're trying to walk that back again. If you're going to be wrong, you could at least have the decency to be consistently wrong instead of waffling back and forth like this.

You said, "There's also no way to install a runtime or compiler on iPadOS." That's also factually incorrect. I can use basically any compiler or runtime that I want inside iSH without even needing an internet connection after they're installed.

At any rate, I've already explained why none of this is even relevant to the point at hand, but since you can't be wrong, you'll probably ignore these points like you've ignored everything else. Or maybe you're just trolling, who knows? Either way it's pretty pathetic.

This comment is bizarrely antagonistic for no reason and I would appreciate if you'd knock it off. I literally admitted I was incorrect in thinking that I could comfortably write code on my iPad, a point that largely agrees with what you're saying, but for some reason you still feel the need to argue even further.

It should be immediately apparent to most people that I made my decision based on my own personal context and requirements at the time, just as you made your decision in your own context, which is why we each came to a different conclusion. I already made it clear the iPad was only intended to supplement my laptop, not replace it, so obviously I didn't expect it to fully replace my development workflow either. I just thought it might be usable for casual coding when I wasn't at my desk, and I was willing to accept that I might be wrong in that.

There's no point in trying to convince me now that the iPad dev experience sucks, because obviously I already know that, as evidenced by the fact that I literally said it two comments ago (and because you're wrong about why it sucks). You don't win anything for proving I was wrong again.

What I really don't get is why you feel the need to tell me I'm wrong about what the iPad is capable of when I actually bought one and wrote a decent amount of code on it, while you admit you dismissed it as an option with a few minutes of consideration. I have literally written, run, and compiled code on my iPad both locally and remotely using the dev tools you claim don't exist or don't count or are too janky or whatever. What is the point in arguing with me about that when we both already agree it's probably not worth programming on an iPad either way?

The funny thing is that tooling wasn't even the main reason I moved away from coding on my iPad. The tooling wasn't my favorite, but it does exist and was passable for my limited requirements. I just didn't like iPadOS's mediocre multitasking and weird conflicts with key bindings in browser-based dev tools. Were it not for that, I probably would've kept programming on my iPad for a while longer.

My use case didn't require an IDE. My main intent was to remote into my batteryless laptop, so in principle the iPad didn't need much functionality of its own.

That said, I don't know what you mean by "the lack of any developer tools". There are absolutely code editors, IDEs, SSH clients, and even runtimes for iPadOS. There are also lots of web-based IDEs and editors now, even self-hostable ones like code-server. Obviously I wouldn't have bought mine if those didn't exist.

I don't know, when I impulse bought my iPad Pro a few years ago to supplement my laptop that stopped charging, I did about 15 minutes of research and found a lot of people claiming that you can comfortably code on an iPad Pro. That turned out to be completely untrue for my use cases, but it would've taken a lot more than 5 minutes to figure that out.

That said, the iPad Pro is my biggest mistake I've never regretted. I've used mine every day since I bought it and I love it. It sucks for coding but it's great for handwritten notes, typed notes, drawing, music production, casual web browsing, mobile games, watching YouTube, controlling Spotify remotely, etc. It's a perfect companion to my regular laptop and a great travel device when I don't want to take my laptop with me. Even the lack of a full OS is an upside for me. iPadOS hinders multitasking enough that it ends up being a more focused device than my normal laptop.

Yeah, it's basically just a conspiracy theorist's screed, poorly disguised as some kind of "COINTELPRO training manual". This part tells you the person's mindset:

> A second highly effective technique (which you can see in operation all the time at www.abovetopsecret.com) is 'consensus cracking.' To develop a consensus crack, the following technique is used. Under the guise of a fake account a posting is made which looks legitimate and is towards the truth is made - but the critical point is that it has a VERY WEAK PREMISE without substantive proof to back the posting.

Someone on a conspiracy forum posting a weak argument? Obviously that's just more proof of the conspiracy!

I find that even more bizarre tbh. Thst seems like the perfect place to document the Scanner class.

Unfortunately, enterprises are intensely risk averse. I worked at a place where we could only generate proper certs by manually submitting a ticket to IT and waiting probably days to get it back, giving us zero hope of applying meaningful automation. Getting certs from a proper CA was absolutely forbidden, despite our lobbying, so in a lot of cases self-signed certs were the only option if we wanted to automate.

I'm pretty sure just giving app developers more time to prepare for price increases would've been enough. If they'd given Apollo and RIF 6 months notice of the new pricing instead of 30 days, the devs would probably have adapted to a paid model and moved on. There would still have been plenty of grumbling, but not nearly as much outrage.

Reddit also offloads the complexity of forum management from moderators and removes the friction of registration.

If you want to create a traditional forum, you have to figure out how to host it, what forum software you want to use, how that software works, how to configure it, etc. If you get attacked by spammers, hackers, or trolls, you have to figure out how to stop that more or less from scratch. It requires a significant amount of technical knowledge, time, and money to make it work.

Then, even if you use a dedicated forum hosting service, your forum is still basically on an island. You have to find a userbase and attract them, convince them to register dedicated accounts for your forum specifically, and keep them coming back, which is really hard if you don't have an existing userbase to make your forum compelling in the first place.

With Reddit, nearly all of that goes away. Creating a subreddit is extremely easy and costs nothing but time. Moderators still have to moderate, but they don't have to figure out how to manage forum software or handle DDoS attacks. Since any Reddit user can join and participate in any subreddit, and since posts appear on users' homepages in one feed, communities can grow much more quickly and are less likely to die out due to inactivity. And there's only one UI for the whole site, so users don't have to learn how to use whatever random forum software each site has chosen.

Your comments disappeared because the sub went private. Reddit won't show any comments from private subs you aren't allowed to view, even comments that you made.

Why do they have to be for-profit corporations in the first place? Wikipedia, Internet Archive, and Archive of our Own are nonprofits that are capable of handing a large numbers of users creating and accessing a large volume of content.