HN user
Recklessly discarding OpenSSL errors is really bad and could lead to security vulnerabilities.
Calling ERR_clear_error before operations is widely recommended: https://github.com/openssl/openssl/discussions/23025
which matches the blog author's point.
How widespread is this OpenSSL error discarding practice? It might explain a lot of security vulnerabilities.
stdx is on crates.io: https://crates.io/crates/stdx
But it seems to be a placeholder crate of sorts and is not Kerkour's stdx.
It does re-export several other crates, but has not been maintained or updated in a long time.
Here is a nice setup that works well:
https://discourse.ubuntu.com/t/use-workshop-to-run-opencode-...
> Something that I had heard is that it is because Mormons use a different baptism, which is not Trinitarian. However, it seems that it is Trinitarian, although this trinity is different from that of Christians (even though they still say "the Father", "the Son", and "the Holy Spirit").
I had not heard that so I looked it up:
-----------
Catholic baptism:
“I baptize you in the name of the Father, and of the Son, and of the Holy Spirit.” The matter is the water poured over the head of the recipient. Traditionally, the one being baptized has water poured over them or is fully emerged in water three times.
Source: https://ascensionpress.com/blogs/articles/the-ultimate-guide...
(Some) Protestant baptism:
Each candidate is presented by name to the Celebrant, or to an assisting priest or deacon, who then immerses, or pours water upon, the candidate, saying
N., I baptize you in the Name of the Father, and of the Son, and of the Holy Spirit. Amen.
Source: https://www.bcponline.org/Baptism/holybaptism.html
(Some groups do it differently, but this seems to be common.)
Mormon baptism:
73 The person who is called of God and has authority from Jesus Christ to baptize, shall go down into the water with the person who has presented himself or herself for baptism, and shall say, calling him or her by name: Having been commissioned of Jesus Christ, I baptize you in the name of the Father, and of the Son, and of the Holy Ghost. Amen.
74 Then shall he immerse him or her in the water, and come forth again out of the water.
Source: https://www.churchofjesuschrist.org/study/scriptures/dc-test...
-----------
I am not an expert, but they all seem mostly the same to me?
Really?
What are some major Linux distributions that are only headless?
What is the market share of those Linux distributions compared to Linux distributions that have a GUI desktop?
Most Linux server distributions would be expected to be headless.
"General purpose" Linux distributions (not "server") typically would include a GUI desktop.
This looks like a really nice feature to see what goes into Rust binaries.
This post says that it is experimental, but does not say where it is used.
On my Ubuntu VM, it works with bat like the example shows, but does not work with the new Rust "ls":
ubuntu@resolute:~$ cargo audit bin /usr/bin/ls
Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
Loaded 1107 security advisories (from /home/ubuntu/.cargo/advisory-db)
Updating crates.io index
error: No dependency information found in /usr/bin/ls! Is it a Rust program built with cargo?
error: parse error: No dependency information found! Is this a Rust executable built with cargo?
ubuntu@resolute:~$ ls -lah /usr/bin/ls
lrwxrwxrwx 1 root root 29 Mar 30 16:50 /usr/bin/ls -> ../lib/cargo/bin/coreutils/ls
ubuntu@resolute:~$
If you like psy electronic music, there is 'The Mystic Didgeridoo':
Greg Kroah-Hartman has been maintaining Linux for decades.
If he says that Rust is helping Linux maintainers to do their work more effectively, that is great news for Linux. I am excited to see the work advance.
I was skeptical of Rust until I gave the language a try for Advent of Code one year. I found it interesting, but I was uncertain about how it would work in a real codebase.
Later at $JOB, I migrated a troublesome C codebase to Rust as an experiment and the results were eye-opening. We discovered errors in the C code we had not realized were present. We were able to structure the code in a way that was easier to understand. The rewritten code was slightly faster, but much easier to understand and maintain.
It really is a game changer.
It is also available as a snap:
Canonical (the company that makes Ubuntu Linux) has remote software engineer jobs:
https://canonical.com/careers/6707824
Their hiring process is a bit strange compared to other tech companies.
https://rosettacode.org/wiki/Hello_world/Newbie is similar.
rosettacode.org also has other tasks: https://rosettacode.org/wiki/Category:Programming_Tasks
> should not be rolled out in an LTS edition.
The Rust coreutils were first rolled out in the previous release which was not LTS:
https://canonical.com/blog/canonical-releases-ubuntu-25-10-q...
> Vegetarianism is such a bad label lol
Agreed. I was expecting to find AI-generated vegetarian recipes.
Actually, I wonder if they would be any good.
I fear that you are correct.
Perhaps if people become desperate enough something might happen, but keeping people divided is a strategy to prevent resistance.
It seems like we are sliding closer everyday to George Orwell's 1984. I wonder when Hate Week starts . . .
> Why? And also: What can be done to change this in the future?
Two corrupt political parties that are owned by monied interests thanks to Citizens United, decades without campaign finance reform, and rampant "gifts" and extortion.
Neither party represents the people or their needs. They take money and make money. Laws are written by monied special interests. Members of both parties have been doing insider trading for decades, but now it is on naked display, bold and unashamed, as if it to say, "what are you going to do about it?"
Drastic systemic changes are needed on the order of a Constitutional Convention, but it is doubtful that it will happen without tremendous public outcry.
if Rust can't do OOP (assumption)
Rust handles basic OOP, but not all of the characteristics seen in C++ or Java:
https://www.youtube.com/watch?v=iRImYairm1A
There is not a good way to "guard ships on the sides" against hundreds of Shahed drones or small seaborne drones.
They would overwhelm any defenses and only a few would need to get through to destroy a tanker.
If multiple tankers are together in a line the risk becomes greater: more targets for the drones to hit and any fires or explosions on one tanker might spread to other tankers.
George's personal home page (seems to be a mirror: https://www.bkinzel.de/misc/ghg/index.html) with the grill lighting video and the TWINKIES experiments (original site gone, but archived: https://web.archive.org/web/20060101093459/http://www.twinki...) were amazing web sites in the late 90s.
Maybe the Ubuntu transition from GNU coreutils to uutils coreutils is going well?
After working with C and C++ for many years and handling the problems associated with such software, Rust solves many of the difficult problems and makes nearly impossible problems manageable.
Rust is not perfect. It has flaws, moves quickly, and is harder to learn than other programming languages, but it is a large improvement and is advancing the state of the art.
Ubuntu recently added a more specific target for AMD64v3:
https://discourse.ubuntu.com/t/introducing-architecture-vari...
An official response from Ubuntu:
https://discourse.ubuntu.com/t/ubuntus-response-to-californi...
The email linked here are ideas from an Ubuntu contributor, not an official response.
What about all the weapons forbidden by the Geneva convention?
Some weapons are prohibited Geneva convention because they are designed to cause suffering or indiscriminately kill non-combatants:
"Weapons prohibited under the Geneva Convention and associated international humanitarian law (including the 1925 Protocol, CCW, and specific treaties) include chemical/biological agents (mustard gas, sarin), blinding lasers, expanding bullets, and non-detectable fragments. Also banned are anti-personnel landmines and cluster munitions.
Key prohibited and restricted weapons include:
Chemical and Biological Weapons: The 1925 Geneva Protocol and subsequent conventions (1972, 1993) banned the use, development, and stockpiling of asphyxiating, poisonous, or other gases, including nerve agents and biological weapons.
Blinding Laser Weapons: Specifically designed to cause permanent blindness (Protocol IV of the CCW).
Non-detectable Fragments: Weapons designed to injure by fragments not detectable in the human body by X-rays (Protocol I of the CCW).
Incendiary Weapons: Restrictions on using fire-based weapons (like flamethrowers) against civilian populations (Protocol III of the CCW).
Anti-personnel Landmines: Banned under the Ottawa Treaty (1997) due to risks to civilians.
Cluster Munitions: Prohibited due to their indiscriminate nature.
These treaties aim to protect civilians and combatants from unnecessary suffering and long-term danger."
Would "good hands" choose weapons that are designed to cause suffering or that kill indiscriminately?
No, they would not.
A weapon is a tool.
Whether they are good or evil depends on the hands that hold it.
In good hands, weapons provide defense, deterrence, and protection.
In bad hands, weapons hurt the innocent, instill fear, and oppress.
The hands that wield them make all the difference.
grep, sed, and awk are nice simple tools but were followed by perl which is a more comprehensive tool and a complete programming language.
perl advanced the state of the art for regular expressions such that most regular expression implementations are "perl compatible".
From HN user unpythonic:
"When perl came out we were living in horrific times. You had the choice of either Bourne, C or Korn shell. Automation was glued together in one of these with a series of grep, awk, sed, ls, test, commands glued together.
Anything more complicated was written in C and called from one of these things. Perl in one stroke collapsed the programming of C, text manipulation, the capabilities of all of the Unix utilities, and data structures into one system. For anything which wasn't subsumed into the monolith of Perl, you could easy access via backticks. It was very friendly in dealing with text streams, and that's what those call-outs in those back ticks spoke.
Yes, awk and sed were replaced by Perl, but more importantly, the unmaintainable nightmare that glued all of it together was wiped out." Source: https://news.ycombinator.com/item?id=36650120
From "The Art of Unix Programming":
"Perl is shell on steroids. It was specifically designed to replace awk(1), and expanded to replace shell as the ‘glue’ for mixed-language script programming. It was first released in 1987." Source: http://www.catb.org/esr/writings/taoup/html/ch14s04.html#per...
It is good to know grep, sed, and awk, but it would be remiss to not include perl too. It is equally ubiquitous, more capable, and still developed and maintained with version 5.42.0 released last year: https://www.cpan.org/src/README.html
"On the scripting side, Perl has also returned to prominence. Once the undisputed leader in scripting, Perl declined after years of internal fragmentation and competition from newer languages. Recently, however, it has staged a comeback, reclaiming a position in the TIOBE top 10 since January 2018." Source: https://www.tiobe.com/tiobe-index/
But don't take my word for it, give it a try and see what you think: https://www.perl.org/get.html
Ubuntu plus Landscape for management:
They have fired the honest people who reported numbers they did not like.
Anything that they publish should be considered untrustworthy. Anything they say should be considered unreliable.
It used to be "trust but verify", now it is "don't trust, seek a different source". It is sad, but reality now.
(2005)
Many US states also have a state guard that is under the sole control of the state government: https://en.wikipedia.org/wiki/State_defense_force
These forces are distinct from the state's National Guard and cannot be federalized.