stephencelis

> Marketing I suppose.

Nope. And not sure where you get that idea. This release even involved a rename away from including "GRDB."

When 0.1 of the library was released, it was a simple adapter between our Sharing library and GRDB, thus the name SharingGRDB. As our needs grew, the tool evolved significantly, and both the Sharing component and GRDB have become more of an implementation detail. In the future we will consider supporting any SQLite adapter, even your libraries ;)

Are you suggesting SQLiteData is an ORM, or SwiftData? SwiftData (and CoreData) are certainly ORMs, but SQLiteData is not. It's simply a collection of tools on top of SQLite that provide similar functionality to SwiftData, but you always have direct access to SQLite.

The things you say that SQLite doesn't do is exactly what SQLiteData provides (Swift-friendly bindings for encoding and decoding data from SQLite), and more. There's a footprint, as there is with any library, but there is no ORM level of abstraction here.

I think you're missing the point. iOS 13 is not the value proposition of the library, it's simply one small feature of comparison of many and isn't highlighted beyond a simple mention. The library provides just as much value if you are starting a new app today and choose to target iOS 26+.

> And with Apple's history of source-breaking changes over major platform updates, plus given how even huge libraries/tools like Alamofire, Realm, RxSwift, Cocoapods eventually succumbed to oblivion, I can't think of why an Apple developer with any modicum of discernment would choose PointFree's tools over Apple's own--unless they are themselves caught by the allure of reinventing the wheel.

Isn't this just a blackpilled take in general? You're complaining that Apple software breaks, that other third party software is discontinued, and this somehow leads to the conclusion to avoid this library?

Ah, I'd missed that update. Thanks! I prefer this to the current workflow.

For those that are worried, the source is there to inspect and compile. For those that aren't, there's reduced friction. It's a young project and I could move the binary elsewhere, but I'm not sure that would change your concern?

Is there an alternate process you would suggest?

Slingshot's supported Retina since V2. Dropbox's auto-upload of screen shots is pretty good (they're using a private API to copy the link the your clipboard before the upload even starts, so it feels really fast), but if you share files outside of screen shots, Slingshot might still fill a need with file and clipboard sharing.

It actually lets you do this already, though the documentation is relegated to a manpage that doesn't get installed automatically. It checks, in order, for:

  - $GHI_REPO env var
  - git config ghi.repo
  - remote named "upstream"
  - remote named "origin"

So you can just use "git config ghi.repo username/reponame" to get the behavior you want.

We didn't spend $79 to read his blog.

Amazon offers 2 price points, emphasizes the ad-driven one, and somewhat obscures the fact that it's ad-driven. I don't see how that relates to the free (and Creative Commons free content of) marco.org, and the fact that he syndicates ads from a network he trusts there.

  If you want to set your login shell to zsh, go to System 
  Preferences -> Users and Groups. Right-click on your user 
  account and select Advanced Options. Change the login shell 
  dropdown to /bin/zsh.

You're better off using `chsh -s /bin/zsh` (or, better yet, `brew install zsh`, append `/usr/local/bin/zsh` to `/etc/shells`, and use that, instead).

I would have loved to have had this a year ago, or two, etc., but my accidental quits haven't been nearly as frustrating since upgrading to Lion. I can still see this being useful, though, especially with apps that are slow to implement resume functionality.

(You should only have to run this the first time you bundle.)

Having a standalone GCC installer is a nice option (especially if you have an Air with limited disk space), but if you want to avoid the hassle of debugging the occasional compilation failure, Xcode is the way to go.