@szbalint Yeah, I think most of us here are going to switch to working from home until this gets sorted.
@eli It's probably get sorted before we move to our new offices in March.
Maybe 😄❄️⛄️
@pkra Haha, yeah. That definitely undercut their argument as I'm pretty sure that PDF form support is pretty spotty in general. It isn't just Chrome that doesn't support it.
@eli 👍🏻
@mjdescy Yeah. I don't blame you.
@szbalint Beer was banned until 1 March 1989 and some people celebrate that day by, well, drinking beer. But the ones that do so are mostly college students, alcoholics, and other people who are prone to manufacturing excuses for getting drunk 😁
@cdevroe Icelanders like giving books as Christmas presents but staying in to read and avoid other people on Christmas Eve is not a tradition. If you want to go to bed and read after you've done the whole Christmas brouhaha, that's fine but that can often be quite late in the evening.
@kaa My guess is that things are still in progress. I'm lucky in that I've had a Mastodon account for a while so I've already got a list of users to follow.
@kaa Meant to say that I’m going to try micro.blog’s mastodon features by following a bunch of folks from this account.
@baldur Seeing this level of interoperability between formerly segregated platforms is really really neat to see.
@baldur And to be even more specific, I meant Apple iOS and macOS since Microsoft is already exploring baking PWA support directly into the platform.
@eli Oh, OS absolutely. By 'browsers’ in the earlier note I meant extending the functionality of built-in browsers and browser views to bake PWA support into the OS..
@eli Yeah. I’m really hoping that other browsers will follow suit once the overall value of the idea has been proven.
@tmj A $200 price difference can't be described as 'only' by any measure.
Especially since there's less of a price difference between the new Airs and the entry level Pros than between them and the Air Classic.
The USD$999 price bracket is a very important entry-level price and if Apple is planning to leave it, we can expect Mac sales to drop even further.
Which is probably why Apple has decided to stop reporting Mac sales numbers.
@atog I'm in the wait-and-see mode as well.
@frankm ChromeOS isn't quite there yet but it's improving quickly.
Android apps are still a little bit too isolated from the rest of the system and Linux apps are still on the unstable side.
But, even though I've been very annoyed at ChromeOS in the past, it's just a matter of time before the OS is a fully-fledge, fully capable general purpose computing platform.
And I think there's a decent chance that ChromeOS and the Pixel Slate will get there before iPad Pro+iOS does.
@uncrtn Text selection. Text selection. Text selection.
The functionality and ergonomics of text selection in iOS are absolutely horrible when using an external keyboard. That's my primary beef. All of the arguments Apple makes against adding touchscreens to Mac? Yeah, those apply equally against using an iPad with an external keyboard. Except with an iPad you can't use an external trackpad or mouse.
And writing for a lot of people requires the use of a ton of research, notes and references. That generally means a lot of browser tabs and quick switching between the browser and the writing app, esp. when you're writing longer texts.
Which is very awkward given the constraints in iOS and hard to fix because there are fundamental limitations to how useful non-touch external screens can be in a touch-only OS.
You're also let down by iOS Safari, which just isn't in the same class as the desktop version. And it doesn't really matter how good the competitors are because you can't change the default browser.
If you're working with images, you also need to easily switch to and from a graphics app, which gets very clunky very quickly in iOS if you're making iterative changes to the graphics (edit text, update image, edit text, update image, etc.).
Finally, even on a desktop it's really easy for me to come up against the limitations of an 8gb laptop just because of the browser tabs I have open and are relevant to my current task.
The 4-6gb the current iPads Pro come with is barely enough.
For a lot of people, involved writing tasks on the iPad are just horribly, horribly awkward and most of it (except the RAM issue) is down to intentional iOS limitations.
@rmcrob That’s a cool idea.
@jack It's kind of always been the case since the first iPad Pro but it's just become embarrassing with the latest update.
The hardware is so powerful and the software is so so iPhone focused and detached from the needs of productivity and creativity in general (esp. writing) that it's almost ludicrous.
It's priced as a laptop. As powerful as a laptop. With a better screen than most laptops. But it can only to a tiny fraction of the normal laptop tasks due to arbitrary limitations in iOS:
@eli @bradenslen Thanks from me as well! PopOS was on my list of things to test because it looked interesting but I guess that even if it didn't have any problems the advantage it has over the equivalent Ubuntu version is marginal at best.
@smokey It's very pretty.
@JohnPhilpin I've been following his work for a while so … 🙂
@eli Same! Which is why I posted the link. To remind myself 😆
@smokey Aww, thanks 🙂
@amit Yeah, like @smokey guessed, both lag and jitter are recurring issues for the Samsung Chromebook Plus that I'm using. It's mostly when you've got Android apps running that both websites and Android apps become jittery/laggy.
ChromeOS can be buttery smooth but IME you have to avoid Android apps to keep it that way. Someties just launching and then exiting an Android app is enough to make the entire system jittery. I'm guessing having the Android subsystem running in the background is enough.
An especially annoying issue is Youtube playback lag/stutter that sometimes comes out of nowhere.
I've also occasionally gotten a bad update that introduces lag/jitter which then disappears in the next update (and this is on stable btw).
I think a lot of people just don't see jitter or lag even though it's there. They're so used to UIs being unresponsive that they are blind to it. Which is my theory as to why the online ChromeOS community doesn't talk about the issue that much.
I think ChromeOS is a great concept and maybe it'll get there eventually. But it definitely isn't there yet.