Shakedown Social

Kevin Karhan :verified:<a href="https://mas.to/@DenOfEarth" class="u-url mention" rel="nofollow noopener" target="_blank">@DenOfEarth</a> <a href="https://mastodon.sdf.org/@ytc1" class="u-url mention" rel="nofollow noopener" target="_blank">@ytc1</a> <a href="https://mastodon.social/@aka_pugs" class="u-url mention" rel="nofollow noopener" target="_blank">@aka_pugs</a> well <a href="https://infosec.space/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> owned the workstation market because <a href="https://infosec.space/tags/Vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vendors</a> like <a href="https://infosec.space/tags/SGI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SGI</a> & <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sun</a> failed to innovate...<ul><li>Abeit sgi hals self-inflicted that by removing the reasons to buy their stuff when they switched to <a href="https://infosec.space/tags/Itanium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Itanium</a> <a href="https://infosec.space/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPU</a>|s and <a href="https://infosec.space/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> <a href="https://infosec.space/tags/GPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPU</a>|s and not developing <a href="https://infosec.space/tags/IRIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRIX</a> any further! </li></ul><a href="https://infosec.space/tags/SunMicrosystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#SunMicrosystems</a> at least didn't stall in terms of <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a>, but once <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> acqured them and started shaking down Sun Technology users for "<a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> infringement" and "License Violations" they basically made using anythibg but <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> a bad choice on <a href="https://infosec.space/tags/Servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Servers</a>!<ul><li>Meanwhile <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> to this day doesn't even halfass <a href="https://infosec.space/tags/Servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Servers</a> anymore and is constantly giving customers and espechally professionals the middle finger in terms of <a href="https://infosec.space/tags/Repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Repairability</a> & <a href="https://infosec.space/tags/Maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maintainability</a>!</li></ul>

Kevin Karhan :verified:<a href="https://dragonscave.space/@TheQuinbox" class="u-url mention" rel="nofollow noopener" target="_blank">@TheQuinbox</a> nodds in agreement to me "<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>" coding ruins the <a href="https://infosec.space/tags/readability" class="mention hashtag" rel="nofollow noopener" target="_blank">#readability</a>, <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a> and <a href="https://infosec.space/tags/auditability" class="mention hashtag" rel="nofollow noopener" target="_blank">#auditability</a> of the <a href="https://infosec.space/tags/sourcecode" class="mention hashtag" rel="nofollow noopener" target="_blank">#sourcecode</a>, and I do require this.<ul><li>Espechally for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>!</li></ul>

Gary "grim" KramlichHoly crap! I just noticed we're up to 130 unit test suites in <a href="https://fosstodon.org/@pidgin" class="u-url mention" rel="nofollow noopener" target="_blank">@pidgin</a> 3 now! Compare that to the 7 suites we have in Pidgin 2!This is what we've been talking about when we've been saying that we're making the code easier to maintain. The code has been reworked so that we can actually unit test way more of it and we will continue to add more tests as we move forward!<a href="https://mastodon.social/tags/Pidgin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pidgin</a> <a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://mastodon.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTest</a> <a href="https://mastodon.social/tags/Maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maintainability</a> <a href="https://mastodon.social/tags/techdebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#techdebt</a>

Kevin Karhan :verified:<a href="https://m.ai6yr.org/@ai6yr" class="u-url mention" rel="nofollow noopener" target="_blank">@ai6yr</a> nodds in agreement whereas the "akshual coding" is "relatively simple" if one doesn't mind <a href="https://infosec.space/tags/readability" class="mention hashtag" rel="nofollow noopener" target="_blank">#readability</a>, <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a> or using understandable variablr names...<ul><li><a href="https://infosec.space/tags/Testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Testing</a> and having <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> as well as <a href="https://infosec.space/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a> (even just <a href="https://infosec.space/tags/comments" class="mention hashtag" rel="nofollow noopener" target="_blank">#comments</a> in <a href="https://infosec.space/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a>!) Is way more important, cuz that'll make it maintainable!</li></ul>Testing can be automated if one builds and documebts the tests that is...<ul><li>So yeah, one does not remove or automate away these things easily, cuz even the best <a href="https://infosec.space/tags/autogenerated" class="mention hashtag" rel="nofollow noopener" target="_blank">#autogenerated</a> documentation needs <a href="https://infosec.space/tags/proofreading" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofreading</a> and <a href="https://www.youtube.com/watch?v=j-6N3bLgYyQ" rel="nofollow noopener" target="_blank">testing for correctness and completeness</a>!!!</li></ul>"<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>" can't do this because those <a href="https://infosec.space/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLM</a>|s don't learn organically but merely act as "<a href="https://infosec.space/tags/StochasticParrot" class="mention hashtag" rel="nofollow noopener" target="_blank">#StochasticParrot</a>" and not as intelligent beings that is able or even willing to transfer * exchange information freely...

