Documentation

Comparison

Compare Pure to similar solutions.

Comparison between Similar Platforms

Overview

Below are some differences/advantages compared to traditional programming or scripting platforms.

The focus is mostly on automation, tooling and daily workloads.

Worthnoting, for GUI dev or mockup, HTML/CSS/JS is great, and works especially well with Gen AI.

Notable Things

  • Pure (1/2) has REPL, though primitive (no multi-line support), it is lacking in dotnet File-Based App.
  • Generally, Pure works great with Gen AI, and minimal adjustments are needed.

Table Comparison

Platform Type Installation Size Stability Features Limitations Package Management/Functionalities Suited For Summary
Python Programming language Too many versions. Fairly stable. Can find pretty much everything in a library. Too many versions; Bulky environment. Package management is troublesome; messy distributable/end-script environments. Agile software; Web backend; Simulation prototype. CLI-oriented or web-based; Ecosystem leass leaned towards desktop GUI app (PyGame and PyQt exists). Lacks advanced language constructs; ubiquitous support. Super easy to get things done; Works well with GenAI.
Perl Programming language Super lightweight and fast. (PENDING) (PENDING) (PENDING) (PENDING) Desgined exactly to get things done (syntax wise speaking), though its ecosystem might be lacking behind Python. From simplicity perspective, might be outdated.
PowerShell Shell scripting language Super easy to install and use. Fairly stable. Flow control; Consume .Net functions. Archaic syntax. Batteries included, and generally a bad idea to import additional unofficial functionalities. Shell automation. Good for process automation; syntax not suited for efficient OOP programming.
Easy Shell Shell scripting language Super lightweight and fast. Work-in-progress; Internal tool. Famililarity to command line use; Consume C# functions. Lack in sophisication and full shell functionalities. N/A in current version; File-level support planned Build automation; Quick REPL evaluation with C# functions. Suitable for build scripts.
C# (Project) Programming language Proper development with an IDE (Visual Studio or IntelliJ) takes forever to install. Very stable as long as one avoids GUI-heavy setups. Many button clicks (in IDE) or commands or .csproj modifications required to install packages. Self-contained dependency environment; fast and lightweight. Non-DSL general purpose apps. Best for strongly typed and highly articulated solutions.
C# 14 (File-Based App) Scripting language Dotnet SDK. Highly stable. NuGet and .csproj reference. Full C#; r: directive; Single-file execution Cannot have multiple script files; Functions and classes must be declared at bottom of file (Mostly what Pure cannot do) Not sure what it's suited for besides more stable than Pure.
Pure (Original) Scripting language Requires .NET 8 (ASP.NET) Runtime; distributable is around 100MB C# .NET 8-based, likely never to change, very stable (depends on underlying C#); very few new language constructs. Easily migratable to proper C#. Single-file freestyle C# scripting. Tracing and multi-file is buggy; Cross-platform not tested. Zero-hassle package management and functionality import; single-file throughout. Short (few hundred to few thousand) single-file script. Provides the most efficient short-snippet authoring capabilities.
Pure 2 Scripting language 300MB (Pending) POS-compliant. (Pending) Preferable if you want easier version control, a text-based scripting experience, and a close-to-C# feel.
Divooka Programming language 500MB (Pending) Battery-packed for everyday use. (Pending) All you need for daily scripting.

Text Comparison

Below is a structured reorganization of the table into readable Markdown sections. Each platform is presented consistently, with clearly labeled fields and preserved intent/content.

Python

Type: Programming language Installation Size: Large; many versions and environments Stability: Fairly stable

Strengths

  • Extremely rich ecosystem; libraries for almost everything
  • Excellent for rapid development and prototyping
  • Strong GenAI integration and tooling

Limitations

  • Version fragmentation
  • Bulky runtime and environments
  • Desktop GUI ecosystem weaker compared to web/CLI

Package Management / Distribution

  • Troublesome and messy
  • Virtual environments and distribution often fragile

Best Suited For

  • Agile software development
  • Web backends
  • Simulation and prototyping
  • CLI-oriented or web-based tools

Summary

  • Ubiquitous and easy to get things done
  • Lacks advanced language constructs
  • High productivity at the cost of long-term cleanliness

Perl

