Lingolol

0 posts0 participants0 posts today

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> was released 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!)...

Dr. Brian CallahanA new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> post appears!I built a native GCC 14.2.0 for Mac OS X 10.4 Tiger PowerPC.<a href="https://briancallahan.net/blog/20250329.html" rel="nofollow noopener noreferrer" target="_blank">https://briancallahan.net/blog/20250329.html</a><a href="https://bsd.network/tags/macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macos</a> <a href="https://bsd.network/tags/macosx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macosx</a> <a href="https://bsd.network/tags/tiger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tiger</a> <a href="https://bsd.network/tags/powerpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powerpc</a> <a href="https://bsd.network/tags/power" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#power</a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://bsd.network/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://bsd.network/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://bsd.network/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://bsd.network/tags/netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a> <a href="https://bsd.network/tags/dragonflybsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dragonflybsd</a> <a href="https://bsd.network/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://bsd.network/tags/solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solaris</a> <a href="https://bsd.network/tags/illumos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#illumos</a> <a href="https://bsd.network/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://bsd.network/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a> <a href="https://bsd.network/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compiler</a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compilers</a> <a href="https://bsd.network/tags/assembler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assembler</a> <a href="https://bsd.network/tags/linker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linker</a> <a href="https://bsd.network/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://bsd.network/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://bsd.network/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://bsd.network/tags/gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnu</a>

Johannes BrakensiekThe simplicity of <a href="https://fosstodon.org/tags/UNIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UNIX</a> has healed me from using <a href="https://fosstodon.org/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a>. Looks like these days I'd rather write a <a href="https://fosstodon.org/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> tool (or even use <a href="https://fosstodon.org/tags/GObject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GObject</a>) than use Java tools again. (I still like <a href="https://fosstodon.org/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> as a language, but the <a href="https://fosstodon.org/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> is incomprehensible.)

Kathy ReidEach year, I write a post on the <a href="https://aus.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> I'm using - the hardware, products and platforms that help me be productive and effective in whatever role I happen to be in. In this year's post, I cover <a href="https://aus.social/tags/NocoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NocoDB</a> and <a href="https://aus.social/tags/Keychron" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keychron</a>. <a href="https://blog.kathyreid.id.au/2022/11/13/state-of-my-toolchain-2022/" rel="nofollow noopener noreferrer" target="_blank">https://blog.kathyreid.id.au/2022/11/13/state-of-my-toolchain-2022/</a>

Recent searches

Search options

Administered by:

Server stats:

#toolchain