ケーボ retweeted
Hurray! Swift Playground 4.7 is out, bringing the iOS 26 API – including Foundation Models! apps.apple.com/gb/app/swift-…
ケーボ retweeted
📣Announcing the first preview releases of Swift for Android, enabling you to build Android business logic with the same Swift that you use for Apple platforms. swift.org/blog/nightly-swift… #Android
ケーボ retweeted
Linus TorvaldsとBill Gates、David Cutlerが同席するディナーか。これは確かにスリリングだな。というか、Linusはどちらとも初対面らしい。
linkedin.com/posts/markrussi…
ケーボ retweeted
"Just gonna leave this here," says Microsoft in a new video showing off Windows Vista's Aero Glass design, taking a jibe at Apple's macOS 26 Liquid Glass 👀 #WWDC25
ケーボ retweeted
Swift 6.2 "officially" supports WebAssembly!
Let’s celebrate this milestone together 🥳
apple.com/newsroom/2025/06/a…
ケーボ retweeted
リンカースクリプトと格闘した結果、Swiftでプログラミングしたゲームを通信ポート経由でゲームボーイアドバンスに転送して実機実行できるようになった!!
いわゆるマルチブートと呼ばれるやつで、容量は限られるけど、フラッシュカートリッジに書き込んだりしないでいいのでめっちゃ手軽🚀
ケーボ retweeted
Scratchのソースコードライセンスが、三条項BSDライセンスからAGPLに変更されました。今後、MODにソースコード公開義務が生じます。ソースコードを公開していない一部の商用MODに影響があると思われます。 github.com/scratchfoundation
At Scratch, collaboration and remixing are at the heart of everything we do. Today, we’re excited to announce a significant step in our commitment to the Free and Open Source Software movement. Learn more about our transition to the AGPL: scratchfoundation.org/open-s…
ケーボ retweeted
A big thanks to Amazon @awscloud, who have added their support to the Swift Package Index as a sponsor, joining @Azure, @MacStadium, @emergetools and @context_sdk. It's awesome to see companies working together to make the Swift platform great! swiftpackageindex.com/blog/w…
ケーボ retweeted
2 weeks ago @Apple released weights for Ferret-UI -> a new Multimodal LLM made specifically for iPhone/IOS screens !!
I worked on the HF integration - now available in @HuggingFace transformers - we made it super easy for you to use and try:
FerretUI-Gemma2b: huggingface.co/jadechoghari/…
FerretUI-Llama8b: huggingface.co/jadechoghari/…
@Gradio Demo: huggingface.co/spaces/jadech…
Ferret-UI excels in mobile UI screen understanding with tasks like icon recognition, text locating, and advanced UI interactions — outpacing even GPT-4V
cc @NielsRogge, @merve, for the support!
ChromeOSみたいにDebianVMか
Android 16 will include a Terminal and full Linux VM support with GPU acceleration
notebookcheck.net/Android-16…
ケーボ retweeted
[itmedia.co.jp]「携帯動画変換君」20周年 バージョンアップ試みたが断念、「コードがDelphiで……」 itmedia.co.jp/news/articles/…
ケーボ retweeted
記事を書きました。
・アルコール消毒との勝敗を聞いてくる看護師
・謎の肺検査用機器「肺 Per +」
・地獄の内視鏡検査
など
人間ドックに行ってきた(後編) kitadakyou.com/blog/went-to-… #北田共のブログ
ケーボ retweeted
On September 2, 2008, Google released the beta version of Google Chrome’s freeware browser for Windows. In December 2008, the first stable version of Google Chrome 1.0 was released.
#InternetHistory
ケーボ retweeted
We've been evaluating a number of C++ successor languages for @ladybirdbrowser, and the one best suited to our needs appears to be @SwiftLang 🪶
Over the last few months, I've asked a bunch of folks to pick some little part of our project and try rewriting it in the different languages we were evaluating. The feedback was very clear: everyone preferred Swift!
Why do we like Swift?
First off, Swift has both memory & data race safety (as of v6). It's also a modern language with solid ergonomics.
Something that matters to us a lot is OO. Web specs & browser internals tend to be highly object-oriented, and life is easier when you can model specs closely in your code. Swift has first-class OO support, in many ways even nicer than C++.
The Swift team is also investing heavily in C++ interop, which means there's a real path to incremental adoption, not just gigantic rewrites.
Strong ties to Apple?
Swift has historically been strongly tied to Apple and their platforms, but in the last year, there's been a push for "swiftlang" to become more independent. (It's now in a separate GitHub org, no longer in "apple", for example).
Support for non-Apple platforms is also improving, as is the support for other, LSP-based development environments.
What happens next?
We aren't able to start using it just yet, as the current release of Swift ships with a version of Clang that's too old to grok our existing C++ codebase. But when Swift 6 comes out of beta this fall, we will begin using it!
No language is perfect, and there are a lot of things here that we don't know yet. I'm not aware of anyone doing browser engine stuff in Swift before, so we'll probably end up with feedback for the Swift team as well.
I'm super excited about this! We must steer Ladybird towards memory safety, and the first step is selecting a successor language that we can begin adopting very soon. 🤓🐞







