Type: Programming language Installation Size: Super lightweight and fast Stability: Pending

Strengths

  • Syntax designed explicitly to get things done
  • Extremely concise and expressive

Limitations

  • Ecosystem lagging behind Python
  • Perceived as outdated in modern contexts

Package Management / Distribution

  • Pending

Best Suited For

  • Text processing and quick scripting

Summary

  • Very efficient from a syntax perspective
  • Simplicity-first philosophy, but aging ecosystem

PowerShell

Type: Shell scripting language Installation Size: Very easy to install and use Stability: Fairly stable

Strengths

  • Built-in flow control
  • Deep integration with .NET
  • Strong automation capabilities

Limitations

  • Archaic and verbose syntax
  • Poor fit for structured OOP

Package Management / Distribution

  • Batteries included
  • Importing unofficial functionality generally discouraged

Best Suited For

  • Shell and process automation

Summary

  • Excellent for automation
  • Not suitable for large or well-structured programs

Easy Shell

Type: Shell scripting language Installation Size: Super lightweight and fast Stability: Work-in-progress; internal tool

Strengths

  • Familiar command-line syntax
  • Ability to consume C# functions
  • Fast REPL-style evaluation

Limitations

  • Limited sophistication
  • Incomplete shell feature set

Package Management / Distribution

  • Not available in current version
  • File-level support planned

Best Suited For

  • Build automation
  • Quick scripting with C# interop

Summary

  • Pragmatic tool for build scripts and quick evaluations

C# (Project-Based)

Type: Programming language Installation Size: Heavy; IDE setup (Visual Studio / IntelliJ) is time-consuming Stability: Very stable if GUI-heavy stacks are avoided

Strengths

  • Strong typing and rich language constructs
  • Excellent tooling for large systems

Limitations

  • High setup friction
  • Many IDE actions or .csproj edits required

Package Management / Distribution

  • Self-contained dependency model
  • Fast and lightweight runtime once built
  • Package installation requires explicit configuration

Best Suited For

  • Non-DSL, general-purpose applications
  • Large, structured systems

Summary

  • Ideal for highly articulated, strongly typed solutions
  • High overhead for small tasks

C# 14 (File-Based App)

Type: Scripting language Installation Size: .NET SDK required Stability: Highly stable

Strengths

  • Full C# language support
  • r: directive and NuGet integration
  • Single-file execution model

Limitations

  • No multi-file scripts
  • Functions and classes must be declared at the bottom

Package Management / Distribution

  • NuGet via .csproj reference

Best Suited For

  • Cases where Pure is insufficient
  • More stable alternative to lightweight scripting

Summary

  • More rigid than Pure
  • Stability-first, flexibility-second

Pure (Original)

Type: Scripting language Installation Size: ~100 MB distributable; requires .NET 8 (ASP.NET) Runtime Stability: Very high (C# .NET 8–based; minimal language changes)

Strengths

  • Single-file, freestyle C# scripting
  • Easily migratable to proper C# projects
  • Extremely efficient for short scripts

Limitations

  • Tracing and multi-file support are buggy
  • Cross-platform behavior not fully tested

Package Management / Distribution

  • Zero-hassle package management
  • Single-file throughout

Best Suited For

  • Short scripts (hundreds to a few thousand lines)
  • Rapid authoring with minimal friction

Summary

  • Maximizes short-snippet authoring efficiency
  • Minimal abstraction, maximal speed of thought

Pure 2

Type: Scripting language Installation Size: ~300 MB Stability: Pending

Strengths

  • POS-compliant
  • Improved version control friendliness
  • Text-based scripting experience close to C#

Limitations

  • Pending specification and evaluation

Package Management / Distribution

  • Not finalized

Best Suited For

  • Users wanting C#-like scripting with better VCS ergonomics

Summary

  • Evolution of Pure toward maintainability and tooling

Divooka

Type: Programming language Installation Size: ~500 MB Stability: Pending

Strengths

  • Battery-packed for everyday use
  • Broad built-in functionality

Limitations

  • Pending details

Package Management / Distribution

  • Extensive built-in functionality

Best Suited For

  • Daily scripting and general-purpose tasks

Summary

  • All-in-one solution for everyday scripting needs