1,655 karma · joined August 5, 2013
[ my public key: https://keybase.io/jmcphers; my proof: https://keybase.io/jmcphers/sigs/INiu-84qInldp1Jp-B0-Mu7pIdog5wJ7hhGPz9uUTAQ ]
https://developer.apple.com/app-store/review/guidelines/#per...
What happened? Google Photos on the iPhone backs up all your photos by default, and, like Microsoft, Google "shares storage" between email and photos. The minute Google Photos was installed, it started backing up photos until the paltry free tier was reached, at which point it disabled the associated gmail account since it was "out of storage".
Talk about an anti-pattern; I spent a good chunk of time on that trip helping people get their storage back so they could send email again.
I'll never recommend Google Photos to anyone ever again.
There are also (currently) no sleep metrics on app itself; you can only see them on the watch, which doesn't show much besides the sleep duration and an abstract representation showing where you might have woken up in the night.
https://learn.microsoft.com/en-us/openspecs/office_standards...
However, the formats are incredibly complicated, because they evolved from earlier formats that represented nearly the entire in-memory state of the editing software. To a first order of approximation, the .doc format _was_ Microsoft Word.
Source: I worked at Microsoft during this time period and helped document the XLSX format.
> Pebble 2 Duo is sold out! We are not making more.
https://ericmigi.com/blog/how-to-build-a-smartwatch-software...
I switched to a Pebble 2 Duo recently and while the features are comparable on paper (multi-week battery life, reflective display, basic health tracking, etc.), everything is just nicer on the Pebble. The software is thoughtful and fun and there are tons of third-party apps, so it can do all kinds of things the Bip could never do.
There really isn't a huge market for this kind of thing; most people, including nerds, want a watch with a brightly colored screen and tons of health metrics and service integrations. I imagine Pebble will stay a boutique brand this time around.
Without aphantasia, it should be easy to "see" where the dots are since your mind has placed them on the apple somewhere already. Maybe they're in a line, or arranged in a triangle, across the middle or at the top.
The thing about MIP is that the viewing angles are just not that amazing. I have had a Kindle and a Kobo, and they look like paper no matter how I hold them. My Playdate however needs to be positioned at a pretty specific angle with respec to the light to get the best contrast.
(I worked at Microsoft from 2004 - 2013)
The real problem with public charger lines is that there is no social protocol for them yet. At a gas station, it is fine to pull up behind a car currently fueling to indicate that you would like to fuel at the pump next. Charging stations, however, are not built with pull-through spots. There's no place to form a queue at all, so people park nearby, circle, and sometimes snipe a spot when it isn't their turn (because who can tell whose turn it is?).
These days I listen to virtually all of my music from a Plex server containing all the music I've bought over the last few decades of my life. They have an app called Plexamp that brings almost all of the conveniences of Spotify to your local music collection (searching, streaming, offline downloads, smart playlists, auto artist mixes, etc.)
On the first Friday of every month (sometimes, but not always, "Bandcamp Friday") I buy a few more albums for the collection. I wind up spending more on music monthly than I would for a Spotify subscription, but not by a whole lot.
https://github.com/posit-dev/positron/issues/3676
Inline plots are pretty challenging, especially in source mode since (so far) Positron mostly lets the Monaco editor surface do its thing. In visual mode, we've already got our own custom webview so there's an easier onramp.
Out of curiosity, do you prefer source or visual mode when working with inline Quarto output?
You can follow the Positron feature request over here: https://github.com/posit-dev/positron/issues/5640
- discover all the interpreters on the system for the language (e.g. 'find me all the Pythons')
- start an interpreter session for the language
- run a fragment of code in the language and return the result
- get all the variables in the current interpreter session for the language
- view data defined in a particular variable
etc.
We generally try not to invent new protocols; in addition to LSP and DAP, we use Jupyter messages and kernels for most of the above. Positron only has custom protocols/APIs for the bits that are outside the purview of existing protocols.
- core services (Positron's core language system is an API, and R and Python are extensions) - native panes (you can contribute webview panes but they're slow!) - toolbars for other panels, or global toolbars - modal dialogs or any UI other than notifications and quick-pick lists - custom layouts
At a higher level, Positron is a platform that contains data science tools for _other_ extensions to use, and doesn't make sense as an extension itself. The R and Python extensions are the first two we built, but the platform is extensible to other languages.
If I could design _my_ dream watch (to borrow Eric's phrase), I'd put a larger version of the black and white MIP display in Time 2's case -- not more pixels, just bigger and easier to read.
Positron provides a batteries-included experience that lets you work with Python and R out of the box; it's easier to get started, everything's already set up for data work, and the tools all work together smoothly. At least, that's the goal. :-)
(disclaimer - I work on Positron)
We're still investing in RStudio and while the products have some overlap there's no attempt to convert people from one to the other.
(I work at Posit on both of these products)
The API is so good that a lot of core VS Code behavior (e.g. Github integration, support for lots of languages) is implemented in the form of built-in extensions.
It is possible to get 80% of VS Code's functionality with 10-20% of the code if you just bake everything into one monolith, but this has been tried repeatedly and it keeps failing in part because the extension ecosystem and attendant network effects form a wide moat.
(disclaimer - I work on Positron)
The only one that really drives me nuts is the lane-keeping feature, which cannot even follow clearly marked lanes in broad daylight. I don't know that I've ever had it go for more than 15s without disengaging on its own, and forget following even a gentle curve.