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.

https://discourse.ubuntu.com/t/introducing-architecture-vari...

https://discourse.ubuntu.com/t/ubuntus-response-to-californi...

The email linked here are ideas from an Ubuntu contributor, not an official response.

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.

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.

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

https://ubuntu.com/landscape

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.

These forces are distinct from the state's National Guard and cannot be federalized.

You answered your own question.

I do not trust an agent to give it unsupervised access to my systems.

If I had a completely local agent that was fully sandboxed and I would be willing to put data in the sandbox, give it a task, and come back later to see what it did.

I would not trust agents to run unsupervised with similar restrictions.

What hardware were you using?

What kind of troubleshooting did you perform?

>> Six weeks in, things changed. The Linux installations started to degrade — subtle at first, then undeniable. Random slowdowns. Browser links that wouldn't register for 10 or 15 seconds. The kind of frustration that makes you stare at the screen and wonder what's happening under the hood. It was consistent across distributions, which suggests this wasn't just a bad package here or there. Something fundamental was happening.

Without more details it would be difficult to determine what problems you were having.

I have never had problems like you describe with Linux. I would be interested to know more details.

The name "Spark" already refers to:

A popular data analytics framework of the Apache Foundation: https://spark.apache.org/

A subset of the Ada programming language used for formal verification: https://learn.adacore.com/courses/intro-to-spark/chapters/01...

An Nvidia AI development system: https://www.nvidia.com/en-us/products/workstations/dgx-spark...

This particular quote comes humanity's struggles through the Butlerian Jihad: https://dune.fandom.com/wiki/Butlerian_Jihad

Thank you for creating DEP-18 and pushing it forward.

As an aspiring Debian developer, learning the Debian packaging tools and procedures has been a challenge.

There are many different packaging tools and they work quite differently from other command line tools I use for software development on Linux.

DEP-18 will help to bring Debian's procedures closer to what the industry follows and lower the barriers for new contributors. I hope it gets adopted.

They kept the header because they legally agreed to keep it, but the rest is conspiracy propaganda.

Comments URL: https://news.ycombinator.com/item?id=45992756

Points: 18

# Comments: 7

https://www.youtube.com/watch?app=desktop&v=Ag1AKIl_2GM&t=57...