Kevin Karhan :verified:<a href="https://linuxrocks.online/@OpenComputeDesign" class="u-url mention" rel="nofollow noopener" target="_blank">@OpenComputeDesign</a> same with many other things.<ul><li><a href="https://infosec.space/tags/GluedInBatteries" class="mention hashtag" rel="nofollow noopener" target="_blank">#GluedInBatteries</a> instead of <a href="https://infosec.space/tags/ToolfreeSwappableBatteries" class="mention hashtag" rel="nofollow noopener" target="_blank">#ToolfreeSwappableBatteries</a> are just an <a href="https://infosec.space/tags/excuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#excuse</a> for <a href="https://infosec.space/tags/AntiRepairDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntiRepairDesign</a>. points at <a href="https://infosec.space/tags/Vaio" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vaio</a> <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#P11Z</a> & <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> <a href="https://infosec.space/tags/FP3plus" class="mention hashtag" rel="nofollow noopener" target="_blank">#FP3plus</a></li><li><a href="https://infosec.space/tags/SolderedDownRAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SolderedDownRAM</a> & <a href="https://infosec.space/tags/SolderedDownSSDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SolderedDownSSDs</a> were never valid outside <a href="https://infosec.space/tags/EmbeddedDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmbeddedDevices</a> that need to survive harsh envoirments. points at a rugged, ATEX-certified PTT radio for industrial plants</li><li><a href="https://infosec.space/tags/Repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Repairability</a> saves lives! points at Medical Devices</li><li>Want to have more <a href="https://infosec.space/tags/battery" class="mention hashtag" rel="nofollow noopener" target="_blank">#battery</a> <a href="https://infosec.space/tags/runtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#runtime</a>? We have solutions for that for decades. points at <a href="https://infosec.space/tags/EeePC" class="mention hashtag" rel="nofollow noopener" target="_blank">#EeePC</a> and a tool-free, swappable, <a href="https://infosec.space/tags/aftermarket" class="mention hashtag" rel="nofollow noopener" target="_blank">#aftermarket</a>, high-capavity battery</li></ul>Personally I'm so pissed off amidst the ongoing <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> that I really need to get the <a href="https://infosec.space/tags/NUCbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#NUCbook</a> off the ground before my <a href="https://infosec.space/tags/X230tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#X230tablet</a> dies. <a href="https://github.com/KBtechnologies/NUCbook" rel="nofollow noopener" translate="no" target="_blank">https://github.com/KBtechnologies/NUCbook</a><ul><li>Tho if I had to choose a <a href="https://infosec.space/tags/Laptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptop</a> right now that I can buy in stores I'd pick the <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> / <a href="https://infosec.space/tags/Framework13" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framework13</a> hands-down because it's (sadly!) the by far best <a href="https://infosec.space/tags/Notebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Notebook</a> in terms of <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#repairability</a> & <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a>!</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@FirewallDragons" class="u-url mention" rel="nofollow noopener" target="_blank">@FirewallDragons</a> I think <a href="https://infosec.space/tags/RightToRepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#RightToRepair</a> must necessitate any <a href="https://infosec.space/tags/RightToModify" class="mention hashtag" rel="nofollow noopener" target="_blank">#RightToModify</a>, because <a href="https://infosec.space/tags/RepairReuseRecycle" class="mention hashtag" rel="nofollow noopener" target="_blank">#RepairReuseRecycle</a> necessitates <a href="https://infosec.space/tags/Upcycling" class="mention hashtag" rel="nofollow noopener" target="_blank">#Upcycling</a> and thus using <a href="https://infosec.space/tags/AftermarketFirmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#AftermarketFirmware</a>.<ul><li>And the "legitimate objections" have long been adressed by <a href="https://infosec.space/tags/ETSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#ETSI</a> et. al. mandating a <a href="https://infosec.space/tags/Lockdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lockdown</a> on <a href="https://infosec.space/tags/Baseband" class="mention hashtag" rel="nofollow noopener" target="_blank">#Baseband</a> / <a href="https://infosec.space/tags/Wireless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wireless</a>-Chipset firmware to "enshure compliance"... </li></ul>Needless to say I think even that is overreach, as regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> not only can but will enforce spectrum regulations and pursue violators by all legal means, so it's not as if there is a rampant flood of <a href="https://infosec.space/tags/SpectrumViolations" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpectrumViolations</a> amd no means to stop them - far from it.<ul><li>Personally I want to see a mandate for the maximum possible extend of <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a> and <a href="https://infosec.space/tags/modifyability" class="mention hashtag" rel="nofollow noopener" target="_blank">#modifyability</a> only limited by legal (regulatory compliance) and technical limitations...</li></ul>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> I mean, isn't the whole point of <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> being written in <a href="https://infosec.space/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> to have <a href="https://infosec.space/tags/ReadableSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReadableSource</a> that is <a href="https://infosec.space/tags/maintainable" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainable</a>?<ul><li>Like Linux sacrifices a lot in terns of <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> and <a href="https://infosec.space/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#performance</a> for <a href="https://infosec.space/tags/readaility" class="mention hashtag" rel="nofollow noopener" target="_blank">#readaility</a> and <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a> when compared to other <a href="https://infosec.space/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a>-esque kernels and that - alongside being relatively "permissively" licensed - made it so successful as it is today...</li></ul>

