TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Native Applications with Racket

83 点作者 Bogdanp超过 5 年前

5 条评论

JohnStrangeII超过 5 年前
Is there any &quot;publishing service&quot; for MacOS that takes a percentage of each sale and allows you to provide build scripts and source code, compiles and tests the application and distributes it on the app store?<p>If not, do the Apple EULAs prohibit such a service or is it not considered lucrative enough?<p>I used to develop for MacOS but have stopped supporting it entirely since Catalina, because I cannot be bothered with being locked into Apple&#x27;s development tools, notarization, the Developer Network, and so on. It just isn&#x27;t worth my time and money, but I&#x27;d still like to distribute native applications. Provided the EULA of such a service would be reasonable (e.g. good protection of the source code), I&#x27;d gladly use it, since otherwise all Apple sales are lost anyway. But there doesn&#x27;t seem to be any such service, and it&#x27;s IMHO weird that Apple don&#x27;t offer that themselves.
评论 #21961743 未加载
nixpulvis超过 5 年前
This notarization nonsense is being implemented very poorly it sure feels like. Shouldn&#x27;t we be more focused on sand boxing and default settings for the sandboxes, vs forcing user applications to ask for everything they need? Put the burden on the runner, not the application.<p>Am I missing something fundamental here?
评论 #21960418 未加载
todd3834超过 5 年前
I’m working on a MacOS app and I started with a somewhat similar idea but with Go instead of Racket. I ended up ditching it for pure Swift. The main difference between myself and the author is that I ended up really liking Swift. Otherwise I would have stuck with my original approach.
评论 #21961453 未加载
saagarjha超过 5 年前
&gt; it is a completely native Cocoa application whose frontend is built with Swift, the core business logic is all in Racket<p>This is generally the way to go if you want to be cross-platform: write your core code in the language of your choice, but make sure you use the platform frameworks for the porcelain. If you do it well, your users won’t notice the difference!
评论 #21960744 未加载
jsjolen超过 5 年前
Sounds slow to use RPC with JSON for communication.<p>It seems that Racket does allow for C-to-Racket calls. You could write a glue program that generates C code that calls Racket functions and returns data, Swift code can then be generated to call that C code. That might be faster.
评论 #21960913 未加载