Incredible journalism.
60 Minutes has a convicted felon go undercover to talk to “pardon brokers,” people who will try to get you a pardon from Trump if you pay them.
This administration’s corruption has created entire new job categories.
"Dying for your country is a patriotic fairy tale. In reality, you will bleed out in the mud like a butchered dog for absolutely nothing." - Ernest Hemingway
it'd be nice if anime & manga fans took an academic interest in anime and otaku studies instead of treating the medium purely as entertainment or arguing about surface-level fandom discourse
@Felixszalonna We also used to be on tiny corners of the internet. Today, Crunchyroll is a business. Doujin games are landing on Steam. This an open field now. Everyone's finding pockets they can belong in. Best thing you can do is create a good one for yourself.
@NicoparaDEV @Jonathan_Blow That's part of it but it's also about how massively bloated dev teams have led to dangerous amounts of specialisation, drying up the pipeline of generalists can pivot successfully to a new environment where teams need to be leaner to control costs.
Eh, I'm a lot less reverential of the classics nowadays. Oh, you can't understand Eva without watching Ultraman and Ideon. But can you really grasp Tomino's work without a background in 70s anime? Tiger Mask is great and all but it's obviously influenced by prior radio drama.
I think I have said the same thing, but
it seems that the creator didn't have the theme like "the fear of totalitarianism" or "fascist dystopia" in Kerberos Saga.
The world of The Red Spectacles, Kerberos, JIN-ROH, Panzer Cop, etc is basically an allegory of real post-war Japan.
I keep my AGENTS.md (and skills) concise and unambiguous. Basically what I would tell an intern before they touch my codebase. Things like "Prefer short names (ideally one word) for tables, columns, symbols, and files.".
The agent doesn't always honor all of it, but neither would an intern.
https://t.co/a5ZEG25uDF
Sonny Rollins wrote a new essay about jazz. Today, VF published it, exclusively—a day after his death, at 95–along w/Steve Schapiro’s photos, from his new book, JAZZ. @sonnyrollins@SchapiroPhoto#jazz#jazzphotography#sonnyrollins
https://t.co/nOoM3yKGkj
In Odin, it's common to see people try to emulate sum types (`enum` in Rust). Odin opted for `union` types instead, which solve a similar set of problems but are interacted with a little differently. A `union` is a set of `distinct` types, while a sum type is a summation of labelled values/types. Both can only inhabit one variant at a time, and the total number of states is the sum of the states of the variants.
TL;DR: Prefer table-oriented thinking rather than trying to model type hierarchies.
People with experience with sum types tend to reach for them everywhere, even when it's not a good idea. As many people know, I'm in the "fat struct" camp, and the short reason is: flat record/product types minimize the combinatorial possibilities of control flow when dealing with related things (at the possible expense of increased possible states). Keeping things flatter lets you see patterns much more easily.
The desire to use a sum/union usually comes from a love of modelling type hierarchies, the same affliction common in OOP languages. OOP models an open set of behaviours through types; a sum/union models a closed set of variants. These patterns do come up, but embedding that explicit hierarchy directly into the type system isn't necessarily a good engineering decision.
A good example of when using a sum/union for different kinds of messages might be a bad idea:
Message_Sender :: struct {sender_id: int, message: string, timestamp: time.Time}
Message_Receiver :: struct {received_id: int, message: string, timestamp: time.Time}
Message :: union {Message_Sender, Message_Receiver}
Both variants share effectively the same fields and will be treated the same way. In fact, every field could be accessed without knowing the variant's type. The flattened approach:
Message_Kind :: enum { Sender, Receiver }
Message :: struct {kind: Message_Kind, id: int, message: string, timestamp: time.Time}
This might seem minor, but it's a fundamentally different way of thinking. It's closer to reasoning about tables in a database rather than a type hierarchy. A common complaint is the loss of "safety", but was the original version actually providing anything useful, or just embedding a hierarchy where it didn't need to be?
There are plenty of cases where a sum/union is the right choice, especially around memory layout and access. But the default position many people take—reaching for sum types first—is a poor one, and not just in a language like Odin.
P.S. Odin's `union` is not technically a "union" for two reasons: it has a `nil` state by default (disableable with `#no_nil`), which is useful given the rest design of the language; and the compiler disallows `union{int, int, f32}` because variants must be distinct types; allowing duplicates would not be useful in practice and would almost certainly be a bug.
btw, there is JIN-ROH's spiritual remake by the JIN-ROH original writer himself.
It's Harahara-dokei no Shoujo.
Unlike JIN-ROH, this story is told from the perspective of the terrorist girl.
Very insightful & nuanced review.
It’s true that Japan can be very strict about rules & procedures. As I mentioned in my post two posts ago, if there were a WAFFLE HOUSE in Japan, they probably would never have sold me their actual physical menu as a souvenir due to store policy, even if I asked.
The game market is unique in some ways as well, but when it comes to PC gaming, Western games are actually quite widespread and sell very well here.
As for living in Japan, I do think it can suit some people more than others. It’s true that work tends to occupy a relatively large portion of people’s lifestyles here, and more importantly — although this exists in every country to some extent (this is an important premise, and I’ll say it again: this exists in every country) — Japan comparatively tends to reward “personal relationships and internal politics” over pure competence when it comes to promotions.
In other words, there’s definitely a “the nail that sticks out gets hammered down” culture, and I think a lot of people struggle with that.
(And by the way, situations where someone who 99 out of 100 people would consider completely incompetent — someone basically unknown in the industry except for endless stories about their incompetence — somehow gets promoted into an absurdly high executive position, leaving entire organizations shocked and dumbfounded… those situations genuinely exist around us. The kind of unbelievably bad personnel placement that feels like it belongs in a movie scene.)
The use of Judeo-Christian occultic imagery and themes isn't really a "right-wing" thing per se, but rather falls into a broader fascination with western esotericism in Japan dating back to about the 1970s. It's not because Anno and Arakawa are "based and trad" or whatever.
Princess Sapphire did not have magic of any kind, so the idea that she's the origin of the magical girl is as nonsensical as Tezuka inventing shōjo.
The death of genre discourse which can be traced back to the emergence of The Sandwich Alignment Chart ~ 2016 an utter disaster!