Urgent.News

What's breaking now, across thousands of outlets.

Tech

plain 0.5.0 against forge 1.9.0 on PRBMath, Solady and Morpho Blue: what ran and how long it took

I ran plain 0.5.0 and Foundry's forge 1.9.0 on three Solidity projects I hadn't tried before, on 2026-11-17: PRBMath, Solady and Morpho Blue. PRBMath passes all 408 of its tests under plain with the same compile time as forge, and an unchanged rerun takes 0.2 seconds where forge needs 3.2. Solady runs once foundry.toml gets one line changed, and then reruns in 0.29 seconds where forge needs 47.…

On November 17, 2026, a report was made comparing the performance of plain 0.5.0 and Foundry's forge 1.9.0 on three Solidity projects: PRBMath, Solady, and Morpho Blue. The experiments were conducted on a 12-core machine with two CPUs running each tool. Both plain and forge used the same Solc versions before the timed runs.

In the case of PRBMath, a fixed-point math library with 408 tests, both tools compiled the same number of files and completed the suites in similar times. The cold run, where no changes were made, took 43.3 seconds for forge and 40.8 seconds for plain. However, when rerun, plain completed in 0.2 seconds, while forge took 3.2 seconds, indicating plain's efficiency in reusing results.

Solady, a library of gas-optimized contracts, had 208 files compiled with forge, which took 151.3 seconds for the cold run and 97.6 seconds for the rerun. For plain, the configuration line in foundry.toml was changed, causing the compilation to fail after 95.5 seconds. After adjusting the evm_version, plain completed the cold run in 0.29 seconds, while forge took 47.2 seconds for the rerun.

Morpho Blue, a lending protocol compiled with via_ir and an optimizer_runs setting, faced a limitation with plain, which refused to compile due to the compilation_restrictions. The error message explicitly stated that plain does not support the evm_version yet. Therefore, plain did not proceed with the compilation or testing, unlike forge, which took 14 minutes and 47 seconds to complete the cold run.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How to handle refund requests in a subscription app

This guide was originally published on the Hailbell blog . Short answer: iOS: you can't refund App Store purchases. Apple decides.

  • Refund handling depends on store (App Store, Google Play, or own website)
  • Verify store, plan status, and charge details before responding
  • Prepare policy statement for consistent refund communication

BugMeNot Calls It Quits

BugMeNot, the password-sharing service launched in 2003 to help users bypass website registration requirements, has shut down without explanation after more than two decades.

Chaos engineering with Dynatrace: measure before you inject a failure

Before scheduling a chaos engineering with Dynatrace experiment in production, one question matters: « if I slow down or cut this component, how will I know within ten minutes that the experiment…

  • Dynatrace measures before injecting failures in production
  • Chaos experiment treated as hypothesis test with clear contract
  • SLO and SRG guardian automate verdict for experiment decision

Designing a Mobile Sales CRM Dashboard for Fast Decisions

Enterprise sales representatives use their phones between meetings, while full desktop CRMs hold more data than a small screen can comfortably display.

  • Mobile CRM dashboard answers quota progress, imminent closing deals, and overdue tasks
  • Streamlined design focuses on clarity, high-level metrics over detailed records
  • Visual hierarchy, color, spacing, typography, and accessibility ensure usability

More from Tuesday 17 November →