3,552 karma · joined May 21, 2009
[ my public key: https://keybase.io/dangoor; my proof: https://keybase.io/dangoor/sigs/S70GBsa2K96S1xO_Z-3r_jHUL6cQ0dFjqQmMlJ6na0o ]
It's totally true that you can't just go by an individual person's account of what happened to them, but I think the evidence for the existence of long COVID goes beyond that.
I've also had some good experiences at bigger companies, but the issues tend to be different.
It's the developer's choice, just like family sharing for the original purchase. This was a good move, since so many apps went from paid to free demo +IAP to unlock. I think a lot of devs who previously allowed family sharing for paid apps have turned family sharing on for IAP.
A good companion article to this could be Simon Willison's "What to blog about" https://simonwillison.net/2022/Nov/6/what-to-blog-about/
The counterpoint to this is that GitHub has been around for a long time and I don't think all of these free features are going anywhere. Even beyond that, there's an API you can use to get your data out and lots of tools build on that API.
https://github.com/MichaelMure/git-bug came up here recently and that looks pretty good, though I haven't tried it. I suspect the usability of a lot of these tools will lag behind GitHub Issues/Projects.
But, yeah, my experience with Go matches yours. It's really amazingly light on resource usage.
Since the sibling comments already addressed everything else, I'll talk about this one:
> For a compiled language it's not very fast
This is essentially true, _but_ a lot of Go users are coming from Python, JavaScript, and maybe Ruby and Go is much faster. Additionally, it comes _close enough_ to Java while typically having a much smaller memory footprint that it really performs quite well in a cloud environment.
Edit to add link from another comment: https://twitter.com/affinitybyserif/status/15903262690314649...
Serif actually said that this is specifically what happened
Beyond what the sibling comments have said about LGPL sounding more like what you're going for, I'll just note that if you'd like broad adoption of this while still ensuring that changes to your code remain open, you might also want to consider the Mozilla Public License.
From what I understand of MPL and LGPL is that MPL is better for instances where dynamic linking isn't possible. The MPL basically says that any changes _to the files you created_ must be available under the MPL, preserving their public availability.
That said, most organizations are fine with the LGPL, but it just gets gnarly if there are instances where you really want to statically link something but you still fully want to support the original library's openness.
You can export to some kind of JSON format. I haven't looked at that yet, personally.
Offline would be good and they definitely need a better mobile story, but for such a new product it's still really great.
Tana mostly works as an outliner now, but they're planning a document mode.
Using "supertags" you can tag a node in the database as being a certain kind of thing (eg an article or, one of my uses, a library for a programming language). You can then specify certain fields that are always (or optionally) part of those things. And you can right queries to display nodes that match a bunch of different criteria and then display those fields in columns in a table or create a board of cards.
It's a very frameworky piece of code, which is exactly the kind of thing that can benefit from generics.
Beyond just folders for categories and tags, Obsidian also supports easy linking between notes (and shows backlinks for the current note).
In the end, it's great: should I decide Obsidian is no longer right for me, I have a bunch of Markdown on disk that I can take elsewhere.
[1]: https://obsidian.md/
It's small compared to iOS, sure, but I think it's still an important part of Apple's overall portfolio. It's currently what all of the iOS developers need to use. Its what Apple's own people use for their work.
I guess the difference of opinion may turn on the phrase "invest a whole lot". I have no idea what kind of investment Apple is making in Mac native GUI frameworks. It's obviously non-zero and is likely what most would deem non-trivial, but I'd argue that it's worth a decent size investment because it is still a potential differentiator for a $40B part of their business.
I will also note that there are some excellent professional native Mac apps, even beyond Apple's own. Things like Pixelmator and the Affinity suite, for example. I'm definitely running a combination of native Mac and Electron apps right now, but I still appreciate the native apps when they're available for the job at hand.
I do feel like this needs to be explicit in the license, especially if jank includes a runtime that is distributed along with your programs.
Looks like a great project to follow!