1,419 karma · joined November 28, 2012
If you leave micro.blog hosting, you can just submit your new RSS feed wherever you're hosting the same content and it'll be pretty seamless, I think.
Curation and diversity, in this post, feel like expressing the same problem in some ways-- too few people with insufficient diversity are currently using the service. Curation _may_ fail at scale the way they are doing it, but we don't know that. And if the diversity isn't there to curate, I'm not surprised curation hasn't surfaced diversity. But micro.blog is super young. Maybe it'll be a useful social place, maybe not. For me, it's a pretty good blog host right now.
It's a huge deal that I can control who shares and sees what vault, turn off an employee's access as soon as they are leaving the company, revoke tokens, etc.
Before this we were using Dropbox and it was a nightmare. Credentials for a bunch of things were mixed up in the wrong vaults, far more duplication, revoking access was more of a pain, etc.
1Password for a family sharing may not be worth it, maybe not even for a small 5 person shop with a very stable set of employees who are all savvy. But with 25 or so people with varying level of technical expertise and actually critical information being shared, 1Password's subscription is a godsend.
It's not the case that one person learns through sights, another sounds, and yet another through movement (roll eyes)-- instead it's the case that doing things multiple ways and multiple times is better for memory.
I'm not particularly excited about it, but it's obvious why they'd want to do this, even if the phone doesn't get thinner, based on this picture from an iFixit teardown: https://d3nevzfk7ii3be.cloudfront.net/igi/fdaWRVGrZhxlZoJH.h...
I've never had any trouble with iCloud syncing personally, though I haven't used it for a ton of stuff. Photos is definitely the biggest use I've ever had for iCloud and it works flawlessly from day one for me.
I have largely avoided ts, zoo, etc where possible. Time series stuff seems to have a lot of specialized tooling all of which tends to be much more strict about data structure than I'm comfortable with for my flow.
packrat has helped a lot with version control of packages, but it still doesn't quite feel like the right solution.
I've been really impressed in the last 5 years how far R has come in these areas though, so like you I keep coming back. By the time I start getting over the learning curve other places, R seems to have developed better tooling for what I want to accomplish anyway and I can come back and right cleaner, clearer, better software faster in R.
I wonder if you tried doing things like:
* preallocate a list, then do.call(cbind, your_data) * Same as above, but with some of the faster alternatives to cbind like dplyr::bind_cols or data.table::cbind * Use data.table, which has far faster joins than base R (so does dplyr) if you were doing a true merge/join
If it was truly just adding a column rom each file together into a file, these kinds of tasks are much better using UNIX tools, in my experience.
I don't know anyone who considers themselves a "data scientist" of any sort that doesn't view their job as 80% or more data wrangling/munging/cleaning.
I write production ETL processes in R at my current job. AMA.
Password fields can't use custom keyboards because of fear of logging that entry. The share sheet extension works great though for 1Password, especially when combined with TouchID.
However, I have had at least two cases where a file somehow didn't completely sync and it was corrupted, totally unrecoverable. I am left feeling that versioning is the killer Dropbox feature that BT will never replace. I'm not sure what I'm going to do... I'm still using BTSync for a lot of stuff, but it has lost its trust.
On 2, third-party apps have long supported opening in a different app. Of course, it's up to that developer to include the x-callback-url and Apple apps won't use that preference.
Did Xbox or Blackberry serve as direct substitutes for traditional PCs? No. Have Android and iOS phones and tablets serve as direct substitutes for traditional PCs? Yes.
If you're spending several seconds to press a button on a toolbar you're already disrupting your workflow in a way directly comparable to resizing a window by grabbing a corner. If "disrupting your workflow" is such a huge concern you'd want a keyboard shortcut for this action anyway.
Sorry, but I actually think not full screening a window is actually the far superior handling in a world with high resolution, large screens. There are other ways to "hide" things you are background like using Spaces or whatever they're calling virtual desktops.
> I do have an addon installed to solve this, but this is stupid core OS functionality and It's unbelievable that I'm living in the 21st century and full screening apps on multiple monitors requires years of waiting and entire OS upgrades.
Ok. Seems like it takes virtually no effort one time to get the functionality you really want. If that's enough to make you super crazed and need a huge vent, that's fine. For me, that's a very plausible solution to a specific problem related to a preference that you likely developed because you are used to working on a different platform. It's true that:
> I'm not asking for weird edge case user environment things, or highly specialized workflows, or ultra-specialized niche window management or other things, just for the things to work as the user would expect.
... but you are asking for OSX to act like Windows has rather than how OSX has since it has had windowing (or at least as far back as my memory goes to the mid 90s). There was a choice made. It's a choice I didn't like when there weren't things like virtual desktops and when screen resolutions were lower and screen size was smaller. On a big screen with lots of pixels, I think it makes sense to double down on the traditional way they've handled enlarging windows.
That being said, you can drag the window to the size you want and have nothing but window and menubar. There are also a ton of third party software to automate this as a keyboard shortcut or similar if that's the key. Then viola, no weird dependencies on a weird feature not designed for 23" + screens.