Whole-known-network
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> <br />Bonus unpopular opinion: <br />Modern JRPGs have lost the plot; classic jrpgs were at the mechanical level games of resource management and optimization (mainly MP, but also inventory). Endless active inventories (ie other than banks) and too-frequent healing broke JRPGs as games and gave birth to the anime-movie-locked-behind-boring-grinds genre.</p>
<p>This may surprise you as much as it surprised us to make the decision: today's episode of Core Intuition, the podcast that <span class="h-card" translate="no"><a href="https://manton.org/activitypub/manton" class="u-url mention">@<span>manton</span></a></span> and I have run for more than 16 years (!), is the final episode. Enjoy, and thanks to all our listeners, members, and sponsors who have supported us for so many years. <a href="https://coreint.org/2025/01/episode-626-something-has-to-change/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">coreint.org/2025/01/episode-62</span><span class="invisible">6-something-has-to-change/</span></a></p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> <br />Whether mmos can ever be good aside, some minimal improvements:</p><p>- The challenging (pve) content should be solo content; group content should be about having fun in a group. Hard group content will always create toxic behavior.</p><p>- Challenging content should give cosmetic rewards, not more power (these players are already good, they don't need it)</p><p>- Gearing and leveling systems don't belong in multiplayer games; power level should be static (global changes notwithstanding)</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span><br />Another one: Nintendo didn't make anything significant since almost 30 years and living of nostalgia of their fans</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> Small screen gaming sucks, 4K gaming sucks, hate multiplayer looter shooters, Console and pc comparison is pointless, best games were best because of storytelling, mechanics, controls and atmosphere, gaming graphics should not matter...</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> if you put treasures behind a dice roll or a minigame with a limited number of tries, I'm gonna save-scam it and I will use cheats to give myself a lot of lockpicks. And I feel exactly zero shame about it!</p>
<p>I get frustrated with C all the time for being fundamentally a 70s language. It may be I'm about to learn the pain of using a *50s language*.</p><p>(Alternately, I hear modern FORTRAN has all kinds of fancy niceties like operator overloading and might not resemble traditional FORTRAN all that much. But then I have the problem if I pick up a random tutorial it's hard to guess which *decade's* standard it's teaching me from, or if it's the GNU extension, if the GNU extension is that different, etc.)</p>
<p>I went into this thinking: C is basically cleaned up FORTRAN, right? I know C? This should be easy, right? Right off the bat I find there will be a lot of difficulties entirely not of the kind I'm used to in programming. After a brief adventure with accidentally naming my file .f and not .f90 causing horrific and baffling errors, I run a hello world off the Internet. There's a space before the printout. Hm, how do I turn that off?</p><p><a href="https://stackoverflow.com/a/31236043" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">stackoverflow.com/a/31236043</span><span class="invisible"></span></a></p><p>Oh my fuck, *what*?</p>
<p><a href="https://mastodon.social/tags/BabelOfCode" class="mention hashtag" rel="tag">#<span>BabelOfCode</span></a> 2024<br />Week 4<br />Language: FORTRAN</p><p>Confidence level: High</p><p>PREV WEEK: <a href="https://mastodon.social/@mcc/113867584791780280" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@mcc/113867584</span><span class="invisible">791780280</span></a><br />RULES: <a href="https://mastodon.social/@mcc/113676228091546556" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@mcc/113676228</span><span class="invisible">091546556</span></a></p><p>I was very excited about doing TCL this week, but I told myself the first time I get a two-dimensional array problem I'd go FORTRAN, so I guess this week is FORTRAN.</p><p>A friend of mine who did AOC2024 in December noted the early challenges this year were *very* easy. Today's definitely is. I wonder if part 2 will have any depth.</p>