lepichudoesdev@ohiodeck in lepichudoesdev in 0.2s !!!
$> # This is native Rust
lepichudoesdev@ohiodeck in lepichudoesdev in 0.0s !!!
$> ~/Downloads/bombardier -c 10 -n 1000 http://localhost:3000/health
Bombarding http://localhost:3000/health with 1000 request(s) using 10 connection(s)
1000 / 1000 [===============================================================================] 100.00% 4947/s 0s
Done!
Statistics Avg Stdev MaxI have been thinking a lot about how language mechanisms intrinsically start off as language tools at some level, for this instance I would like to discuss Rust's Borrow Checker in-tandem with Clippy; the Linter for Rust projects. A Linter, traditionally, is defined as a collection of "lints" or rules (examples: unused variables, missing method implementations, missing await in asynchronous blocks, etc.) which check for specific patterns across a given set of code, it may or may not take program state and type-checking into account, the end goal of a linter is to catch supposedly bad code ahead of time, much like something like a type-system trying to catch for type-inconsistencies or other type-safety failures. Clippy has more than 800 linting rules out of the box.
The Borrow Checker is an integral part of the Rust language which ensures memory safety by the system of borrowing, only one variable can truly own something at a given time and the others must use said something using a reference. It (th
lepichudoesdev@ohiodeck in chai_deps_test via 🦀 on master $> ./Invoke-Benchmark.ps1; ./Invoke-BenchmarkWarm.ps1 🚀 Starting benchmark suite for 32 packages... ============================================ 📦 Package 1/32 🔍 Benchmark: com.google.code.gson:gson:2.10.1 =====================================
lepichudoesdev@ohiodeck in chai_deps_test via 🦀 on master in 0.0s !!! $> ./Invoke-Benchmark.ps1 🚀 Starting benchmark suite for 12 packages... ============================================ 📦 Package 1/12 🔍 Benchmark: com.google.code.gson:gson:2.10.1 =====================================
lepichudoesdev@ohiodeck in chai_deps_test via 🦀 on master in 19.8s !!! $> ./Invoke-Benchmark.ps1 🚀 Starting benchmark suite for 12 packages... ============================================ 📦 Package 1/12 🔍 Benchmark: com.google.code.gson:gson:2.10.1 ===================================== 🧹 Clearing all caches...
| lepichudoesdev@ohiodeck in chai_deps_test via 🦀 on master in 0.0s !!! | |
| $> ./Invoke-Benchmark.ps1 | |
| 🚀 Starting benchmark suite for 12 packages... | |
| ============================================ | |
| 📦 Package 1/12 | |
| 🔍 Benchmark: com.google.code.gson:gson:2.10.1 | |
| ===================================== |
| lepichudoesdev@ohiodeck in Dump in 14.5s !!! | |
| $> ./Test-Maven.ps1 | |
| Processing com.google.code.gson:gson:2.10.1... | |
| Processing org.apache.commons:commons-lang3:3.14.0... | |
| Processing com.squareup.okhttp3:okhttp:4.12.0... | |
| Processing io.reactivex.rxjava3:rxjava:3.1.8... | |
| Processing com.google.guava:guava:33.0.0-jre... | |
| Processing org.hibernate:hibernate-core:6.4.1.Final... | |
| Processing io.quarkus:quarkus-core:3.6.4... | |
| Processing io.micronaut:micronaut-core:4.2.3... |
| Set-PSReadLineOption -EditMode Windows | |
| Set-PSReadLineOption -PredictionViewStyle ListView | |
| Set-PSReadLineOption -Colors @{ "Parameter" = $PSStyle.Foreground.FromRgb(127, 127, 127) } | |
| Set-PSReadlineKeyHandler -Key ctrl+d -Function DeleteCharOrExit | |
| Set-PSReadLineKeyHandler -Key ctrl+e -ScriptBlock { | |
| [System.Console]::Clear() | |
| $global:COLDBOOT = $true | |
| [Microsoft.PowerShell.PSConsoleReadLine]::BeginningOfLine() | |
| } |
| Write-Host "Hello honey, we are installing things now ^_^" | |
| winget install -e --id Python.Python.3.13 | |
| winget install -e --id Microsoft.VisualStudioCode | |
| winget install -e --id FreeCAD.FreeCAD |
RFC 01 - Vanilla HTML Element Extensions for Utahraptor.
Through out the history of Metaframeworks in the Web Ecosystem, every one of them implements common abstractions to reach common goals, some of these include appending data to the <head> element, another is to have seamless routing between pages, and more.
- Only rely on extending existing HTML Elements
- Cover all major usecases, but also try to cover niche usecases
- Expose extensions as opt-in attributes