Do you happen to own one? If yes, how do you feel about it?
For example, in the PineTime there is a heart rate monitor, but it's too slow and imprecise. Notifications work great, and the battery lasts 20 days or more. How about the Bangle.js 2?
I'm definitely no expert so I might not be the best person to try and help, but if you want to try having a 1 on 1 chat to fix it, feel free to send me a PM.
Isn't rescaling usually done by the display driver? I am fairly certain this is the case for external displays. Are laptop displays any different?
Edit: with "display driver" I mean the hardware chip behind the display panel, dedicated to converting a video signal to the electrical signals necessary to turn on the individual pixels.
As a web developer, I noticed that some elements such as very big tables struggle to render on 4K but are absolutely fine at 1080p. I would assume that means the CPU and/or GPU are more taxed to draw at higher resolution, and therefore I assume they would draw more power. I might be mistaken. Do you speak by experience?
Good separation between business logic and UI without effort, cross-platform UI in any language, possibility to turn it into a web-accessible service in the future, great choice of UI frameworks and battle-tested components if you decide to go for a web framework and language.
As an example of a successful software that followed this approach: Synchthing. All versions run a local web service in the background. The Desktop version just opens a browser on the index page. The Android version is a native app that calls the exposed REST API on localhost, bypassing the web UI.
As an example of a much more complex software, albeit not FOSS: EasyEDA. It's a web software, but it also comes as a desktop app (which I never tried) which I assume is not much more than a frame for the web view.
My recommendation: write the UI with React on Vite in TypeScript, and write the business logic in your general purpose language of choice (mine would usually be C#).
If it makes sense for your software, please consider giving it a web interface and turning it into a localhost-only web-service.
I thought so. Although almost nothing for modern standards, 60MB is not exactly tiny. Sorry about that.
On a different note, a repository is always a good thing imho. If you'd rather not have to worry about the dependency-pull step you can always include the dependencies with your sources, or just limit your code to using features included in the standard library.
I've never had the chance to work with the RAW format, but I think Photoprism should handle it transparently. Depending on your area of knowledge, the setup might feel a bit convoluted though.
I work as a professional developer in .NET on Windows, and in my free time I develop in .NET on Linux as a hobby.
Unfortunately I would say the .NET development experience on Linux (with VSCode) is slightly inferior compared to on Windows (with Visual Studio).
For instance there is no support for SourceLink during development, only during debug. And on VSCode the "go to definition" to third party assemblies works only for one level deep, whilst on Visual Studio it works for any depth level.
It is certainly still a great experience on Linux, but not «better than Windows» in my opinion. If you have any recommendations to improve it please share, I would be very grateful.
Ah I get what you mean, I used to share your same view. I used to think that the MIT license was more free than GPL for the reasons you mentioned.
When Google started working on Fuchsia OS and they said it will be MIT license, I started to get worried that smart products producers would start using it instead of Linux. Then they wouldn't need to release the source code to customers as the software would no longer be GPL.
The difference is that MIT gives more freedom to the producers, while GPL gives more freedom to the consumers.
Personally, my sympathy goes to consumers, not producers, thus I understood why people say GPL is more free than say Apache or MIT.
Licenses such as MIT, Apache, MPL, etc... are a double-edged sword. 😬
bruce965
joined 2 years ago
Well... that would make sense. But it's much much easier to just do it preemptively. The browser API to check how much memory is available are quite limited afaik. Also if there are too many elements the browser will have to do more work when interacting with the page (i.e. on every rendered frame), thus wasting slightly more power and in a extreme cases even lagging.
For what it's worth, I, as a web developer, have done it too in a couple occasions (in my case it was absolutely necessary when working with a 10K × 10K table, way above what a browser is designed to handle).