Hacker NewsUnix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
Roto: A Compiled Scripting Language for Rust
https://blog.nlnetlabs.nl/introducing-roto-a-compiled-scripting-language-for-rust/
#HackerNews #Roto #Rust #Scripting #Language #Compiled #Programming
Introducing Roto: A Compiled Scripting Language for Rust
By Terts Diepraam We are working on an embedded scripting language for Rust. This language, called Roto, aims to be a simple yet fast and reliable scripting language for Rust applications. The need for Roto comes from Rotonda, our BGP engine written in Rust. Mature BGP applications usually feature some
Things Zig Comptime Won't Do
https://matklad.github.io/2025/04/19/things-zig-comptime-wont-do.html
#HackerNews #Zig #Comptime #Compiled #Languages #Programming #Blog #Post
C.There are a lot of #tools and #libraries - in #Python and other languages - that are basically #wrappers around #compiled libraries written in C, C++, or other compiled languages. In general, installing the Python package from a repository declares the binary library package as a #dependency.
A name collision between the Python package and the underlying C library would be problematic. You could argue that a Python library that exposes the functionality of `libfrobnicate`, which is part of the `frobnicate` package, shouldn't itself be called `frobnicate` but something totally different - but people go searching for "Python for Frobnicate" so it's a natural enough name. And therefore the repository maintainers have to make it `python-frobnicate` etc.
In general, no, but in data science your chances of problems are a little higher. If you're relying on any binary wheels in your work, you may find it more difficult because many projects don't produce wheels for non-dominant architectures on any given OS. It was really common on MacOS when the Mx chips were newer, to find only x86 binary wheels.
So you may have to build wheels for compiled extensions, which can be fiddly.
Despite what the #systemd #devs might think, "42% less #Unix philosophy" is an anti-selling-point.
"Replace #sudo with #run0, let systemd do it" - sure. Throw away a well-audited, widely-used codebase which has worked well for decades, and instead turn it into a request to a #PID 1 process that is a huge modular-but-#monolithic codebase full of constant churn which has barely been #compiled, much less #understood.
Dollars to doughnuts there are more root holes lurking in systemd than in sudo.
Social User π€ΏWhat is the prevailing thought about adding a #compiled #docker #image to a #git #repository?
I understand it takes a lot of space, as does a backup though. Should I create a new repository just for the image?
Something like github/socialuser/myGreatProject and then github/socialuser/myGreatProject-binaries
Thoughts? Discussions?
#Compiled vs. #interpreted doesn't explain memory usage. For example, there are systems implemented in high-level languages (#Lisp and #Smalltalk come to mind) from the hardware right up to the UI that ran just fine on hardware that is today trivially tiny. It's more system design and what is being #optimized for, I think. When main memory was a few thousand iron doughnuts or the surface of a spinning drum, you optimized for every word of memory.
1/2
Furycd001
Chris CemperHey fellow #Developers π€
What is your #backend #programming #language type of choice?
Script (PHP, JS/Node, Ruby, Python, Bash, ASP)
Compiled (C, C++, Rust, Golang,...)
Poll ended at .