Med-Mastodon

Felix Palmen :freebsd: :c64:Still working on <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a>, and currently very busy with improving quality, most of the actual work done inside my <a href="https://mastodon.bsd.cafe/tags/poser" class="mention hashtag" rel="nofollow noopener" target="_blank">#poser</a> library.After finally supporting <a href="https://mastodon.bsd.cafe/tags/kqueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#kqueue</a> and <a href="https://mastodon.bsd.cafe/tags/epoll" class="mention hashtag" rel="nofollow noopener" target="_blank">#epoll</a>, I now integrated <a href="https://mastodon.bsd.cafe/tags/xxhash" class="mention hashtag" rel="nofollow noopener" target="_blank">#xxhash</a> to completely replace my previous stupid and naive hashing. I also added a more involved <a href="https://mastodon.bsd.cafe/tags/dictionary" class="mention hashtag" rel="nofollow noopener" target="_blank">#dictionary</a> class as an alternative to the already existing <a href="https://mastodon.bsd.cafe/tags/hashtable" class="mention hashtag" rel="nofollow noopener" target="_blank">#hashtable</a>. While the hashtable's size must be pre-configured and collissions are only ever resolved by storing linked lists, the new dictionary dynamically nests multiple hashtables (using different bits of a single hash value). I hope to achieve acceptable scaling while maintaining also acceptable memory overhead that way ...<a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> already uses both container classes as appropriate.Next I'll probably revisit poser's <a href="https://mastodon.bsd.cafe/tags/threadpool" class="mention hashtag" rel="nofollow noopener" target="_blank">#threadpool</a>. I think I could replace <a href="https://mastodon.bsd.cafe/tags/pthread" class="mention hashtag" rel="nofollow noopener" target="_blank">#pthread</a> condition variables by "simple" <a href="https://mastodon.bsd.cafe/tags/semaphores" class="mention hashtag" rel="nofollow noopener" target="_blank">#semaphores</a>, which should also reduce overhead ... <a href="https://github.com/Zirias/swad" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/swad</a><a href="https://mastodon.bsd.cafe/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a>

Todd A. Jacobs | RubyistOther than supporting legacy systems or implementing cryptographic password functions that *should* be slow, why aren't your teams using GNU or BSD tar with <a href="https://ruby.social/tags/zstd" class="mention hashtag" rel="nofollow noopener" target="_blank">#zstd</a> compression and <a href="https://ruby.social/tags/xxHash" class="mention hashtag" rel="nofollow noopener" target="_blank">#xxHash</a> or <a href="https://ruby.social/tags/Blake3" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blake3</a> checksums yet? If time is money, please stop wasting either with legacy algorithms when there are faster, more secure, and more trusted options currently available.

𝖆𝖒𝖆𝖗𝖔𝖐 🇨🇿🇪🇺Today <a href="https://mastodonczech.cz/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> has built-in support for 60 hash algorithms 😎 One of the new ones is <a href="https://mastodonczech.cz/tags/xxHash" class="mention hashtag" rel="nofollow noopener" target="_blank">#xxHash</a>. Ultra fast, portable, cool. Why do people still use MD5 or SHA1 for file checksums? <a href="https://mastodonczech.cz/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> package: `apt install xxhash` PHPwatch article ➡️ <a href="https://php.watch/versions/8.1/xxHash" rel="nofollow noopener" translate="no" target="_blank">https://php.watch/versions/8.1/xxHash</a> Official home ➡️ <a href="https://xxhash.com/" rel="nofollow noopener" translate="no" target="_blank">https://xxhash.com/</a>

Todd A. Jacobs | RubyistI'm curious to know what other people do. I know I've asked before, and QT or GTK have been suggested, but are there better options especially for <a href="https://ruby.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a>? I don't think <a href="https://ruby.social/tags/RubyMotion" class="mention hashtag" rel="nofollow noopener" target="_blank">#RubyMotion</a> is still maintained, and even if I switch to <a href="https://ruby.social/tags/CrystalLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrystalLang</a> I still have a <a href="https://ruby.social/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UI</a> issue to solve for.I'm also curious to know if anyone knows of a better <a href="https://ruby.social/tags/xxHash" class="mention hashtag" rel="nofollow noopener" target="_blank">#xxHash</a> <a href="https://ruby.social/tags/RubyGem" class="mention hashtag" rel="nofollow noopener" target="_blank">#RubyGem</a> or wrapper than digest-xxhash-ruby, which is a relatively new project that doesn't seem to have wide adoption.What says the <a href="https://ruby.social/tags/RubyHiveMind" class="mention hashtag" rel="nofollow noopener" target="_blank">#RubyHiveMind</a> on this?

Todd A. Jacobs | RubyistI'm really giving thought to building a <a href="https://ruby.social/tags/crossplatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#crossplatform</a> but <a href="https://ruby.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> friendly <a href="https://ruby.social/tags/GUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GUI</a> for doing file manifests with <a href="https://ruby.social/tags/xxHash" class="mention hashtag" rel="nofollow noopener" target="_blank">#xxHash</a> and focused on <a href="https://ruby.social/tags/XXH3" class="mention hashtag" rel="nofollow noopener" target="_blank">#XXH3</a>. However, I'm still unhappy with the options for GUIs; I could do it as a <a href="https://ruby.social/tags/RoR" class="mention hashtag" rel="nofollow noopener" target="_blank">#RoR</a> or <a href="https://ruby.social/tags/Sinatra" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sinatra</a> app with a database, but I'm not a fan of having to run a <a href="https://ruby.social/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#webserver</a> just to have a GUI. Still, that seems like the easiest path, since (as an example) Shoes4 last released in Nov. 2017, scarpe is pretty new, and no one but me likes Tk and the bindings have poor docs. …

Recent searches

Search options

Administered by:

Server stats:

#xxhash