Tim Sweeney
21.9K posts

Tim Sweeney
@TimSweeneyEpic
Epic Games founder and CEO. Doesn’t know when Attack on Titan is returning to the Fortnite item shop.









Former Epic Games vice president Steve Allison has joined Saber Interactive as chief business officer gamesindustry.biz/former-epic-ga…







The EU's General Court dismissed Apple's challenge to its gatekeeper designation last week. Apple argued it runs five App Stores, one for each device, and only the iOS one was big enough to qualify. The judges said they all do the same thing and brought them all under the Digital Markets Act. In May, AEI's Bronwyn Howell read the Commission's own review of the law, which found it fit for purpose and proposed no changes. The review relied on stakeholder submissions but included no apparent input from regulated companies or consideration of research finding that the DMA had chilled innovation. Read her work here: aei.org/technology-and…






The current Haskell drama centers on a July 10 blog post by avi_press (Scarf founder + Haskell Foundation board member). After 7 years in production, Scarf is moving new work to Python. Key reasons: Haskell's long compile times + build friction have become major bottlenecks for fast LLM/agent-driven development (parallel exploration, quick iteration, cold starts). Existing Haskell code stays; new routes go to Python. Productivity jumped. Avi stresses he's still deeply committed to Haskell and wrote the post to urge the community to prioritize AI-era improvements: faster builds, more agent-friendly tooling, better docs/examples for models, etc. The post triggered sharp backlash. Some see it as betrayal or an attack on the language, with personal attacks flying. josecalderon (former Haskell Foundation director) posted a thread calling the reactions "too much" and "unacceptable," urging people to accept that strong Haskell advocates can still choose different engineering tradeoffs without it being disloyal. It's mostly a heated debate over language priorities as AI changes dev economics, with r/haskell apparently sensitive to AI talk right now. Mixed views: some defend the move for speed, others argue Haskell's long-term strengths outweigh short-term friction.















