Thank you! That means more than you know. :) I've thought about an Android client. It would have the same problem that exit-node support would have: Tela is currently engineered as a user-space alternative to Tailscale. However, as I mentioned in another reply here, I've gotten so fond of a lot of the other features of Tela that I might consider adding support for low-level features that require kernel support. It might not be 1.0, but I'm open to suggestions.
Apikulture. A small, fast alternative to Postman/Insomnia that doesn't upload your data to the cloud.
Written in C++ and Slint, it was also a testbed of slint as an UI framework. Having used wxWidgets in the past, and Qt recently, it is certainly a different thing. I just wish there was a native C++ alternative to slint.
I need to integrate the CI to produce binaries, but you can compile it yourself for now.
It doesn't matter, one way or the other.
The overall market share will decide.
In some cases, I think good code will be a decisive factor. Think Steam launcher Vs Epic.
Epic doesn't have good code. Their performance suffers in consequence.
In other cases the users are so trapped it makes no difference. MS Outlook and Teams is the prime example of this.
People do these kind of decisions every day, every second.
Shit bloated code is one of the reasons Epic Launcher is extremely behind in market share when compared to Steam.
Sure, they ship their product fast. They can iterate faster than Valve. They also add technical debt with each iteration.
Also: we are almost all using a Chrome derived browser instead of Firefox, old IE, old Opera, because of performance and quality. They just won the internet because of the quality of their code. Besides that, all browsers let you browse the internet.
When people can choose, they choose quality most of the time.
I'm sorry to get into this conversation, but the performance of a model is some orders of magnitude lower (meaning it requires greater amounts of specific computing power) than all the network stack of all the nodes involved in the internet traffic of some particular request.
Meaning: these 5000 tokens consume tiny amounts of energy being moved all around from the data center to your PC, but enormous amounts of energy being generated at all. An equivalent webpage with the same amount of text as these tokens would be perceived as instant in any network configuration. Just some kilobytes of text. Much smaller than most background graphics. The two things can't be compared at all.
However, just last week there have been huge improvements on the hardware required to run some particular models, thanks to some very clever quantisation. This lowers the memory required 6x in our home hardware, which is great.
In the end, we spent more energy playing videogames during the last two decades, than all this AI craze, and it was never a problem. We surely can run models locally, and heat our homes in winter.
It's comparing cables, which everyone with some experience knows they make no difference.
I expected something more substantial, like a comparison of different IEM price tiers, or a comparison of different DAC chips, or something else that actually matters.
I used to dislike TCL/Tk because of the ugly toolkit and also language.
Now I wish it had won instead of the unholy abomination we have with Electron apps.
reply