Sean FenianThis is an open request to <a href="https://plasmatrap.com/tags/anyone" rel="nofollow noopener" target="_blank">#anyone</a> <a href="https://plasmatrap.com/tags/building" rel="nofollow noopener" target="_blank">#building</a> <a href="https://plasmatrap.com/tags/anything" rel="nofollow noopener" target="_blank">#anything</a>. And TOTALLY DOES NOT IN ANY WAY refer to my own employer in any way. (You believe me, right?) FOR THE LOVE OF ALL THAT'S HOLY, if you are going to build a large <a href="https://plasmatrap.com/tags/commercial" rel="nofollow noopener" target="_blank">#commercial</a> <a href="https://plasmatrap.com/tags/product" rel="nofollow noopener" target="_blank">#product</a> which depends at its very core upon a <a href="https://plasmatrap.com/tags/database" rel="nofollow noopener" target="_blank">#database</a> <a href="https://plasmatrap.com/tags/engine" rel="nofollow noopener" target="_blank">#engine</a>, and whose <a href="https://plasmatrap.com/tags/performance" rel="nofollow noopener" target="_blank">#performance</a> and <a href="https://plasmatrap.com/tags/maintainability" rel="nofollow noopener" target="_blank">#maintainability</a> will depend critically on how properly and correctly you designed your data structures and use the database, FOR FUCK'S SAKE LEARN HOW THE DATABASE WORKS BEFORE YOU START. Don't just fucking YOLO it.

Geert BevinIt's really cool to be getting the question: "Why choose <a href="https://uwyn.net/tags/RIFE2" class="mention hashtag" rel="nofollow noopener" target="_blank">#RIFE2</a> over other popular frameworks?" already. So I wrote up a page that hopefully answers that: <a href="https://github.com/gbevin/rife2/wiki/Why-RIFE2" rel="nofollow noopener" target="_blank">https://github.com/gbevin/rife2/wiki/Why-RIFE2</a><a href="https://uwyn.net/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#java</a> <a href="https://uwyn.net/tags/framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#framework</a> <a href="https://uwyn.net/tags/productivity" class="mention hashtag" rel="nofollow noopener" target="_blank">#productivity</a> <a href="https://uwyn.net/tags/maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainability</a>

Recent searches

Search options

Administered by:

Server stats:

#maintainability