Instagram is testing the ability to share videos up to 90 minutes long and has launched on Apple TV, letting users watch Reels and other content on larger screens. Unlike YouTube, Instagram is not paying creators for these longer videos.
Meta is trying to turn Instagram into a destination for longer-form entertainment and a stronger competitor to YouTube, using its existing creator base and Apple TV distribution to increase viewing time.
Variety reports the Sharjah International Film Festival for Children and Youth signed an agreement with the UAE's recently established National Media Authority covering film screening procedures, training, and technical support.
Variety reports Instagram is testing video uploads up to 90 minutes, launching an Apple TV app for Reels and longer content, and is not paying creators for that content, positioning itself against YouTube.
Variety confirmed Walter Koenig, who played Chekov in the original “Star Trek” series and seven feature films, died Sunday in Los Angeles at age 90; his reps issued a statement mourning him.
Variety reports Harry Styles released a music video for “Coming Up Roses” from his fourth album, directed by Bradley & Pablo.
SBirat Datta posted on X that every web dev has a Safari DevTools horror story. That's a bold claim.
EHe's not wrong. Safari's dev tools feel like they were built in 2010 and never updated.
SSo he got tired of his own horror story and built a concept for what Safari DevTools should look like. It's a single-file, zero-dependency toolkit that runs right in the page.
EConsole, elements, network mocking — even MCP and Playwright support. That's actually clever.
SIn-page? So you debug your site by injecting more JavaScript into it? That sounds like exactly the kind of thing that breaks production.
EIt's a concept, Sloane. He's not telling Apple to ship it tomorrow. He's showing what's possible when Apple won't.
SBut tagging Apple in the post, with the eyes emoji? That's not going to make Tim Cook drop everything.
EIt's not about Tim Cook. It's about building a community alternative. Developers have been asking for better Safari tools for years, and Apple just ignores them.
SBecause most developers don't use Safari to debug. They open Chrome or Firefox and move on. The market has spoken.
EThat's exactly the problem! If everyone abandons Safari, Apple has zero incentive to improve it. Then Safari users get a worse web, and we all pay for it.
SSafari users are not developers. They're people watching Netflix and reading articles. They don't care if the console is clunky.
EBut developers build the sites those people use. If we can't test properly in Safari, we ship bugs that only Safari users see. That's a real cost.
SThen use a real browser for development and test Safari at the end. That's been standard practice for a decade.
EAnd that's why Safari has become the new Internet Explorer! We treat it as an afterthought, so it stays behind.
SOh, come on. Internet Explorer had no competition. Safari has Chrome, Firefox, Edge, Brave, Arc. It's not the same.
ETell that to the developer who just lost three hours to a Safari-only flexbox bug. It feels exactly the same.
SMaybe the developer should have opened the in-page toolkit Birat built.
EThat's my point! This concept might actually be useful, even if Apple never adopts it.
SSo now you're saying a third-party dev tool could replace Safari's own DevTools?
EWhy not? Chrome's DevTools started as a separate project. Developers built extensions and tools until Google folded them in. Same playbook.
SBut it's not a product. It's a concept page with a nice write-up. There's no install, no updates, no browser integration.
EEvery tool starts as a concept. The fact that it's single-file and zero-dependency means someone could fork it today and build it out.
SAnd who's going to maintain it? A random developer on X? That's not a reliable foundation for professional work.
EMaybe not, but it plants a flag. It says the current state is unacceptable, and here's a direction. That matters.
SI'll give him credit for shipping something. But calling it a "concept for what it should look like" is generous. It's a mockup with some clever engineering.
EAnd mockups have changed products before. Remember when the iPhone was just a concept? Or the first Tesla Roadster?
SNow you're comparing a Safari DevTools mockup to the iPhone?
EThe principle is the same! Small ideas from frustrated people become big products.
SThe principle is the same, the execution is not. This is a single HTML file, not a multi-billion-dollar research project.
EYou know what? I'd rather have a hundred developers shipping single-file concepts than one more Apple executive saying "we hear you" and doing nothing.
SFair enough. But the real test is whether anyone actually uses it. Not whether it gets likes on X.
EAnd that's why he asked "What would you add?" He's looking for feedback, not applause.
SGood. Because the answer from most web devs is probably "make Safari's DevTools not terrible." But that's Apple's job, and they're not doing it.
ESo we agree Apple's not doing their job?
SI didn't say I agree. I said that's what the feedback would be. I still think developers have alternatives.
EAlternatives that don't work when you're on a locked-down iPhone or iPad and need to debug WebKit. Safari is the only engine allowed on iOS.
SThat's the real issue — Apple's walled garden. Not the DevTools.
EIt's the same issue! Apple controls the browser engine on iOS, so developers can't just switch. They're stuck with Safari's rendering and its tools.
SOkay, that's a fair point. If you're building for iOS, you have to deal with WebKit. But that doesn't make a third-party in-page console the solution.
EIt could be a stopgap until Apple gets its act together. And if enough people adopt it, Apple might pay attention.
STagging Apple with an eyes emoji is not a strategy.
ENo, but it's a start.
SWe'll see if Apple replies. Don't hold your breath.