![]() Rust felt like being married as all it does is whine and you can't get rid of it. I have tried many options: PyQt wasted too much memory and was too hard to deal with async stuff through QThreads. During this time, while thinking about it, I realized that all the time that I tried to save by avoiding C++ made me waste even more time. This made all the code that I wrote basically useless as it would have to be rewritten in JS to be compatible with the new version (really bad timing for me to write it in Sciter at that time).Īfter trying the JS version, it felt even buggier than the TIScript version, and at this time I got sick (stomach related) and had to stop developing it for about a year. Then I decided to rewrite it in Go + Sciter, but when it was becoming usable, as it had voice channels, custom avatars, custom themes, and layout modification, embedded images, custom user roles, file upload, and Markdown support, Sciter's creator decided to end support of its TIScript version, which was a JS alternative for controlling the UI. The problem is that I made a few mistakes as I started by writing the client in Go + GTK3, and at some point, it was very buggy (especially in Windows) and hard to debug. I have been building a Discord/Slack/Mumble alternative since 2020, which is something that I wanted to do since around ~2008 but I didn't have the skills back then. Some day we'll have a decent chat that doesn't give you problems you don't need. ![]() See Huddles for example.ĭisclaimer: I hate using Slack too and personally wish it wasn't a part of my day to day. I think Slack sees these problems and attempts to address them, even if it isn't perfect. > So we have hours longs Slack discussions that spare us minutes of reading a wiki page or discussing on a phone call. You just annoy a small, yet outspoken subset of people while doing it. To a certain degree this is an indexing problem as much as it is a problem with the communication medium, but if you bring together all of your communication into a central hub you solve this issue plus many others. Does something exist as an issue, a discussion, a wiki, in the code itself, a comment on the PR? What's the right place for something to go? These aren't trivial questions, especially for large orgs. If I could only tally up the lost hours I've spent trying to track down whether a comment was made on the wiki, or in chat, or via email, or in the PR.Įven using Github alone has this problem. Yet at the same time, it creates its own set of problems. > Public articles - Pull requests - Issue trackers - Internal Wiki - Emails - Chat - Phone calls - Visio - Face to face ![]() > There is a reason why we have multiple communication medium. To me it is the gold standard for everything. Instead, maybe click around in the docs, don't read so much but spend 5 clicking on all the pages, and skim them, you'll see what I mean. But one that is hard to show off in screenshots because unless you show 50 screenshots of custom configurations, you'll sell it short. As long as that only exists on Windows, I'll always run windows, if even just in a VM with access to the host filesystem. Why would I want to go back from that? Speaking of Amiga and continuous progress, for me the god king emperor of interfaces is Directory Opus. Then came Workbench 2.0, then 3.0 with Magic User Interface Icons, a clear progression. this is my HN stylesheet: įlat design is Workbench 1.3. For me, subtle gradients and borders and such are not just a matter of being prettier (to me), but they really help the eye along. ![]() Though that's probably more high knob density than information density, I wouldn't want to have it any other way. What would you consider a high information density program? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |