#compiled — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #compiled, aggregated by home.social.
-
Unix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
-
Unix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
-
Unix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
-
Unix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
-
Unix "find" expressions compiled to bytecode
https://nullprogram.com/blog/2025/12/23/
#HackerNews #Unix #find #bytecode #compiled #programming #technology #efficiency
-
Minkah Fitzpatrick cracks top-10 list compiled by NFL insiders for ESPN
The Miami Dolphins finally have a player who was named among the top-ten at his position in ESPN’s…
#NFL #MiamiDolphins #Miami #Dolphins #by #compiled #cracks #espn #fitzpatrick #Football #for #front-page #insiders #list #miami-dolphins-news #miami-dolphins-power-rankings #miami-dolphins-roster #minkah #phinsider #the #top
https://www.rawchili.com/nfl/200949/ -
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
-
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
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
#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
-
#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
-
#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
-
#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
-
#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
-
Hey fellow #Developers 🤓
What is your #backend #programming #language type of choice?
-
Hey fellow #Developers 🤓
What is your #backend #programming #language type of choice?
-
Hey fellow #Developers 🤓
What is your #backend #programming #language type of choice?
-
Hey fellow #Developers 🤓
What is your #backend #programming #language type of choice?
-
Hey fellow #Developers 🤓
What is your #backend #programming #language type of choice?
-
That was one hell of a mission! Finally migrated from my old #RaspberryPi2 to a Shuttle as my #Yunohost #Server. It was far more difficult than I anticipated, what with the completely different architectures (#armf to x86_64).
This oversight by some of the contributed "High Quality" apps, seems to be one that has been overlooked.
Migrating should be quite a simple task:
1. create backup
2. copy backup to destination
3. restore backup
For apps that are arch agnostic, this isn't a #problem (like #WordPress). But for those apps that are installed with #compiled #binaries that run as system services, this is a potential weakness that might need to be addressed.
No-one wants to install an application on a small #SBC only to find out later that they cant migrate to a more powerful machine should the need arise.
This issue isn't addressed in the #Wiki, Bug Reports, Readmes, #FAQ or relevant documentation. Perhaps it might be something worth looking at? -
That was one hell of a mission! Finally migrated from my old #RaspberryPi2 to a Shuttle as my #Yunohost #Server. It was far more difficult than I anticipated, what with the completely different architectures (#armf to x86_64).
This oversight by some of the contributed "High Quality" apps, seems to be one that has been overlooked.
Migrating should be quite a simple task:
1. create backup
2. copy backup to destination
3. restore backup
For apps that are arch agnostic, this isn't a #problem (like #WordPress). But for those apps that are installed with #compiled #binaries that run as system services, this is a potential weakness that might need to be addressed.
No-one wants to install an application on a small #SBC only to find out later that they cant migrate to a more powerful machine should the need arise.
This issue isn't addressed in the #Wiki, Bug Reports, Readmes, #FAQ or relevant documentation. Perhaps it might be something worth looking at?