Earlier this month Opera announced that it would be moving from Presto to WebKit as the engine at the core of the browser. The move to Opera WebKit will allow the development team to concentrate more on user experience in the future, said Opera.
But the move to Opera WebKit has also brought with it a downsizing of the development team at Opera, who has now dismantled a core technology developer team.
Opera CEO, Lars Boilesen, confirmed the cuts are linked to its switch to Opera WebKit, explaining to the Tech Crunch website:
“We will still have a Core team but it will be less people going forward,”-“Today we are living in a world where there are very few platforms for mobile, very few platforms for Windows, very few platforms on tablets… We think WebKit’s good enough, to switch, and by doing that we free up a lot of resources,”- “the size of the developer team at Opera now numbers “around 600″. Of the around 90 jobs that have gone in the Core team, around half were developer roles — with many other less technical roles such as checking website compatibility something Opera has been freed up from by moving to WebKit.”
Impact on the Browser Market
The decision to switch to WebKit is significant in the context of the broader browser market. WebKit, originally developed by Apple and used in its Safari browser, has become a widely adopted rendering engine. Google Chrome also uses a fork of WebKit called Blink. By adopting WebKit, Opera aligns itself with these major players, potentially increasing compatibility and performance across different platforms. This move could make it easier for web developers to ensure their sites work well on Opera, as they would no longer need to account for the unique quirks of the Presto engine.
Moreover, the switch to WebKit could lead to faster updates and improvements in the Opera browser. WebKit’s open-source nature allows for a collaborative development environment where innovations and bug fixes can be shared among different browsers using the engine. This could result in a more robust and feature-rich browsing experience for Opera users.
Challenges and Opportunities
While the transition to WebKit offers numerous advantages, it also presents challenges. One of the most immediate impacts is the downsizing of Opera’s development team. The reduction of around 90 jobs, including both developer and non-developer roles, indicates a significant restructuring within the company. This downsizing could affect the speed and efficiency of future developments, at least in the short term.
However, the move also frees up resources that can be redirected towards enhancing user experience and adding new features. With fewer resources tied up in maintaining a proprietary engine, Opera can focus on differentiating itself through unique features and optimizations. For example, Opera has historically been known for its innovative features like built-in ad blockers, VPN services, and data-saving modes. By leveraging WebKit, Opera can concentrate on refining these features and introducing new ones that set it apart from competitors.
Additionally, the switch to WebKit could open up new opportunities for collaboration and partnerships. By aligning with a widely-used engine, Opera may find it easier to form alliances with other tech companies and developers. This could lead to integrations and features that enhance the overall user experience.
In conclusion, Opera’s decision to switch from Presto to WebKit marks a significant shift in its development strategy. While the move has led to a downsizing of the development team, it also opens up new opportunities for improving user experience and staying competitive in the browser market. By adopting WebKit, Opera aligns itself with major players like Apple and Google, potentially leading to a more robust and feature-rich browsing experience for its users.
Source: Tech Crunch : digi.no
Latest Geeky Gadgets Deals
Disclosure: Some of our articles include affiliate links. If you buy something through one of these links, Geeky Gadgets may earn an affiliate commission. Learn about our Disclosure Policy.
