Shakedown Social

1 post1 participant0 posts today

antenne_berlin<a href="https://fosstodon.org/@libreoffice" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@libreoffice</a> I love <a href="https://mastodon.social/tags/LibreOffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LibreOffice</a> as I believe in <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> and all of our <a href="https://mastodon.social/tags/ToolChain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToolChain</a> should be free for everyone - just like our <a href="https://mastodon.social/tags/data" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#data</a> should belong to ourselves. We want free Tools! We need them more than ever! - Besides that <a href="https://mastodon.social/tags/LibreOffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LibreOffice</a> is the Nr. 1 Open Source Tool I use besides <a href="https://mastodon.art/@inkscape" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@inkscape</a> and <a href="https://floss.social/@GIMP" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GIMP</a> - Thanks for keeping up these Options! It is a lot of work - but so important to all of us! Thank you! <a href="https://mastodon.social/tags/opentools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opentools</a> for Free People! <a href="https://mastodon.social/tags/democracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#democracy</a>

Kevin Karhan :verified:<a href="https://social.vivaldi.net/@ajsadauskas" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ajsadauskas</a> <a href="https://infosec.exchange/@JessTheUnstill" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@JessTheUnstill</a> also <a href="https://infosec.space/tags/BlackBerry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlackBerry</a>'s <a href="https://infosec.space/tags/PlayBook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PlayBook</a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tablet</a> <a href="https://www.youtube.com/watch?v=lYmHId9kJP4" rel="nofollow noopener noreferrer" target="_blank">was released</a> as a accessory screen for their Phones, which gave it "<a href="https://infosec.space/tags/WiiU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WiiU</a>-Effect" in terms of marketing.<ul><li>Plus <a href="https://infosec.space/tags/RIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RIM</a> relying hard on business clients and their proprietary applianced mail systems and having big carriers upsell to business people made them look outdated & quite literally out of touch once <a href="https://infosec.space/tags/iPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iPhone</a> went mainstream.</li></ul>I mean, the hardware was never their problem and <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMS</a>-Typists swear by their <a href="https://infosec.space/tags/BlackberryCurve" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlackberryCurve</a>'s <a href="https://infosec.space/tags/keyboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keyboard</a> but BlackBerry's <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> - just like <a href="https://infosec.space/tags/SymbianOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SymbianOS</a>'s - was just hideous to the point that devs like <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> didn't even want to try making <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apps</a> for those devices.<ul><li>Unlike <a href="https://infosec.space/tags/Mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla</a> fucking up <a href="https://infosec.space/tags/FirefoxOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FirefoxOS</a> by refusing to sell devices to <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developers</a>, by the time RIM & <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nokia</a> came from their high horses, their market shares had been squeezed into mere "rounding errors" by <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iOS</a> and <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> as it was way cheaper and easier to get <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apps</a> developed, tested, sold, bought and use them than on their devices. </li></ul><a href="https://infosec.space/tags/Sony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sony</a> even released some <a href="https://infosec.space/tags/Symbian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Symbian</a> <a href="https://infosec.space/tags/S60" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#S60</a> devices but since they didn't have the same signing keys, one couldn't even <a href="https://infosec.space/tags/sideload" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sideload</a> apps (not to mention they didn't had the <a href="https://infosec.space/tags/OviStore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OviStore</a> on those either!)...

Kevin Karhan :verified:<a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ryanc</a> add the file used to store it into <code>.gitignore</code> is propably not an option?Maybe you can setup a build script that merges that <code>secrets.list</code> into a final build file and exclude that as well?I mean, I did such seperation and build scripting in some cases a while ago...<a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> <a href="https://infosec.space/tags/ESP8266" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ESP8266</a> <a href="https://infosec.space/tags/Secrets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Secrets</a> <a href="https://infosec.space/tags/GitSecrets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitSecrets</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/Firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Firmware</a> <a href="https://infosec.space/tags/Compiling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compiling</a> <a href="https://infosec.space/tags/Toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Toolchain</a> <a href="https://infosec.space/tags/gitignore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitignore</a>

Ben RosengartLike all Apple internships, this is paying work.In 30 years of IT work, I’ve seen fads come and go. There are a few areas that are absolutely evergreen, and an ornament to any resume. Linkers/loaders is one of these, so I’d strongly encourage any qualified early-career software dev to take a look at this.If you’re from an underrepresented background and you want me to go over your resume with you, I’ll be happy to do it. <a href="https://tilde.zone/tags/FediHire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediHire</a> <a href="https://tilde.zone/tags/ToolChain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToolChain</a> <a href="https://tilde.zone/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://sfba.social/@DarGoul/113289784472286550" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sfba.social/@DarGoul/113289784472286550</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> personally I think that <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kernel</a> needs to prioritize what it wants.<a href="https://infosec.space/tags/AFAICT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AFAICT</a> Linux always prioritized clean, lean & human-readable <a href="https://infosec.space/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> code over features, efficiency and sometimes even security.<a href="https://infosec.space/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> being turned into an integral part would extremely complicate the <a href="https://infosec.space/tags/build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#build</a> process and add a shitload of <a href="https://infosec.space/tags/dependencies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dependencies</a> to build <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> or any other <a href="https://infosec.space/tags/minimal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#minimal</a> / <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embedded</a> OS that it would be a net negative by just making the whole <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> bigger, <a href="https://infosec.space/@kkarhan/113056809739446456" rel="nofollow noopener noreferrer" target="_blank">bulkier, more complex and convoluted</a>.

Jarkko SakkinenA typical <a class="hashtag" href="https://social.kernel.org/tag/tui" rel="nofollow noopener noreferrer" target="_blank">#TUI</a> <a class="hashtag" href="https://social.kernel.org/tag/rust" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> application has usually about ~600 dependencies or similar figure. A typical C applications has less than ten. C application might possibly be less "memory safe" language but you can statically analyze every bit and piece of the code base, including dependencies. And by doing hat, you end up getting more verified, and *objectively* more memory safe build artifact ;-) 🤷 What many people especially in the Rust community completely have ignored, one side-effect of this new language popping, was igniting the heyday of the development of static analysis of the C language, which has *vastly* improved both in LLVM and GCC toolchains. Just look at how amazing e.g. GCC 14 is when analyzing C code, and given the low amount of dependencies you can get pretty solid guarantees on safety of your code base. Static analysis of C can *only* get better because the base language is compact and does not really grow anymore. One thing where C is factors more immutable is the language spec itself ;-) Rust language spec on the other hand is the most mutable spec ever invented, and run by a Github pull request process... <a class="hashtag" href="https://social.kernel.org/tag/rustlang" rel="nofollow noopener noreferrer" target="_blank">#rustlang</a> <a class="hashtag" href="https://social.kernel.org/tag/gcc" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a class="hashtag" href="https://social.kernel.org/tag/llvm" rel="nofollow noopener noreferrer" target="_blank">#llvm</a> <a class="hashtag" href="https://social.kernel.org/tag/toolchain" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a>

Recent searches

Search options

Administered by:

Server stats:

#toolchain