Welcome to SumatraType

Why opt for the clarity of TypeScript when ambiguity can offer so much more... character? Introducing SumatraType – where type safety meets type danger in a riveting dance of coding drama. Indeed, strong typing is for the weak.

"Features"

• Optional Typing: Specifying types? Too mainstream. Let's just guess!
• Generics...Sort of: Dive into the world of "Generish". They look like generics, but don't really do anything.
• Interfaces but Fuzzier: With "Surfaces", you can kind of define the shape of your objects...if you squint hard enough.
• Mixed Types: Who needs a union type when you can have a confusion type?
• Any and Never: They mean something. We're not sure what, but they're there!
• Decoys: Like decorators, but they just add random comments to your classes.
• TypeScript Compatibility Mode: Turns SumatraType back into TypeScript. But why would you want that? *Feature has not been tested.*
• LRun-Time Compile-Time Checks: Check your types at runtime but call it compile-time. It’s a perception thing.
• Enums...or Enumerations? Does it list values or does it narrate a lengthy tale about them? It's a surprise.
• Null and Undefined: Now with added vagueness! Introducing "Nullish" and "Undefinedish".

The Legend of SumatraType

In an era where SumatraScript redefined logic, SumatraType emerged to challenge clarity. Where TypeScript offered a lighthouse, SumatraType promised a funhouse mirror – a reflection of reality, but twisted, turned, and thoroughly entertaining.

If you felt SumatraScript was an unpredictable whirlwind, welcome to its stormy cousin. Embrace the ambiguity, code in riddles, and let's bring back the "fun" in type functions!

Ecosystem

SumatraType seamlessly, sort of, integrates with SumatraScript. Combine the bewildering power of both for an experience that's... unforgettable. Also, try SCS for styling – after all, clarity in design is overrated.

Take a leap into the uncertain waters of SumatraType. It's about the journey, not the destination, right?