Readit NewsIn the past, I've used MORT to play some Japanese MMO game. In-place overlay makes it easier to actually play the game instead of doing dictionary lookup on the side.
These days I stopped using realtime translator and just embrace the slow pace of learning these languages while enjoying the game story.
> improved CPU schedulers for responsive gameplay,
on their homepage https://bazzite.gg/
Does these custom scheduler bring noticeable gains during usage? My previous linux desktop was a non-gaming distro, so I'm a bit curious on these fancy stuffs.
- BORE, CachyOS scheduler: https://wiki.cachyos.org/cachyos_basic/why_cachyos/#advanced...
- LAVD, SteamOS scheduler: https://www.igalia.com/2025/11/helpingvalve.html
This brings a more clear divide between fully native iOS applications and React Native -style "build once and cross-compile" -platforms.
What I don't understand is how this thing does keyboard input.
At 3:42, the video simply says, "And, yes, there's a way to do keyboard input," without elaborating on how. What sorcery is that? There must be something outside the type system translating keyboard input into TypeScript types…??
[0]: https://github.com/MichiganTypeScript/typescript-types-only-...
BTW something on the game is making my CPU go 100%. I'm on Firefox, Linux and in the JS console I can see "Unexpected value translate(52.460687992082626%, 52.24894125700998%) scale(1.0398801892701597) parsing transform attribute." warning being printed nonstop.
> 7-Zip, Bandizip and Winrar are tightly packed around very similar performances of 17 seconds, while PeaZip fast drag and drop implementation shows a clear performance advantage in this scenario completing the extraction in 13,6 seconds. WinZip provides an intermediate performance at 15,5 seconds.
Serious question though. Who is this for?
I’ve done mobile app dev in all the popular ways - native, flutter, and react native.
Both flutter and react native bring up a ton of issues anytime the app becomes more complex than rendering a list with some detail pages.
I wrote so much custom code bridging gaps.
Swift and Kotlin make native dev so easy and straightforward.
With flutter (which I have the most experience with along with native) I had to anyway write bridge code for handling both platforms.
I think considering how easy it is to write APIs, isn’t it better to just use native for both platforms to deliver a fantastic user experience built on those APIs?
Is this another project that’s suitable for simple apps or will it actually be useful for very complex UIs and deep device integration. I mean flutter still has open issues around scroll to top breaking which I fixed with custom bridge code. It’s impossible to get issues addressed.
Like say it takes 3 days to make a complex UI. Then a week or more to write and test the bridge code. I’d rather take 6 days writing platform appropriate code and save a day or more of pain. And when that breaks fix it. Over time this adds up to a lot of saved time I think.
Speaking with my experience with Expo, this kind of framework works great for their purpose in enabling a small team of engineers working closely with products and business analyst to deliver features as fast as possible.
From business perspective, turns out not everything needs to be a blazing fast native code. That means if you can write code once and it will run in other platforms with minimal changes, you save some time. More time to ship more features!
In a zero sum market where every extra features could bring more customers, this could become important factor when picking the tech stack. More so when you're running on investors money and need to make profit ASAP.
MacOS however truly takes the cake. An OS that’s great for creative softwate, working with images, video, audio and so on, and every single music player is something designed by aliens and/or buggy and/or missing some basic features. I went through ~five different players just to find one that has a waveform seekbar, eventually finding it in quodlibet, which while somewhat functional fits in the designed by aliens part. Baffling.
Technically fooyin also builds on macOS, but it's not officially supported yet, there's some works here[1] and there[2].
[0]: https://github.com/fooyin/fooyin
[1]: https://github.com/fooyin/fooyin/pull/476
[2]: https://github.com/fooyin/fooyin/pull/579