Solidity, Vyper or Rust: Choosing a Smart Contract Language by Blockchain Target

·1 views

Selecting a smart contract programming language is an early and consequential decision in blockchain development, shaping which networks and tools a project can use. Solidity and Vyper are built primarily for Ethereum Virtual Machine environments, while Rust is used in several ecosystems such as Solana, with frameworks that differ between networks. The article stresses that the target blockchain should guide the choice, since Rust does not make code portable across all Rust-supporting chains and EVM contracts often need changes to run on other networks. Solidity is highlighted for its wide adoption, familiar syntax and mature tooling like Hardhat and Foundry, while Vyper offers a deliberately restricted, Python-inspired design aimed at clarity and auditability. Developers are advised to weigh existing expertise, ecosystem support and long-term maintenance alongside language features, since no language eliminates security risks on its own.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Respan Launches Open-Source Rust AI Gateway Built on a Plugin Architecture

Respan, a Y Combinator W24 startup, has launched an open-source AI gateway written in Rust that uses a small core with everything else built as plugins. The design covers LLM providers, protocols such as MCP and voice, modalities like images and video, and features including fallbacks, PII redaction, and smart routing. The company says it grew out of a wrapper around LiteLLM that became hard to maintain, and that a failed LiteLLM upgrade in January led it to redesign the gateway. Developers can add their own providers and features as plugins without changing the core, and the gateway translates between API formats so applications can use models from other vendors. The project is inspired by Nginx's minimal-core approach.

0 comments Read more at Hacker News

ProgrammingHacker News ·

Facebook reportedly plans fee for posting more than two links a month

A post on Mastodon by user AshleyGullen claims that Facebook is now charging users who share more than two links per month. The claim was shared on Hacker News, where it gained modest attention with 11 points and 2 comments. The source material is a social media post and a discussion thread rather than an official announcement from Meta. No confirmation from Facebook or its parent company was included in the available information. Details such as how the fee works and when it takes effect remain unverified.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer's self-scan finds own repo still on retiring macos-14 runner image

On October 19, GitHub began rolling the ubuntu-latest label to Ubuntu 26.04 and started a first brownout of the macos-14 image ahead of its November 2 retirement. The author ran their RunnerDriftAudit scanner on five repositories and found eleven high-severity floating or retired runner labels, including one iOS project still pinned to macos-14. Switching that workflow to macos-15 fixed it, with CI passing on the new image the same morning. The author deliberately left other floating labels in place where they serve as intentional tests, and noted that unpinned actions/checkout@v4 references remain unfixed. The scanner is a free, open-source, single-file Python tool.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Deleted Open Files Keep Disk Space Until the Writing Process Exits

A cleanup that removes camera clips can leave disk usage unchanged if a process still holds one of the files open. On Linux, removing a name does not release the space while a file descriptor remains open. In tests on ext4 using a stand-in recorder, a deleted 200 MiB file kept its space allocated until the writing process exited. The author found the process with lsof and /proc, and noted that truncating the file through /proc freed space but left the writer with a sparse file. The behavior matches the unlink(2) documentation, which keeps the file in existence until the last descriptor closes.

0 comments Read more at DEV Community