The browser company has repeatedly said that it does not get rid of the ARC browser when it goes to the novel dia-percentric browser. But the company also does not intend to develop novel functions. AND New blog post From CEO, Josh Miller explains why and what will happen next.
The ARC browser was a large reflection on how browsers should be, and it has dedicated users, including yours. But many reasons for stopping the development of ARC, which Miller gives on the blog – for example, that it is too complicated to go to the mainstream, that sometimes it was tardy and unstable (truth!), Or that the browser company recently wants experience in AI recently – he also gave in in October.
Why just not throw Dia in ARC? One great thing Miller recalls is security. ARC had at least one large security problem: a security researcher discovered last year to be susceptible to the threat that the browser company quickly arranged, but which allows the attacker to insert any code in the user browser session, knowing their user identifier. According to Miller, the browser company has developed their security engineering team from one person to five. This focus is particularly significant, he writes, because AI agents – AI systems that perform autonomous tasks – become more common.
As for what all this means for ARC and its users, Miller still insists that the browser does not disappear. ARC will continue to receive security and error corrections and will be improved because the chromium code on which it is based on the update. But he also says that the browser company does not intend to open or sell ARC, because in addition to chromium it is based on a custom infrastructure, which also the basis of DIA. He says that the company would like to open a browser someday, but only “does not expose our team or shareholders anymore.”
The browser company did not answer immediately when The Verge Asked if the same larger security team is also working on increasing the safety of the ARC itself. We will update when we learn more.