optimism VS Tailwind CSS

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

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository

Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

- Performance is a feature.

Another common interpretation of brutalism is aesthetic, reacting to overly complicated user interfaces by creating simpler, more direct ones. Tailwind CSS (https://tailwindcss.com), one of today's most popular CSS libraries, promotes this approach in its component examples. There's also a neat library I've seen recently called "Neobrutalism Components" for React that I like (https://neobrutalism-components.vercel.app), providing components with a similar look and feel to Gumroad. This might more accurately be called 'Neo-Brutalism,' as noted in the comments.

A more engineering-centric interpretation of Brutalism focuses on form, structure, and efficiency, drawing significantly from brutalist architecture principles. Apart from the user interface itself, most mobile, desktop, and web applications are extremely bloated and often perform worse than sites from 10 years ago did. While one HTML file might be "less brutalist" than the original HN site, it is substantially more brutalist than any HN mobile app in existence, and offers nearly identical functionality.

A broader interpretation of brutalism, which could be termed 'Meta-Brutalism,' is embodied in the overall experience on this site through UX flows. Yes, in the strictest sense, the original HN site is more Brutalist in many ways, but it only shows 30 articles at a time and does not function as a PWA. For this site, the experience of reading 10 stories is arguably less brutalist, but for quickly browsing through several pages and skimming articles (which is how I read HN) it is a lot faster, and in my opinion, more Brutalist.

My primary inspiration was addressing software and tool bloat in UIs rather than strictly adhering to every principle set forth by David Bryant Copeland. I don't find it convincing that this site "isn't brutalist" compared to really any other experience apart from the Main HN site, and I would argue the overall experience is more brutalist in its performance and scrolling behavior.

As a side note: I generally don't like Brutalist architecture that much although I believe it is unfairly maligned. I visited the Salk Institute once and enjoyed it though (https://www.archdaily.com/61288/ad-classics-salk-institute-l...).