Chief Unblocking Officer
Intel once the world's largest chipmaker for more than 30 years, has been dethroned from its position. Manufacturing delays, failure to enter the mobile chips market, and losing market share in the PC and data centre segment to competitors.
Boeing
Series B last December, I'm happy to announce we've raised a $102M Series C from existing and new investors.
Our vision of the Web is a global realtime medium for both creators and consumers, where all friction and latency are eliminated.
We'll use this investment to:
1. Hire and develop the best
Unlike other software development platforms, the Web never came with an SDK or Standard Development Kit.
Next.js builds on this formidable foundation to give developers and companies a meaningful starting point to build great pages, open sourcing the lessons learned from the giants of the Web.
2. Embrace conflict
deploy and scale frontend projects. But significant challenges remain to frictionless collaboration:
- Setting up and maintaining your developer environment
- Integrating it into Git for continuous integration
- Manually pushing and waiting to share progress with your team
Perhaps the most incredible aspect of diverse group of smart people is that different ideas will rise. Each Web browser is simultaneously the [consumption and creation mechanism](https://twitter.com/sulc o/status/1177559150563344384).
With Next.js Live, we want to build a Web that everyone can contribute to. Whether it's to pitch in an idea or an edit, by an experienced developer or a new designer, from a local editor or the browser itself.
3. Focus on the end-user
A particularly interesting challenge of building a platform and tooling company is that you have two users (whether it's acknowledged or not):
- The user of the tool
- The user of the output of the tool
No matter how many downloads Next.js gets, or how delightful and realtime the development experience, a universal truth remains: the customer is king.
Performance for the end-user has been baked in the design of everything we make. To name some examples:Perhaps the most incredible aspect
- Next.js was born out of the insight that React in its initial Single Page Application presentation was putting the rendering burden on the user's device that should have been on the server instead.
- Vercel Analytics prioritized giving you a Real Experience Score calculated by each device, rather than just listing traffic stats or TTFB latencies.
- Pre-rendering at build time or via Incremental Static Regeneration is all about taking the CPU cycles entirely out of the page serving equation, removing latency for the end user.
Our primary fitness function is your success for your customers. Not every visitor might understand fully how every page is built, but if the experience is delightful and fast, they ought to think it was powered by Vercel.