optimism VS Next.js

open source. we’re building base on the OP Stack — which means that if you want to contribute, you can! you can review the code and start contributing here. we’ll be open sourcing as much as possible, so more people can get involved.

OP Labs | Remote-first | Full-time |

https://optimism.io

Optimism is an Ethereum scaling solution that enables anyone to execute any vision on an open source protocol that will never be captured by private interests. We’re building this technology as a public good, in order to fundamentally change the relationship between companies and their users.

From code to ethos, we are Ethereum-aligned. By operating as a Public Benefit Corporation, we align private incentives with public good and create a positive-sum economic model that provides a sustainable future for the internet.

Today, the most pressing bottleneck to Ethereum and crypto’s growth is its performance and scalability. We are building the most elegant solution to this problem. We do this out in the open because we believe in open source and its ability to accelerate innovation.

To date, we have raised $178M. Both series A and B were led by Andreessen Horowitz and Paradigm.

We are actively hiring for the roles listed here: All open roles are listed here:

https://boards.greenhouse.io/oplabs

Join us in scaling Ethereum and empowering the creators of public goods! :)

Optimism's Bedrock contracts have pretty good examples - https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock

Perp-maker is an open-source market-making template for Perpetual Protocol v2, the most popular dApp on Optimism (a layer-2 scaling solution for Ethereum). Anyone can use or modify the template to facilitate trades on the protocol and earn fees.

Except that anyone with a minimal involvement with Ethereum already knows that the base layer is not meant to be used on day-to-day operations.

We already learned about the decentralization trillema. The strategy to scale Ethereum through will be through the adoption of "layer-2" systems, where users are expected to be doing their transactions and avoid these costly transactions altogether.

There are roll-ups already dealing with NFT marketplaces [0]. There are roll-ups that can execute any type of ethereum smart contract [1] [2]. There are payment channels that allow completely decentralized and gas-less transfers of ERC-20 tokens [3].

[0] https://loopring.io

[1] https://optimism.io/

[2] https://offchainlabs.com/

[3] https://raiden.network

Boba is a compute-focused L2. We believe that L2s can play a unique role in augmenting the base compute capabilities of the Ethereum ecosystem. You can learn more about Turing hybrid compute here. Boba is built on the Optimistic Rollup developed by Optimism. Aside from its main focus, augmenting compute, Boba differs from Optimism by:

The Across bridge is the fastest, cheapest, and most secure bridge between L1 and L2 (and soon between L2 and L2 hopefully). Across has integrated with the canonical bridges of Boba.network, Optimism.io, and Arbitrum.io, with more to come. Go take it for a spin and save yourself some ETH here: https://across.to/

Optimism - Already usable in alpha phase

Optimism Arbitrum Starknet dYdX Immutable X Hermez Aztec ZKSync Loopring

https://github.com/vercel/next.js/discussions/27666 One of them said 'renaming folder to uppercase' might cause trouble. git might not recognize case-sensetive changes by default.

Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.

Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

Next.js: For the website and the admin dashboard

Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.

next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.

Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.

For more information, check out this issue.