lordmagian's movie Reviews on Newgrounds

[The Fire Watch (Meatball in Space EP 8)]

Hope to see more!

Snakefood responds:

There will be plenty more!

[Aquatics - TPP]

This is pretty surreal. I enjoy.

[Mean Girls Animated Collab | Meet the Plastics]

I am in tears bruh, this is parody on top of parody

[IMAGINARIUM CHRONICLES: Episode 1]

When you're a starving artist and someone commissions you to draw purry forn so you start bleeding from every orifice.

[Everything Must Go]

A waking fever dream.

[Chillo Night]

Where is the rest of the video? This is a gif with music on top.

Dieswyx responds:

What's the matter, mate?

[NG Summer Fest 2023 Opening Animation]

We put together something special for this very special website, I wouldn't change it for the world.

[[APRIL FOOLS]-SATISFACTION-Newgrounds anime shorts-[VHS]-{sub}]

Blue was just getting some snacks he stashed.

[Lucky Shart]

As an Arch Linux user I would like to point out that what you refer to as Linux is actually GNU/Linux, furthermore I'd like to interject for a moment to further explain that I use Arch Linux which is a Linux distribution created for computers with x86-64 processors. Arch Linux adheres to the KISS principle ("Keep It Simple, Stupid"). The project attempts to have minimal distribution-specific changes, and therefore minimal breakage with updates, and be pragmatic over ideological design choices and focus on customizability rather than user-friendliness. Arch Linux uses a rolling release model, meaning there are no "major releases" of completely new versions of the system; a regular system update is all that is needed to obtain the latest Arch software; the installation images released every month by the Arch team are simply up-to-date snapshots of the main system components. Arch Linux has comprehensive documentation, which consists of a community wiki known as the ArchWiki. Until Pacman version 4.0.0, Arch Linux's package manager lacked support for signed packages. Packages and metadata were not verified for authenticity by Pacman during the download-install process. Without package authentication checking, tampered-with or malicious repository mirrors could compromise the integrity of a system. Pacman 4 allowed verification of the package database and packages, but it was disabled by default. In November 2011, package signing became mandatory for new package builds, and as of the 21st of March 2012, every official package is signed. In June 2012, package signing verification became official and is now enabled by default in the installation process. Arch is largely based on binary packages. Packages target x86-64 microprocessors to assist performance on modern hardware. A ports/ebuild-like system is also provided for automated source compilation, known as the Arch Build System. Arch Linux focuses on simplicity of design, meaning that the main focus involves creating an environment that is straightforward and relatively easy for the user to understand directly, rather than providing polished point-and-click style management tools — the package manager, for example, does not have an official graphical front-end. This is largely achieved by encouraging the use of succinctly commented, clean configuration files that are arranged for quick access and editing. This has earned it a reputation as a distribution for "advanced users" who are willing to use the command line. The Arch Linux website supplies ISO images that can be run from CD or USB. After a user partitions and formats their drive, a simple command line script (pacstrap) is used to install the base system. The installation of additional packages which are not part of the base system (for example, desktop environments), can be done with either pacstrap, or Pacman after booting (or chrooting) into the new installation. An alternative to using CD or USB images for installation is to use the static version of the package manager Pacman, from within another Linux-based operating system. The user can mount their newly formatted drive partition, and use pacstrap (or Pacman with the appropriate command-line switch) to install base and additional packages with the mountpoint of the destination device as the root for its operations. This method is useful when installing Arch Linux onto USB flash drives, or onto a temporarily mounted device which belongs to another system. Regardless of the selected installation type, further actions need to be taken before the new system is ready for use, most notably by installing a bootloader and configuring the new system with a system name, network connection, language settings, and graphical user interface. Arch Linux does not schedule releases for specific dates but uses a "rolling release" system where new packages are provided throughout the day. Its package management allows users to easily keep systems updated. Occasionally, manual interventions are required for certain updates, with instructions posted on the news section of the Arch Linux website. Arch Linux's only supported binary platform is x86_64. The Arch package repositories and User Repository (AUR) contain 58,000 binary and source packages, which comes close to Debian's 68,000 packages; however, the two distributions' approaches to packaging differ, making direct comparisons difficult. For example, six out of Arch's 58,000 packages comprise the software AbiWord, of which three in the user repository replace the canonical Abiword package with an alternative build type or version (such as sourcing from the latest commit to Abiword's source control repository), whereas Debian installs a single version of Abiword across seven packages. The Arch User Repository also contains a writerperfect package which installs several document format converters, while Debian provides each of the more than 20 converters in its own subpackage. To facilitate regular package changes, Pacman (a contraction of "package manager") was developed by Judd Vinet to provide Arch with its own package manager to track dependencies. It is written in C. All packages are managed using the Pacman package manager. Pacman handles package installation, upgrades, downgrades, removal and features automatic dependency resolution. The packages for Arch Linux are obtained from the Arch Linux package tree and are compiled for the x86-64 architecture. It uses binary packages in the tar.zst (for zstd compression), with .pkg placed before this to indicate that it is a Pacman package (giving .pkg.tar.zst). As well as Arch Linux, Pacman is also used for installing packages under MSYS2 (a fork of Cygwin) on Windows. The Arch Build System (ABS) is a ports-like source packaging system that compiles source tarballs into binary packages, which are installed via Pacman. The Arch Build System provides a directory tree of shell scripts, called PKGBUILDs, that enable any and all official Arch packages to be customized and compiled. Rebuilding the entire system using modified compiler flags is also supported by the Arch Build System. The Arch Build System makepkg tool can be used to create custom pkg.tar.zst packages from third-party sources. The resulting packages are also installable and trackable via Pacman. In addition to the repositories, the Arch User Repository (AUR) provides user-made PKGBUILD scripts for packages not included in the repositories. These PKGBUILD scripts simplify building from source by explicitly listing and checking for dependencies and configuring the install to match the Arch architecture. Arch User Repository helper programs can further streamline the downloading of PKGBUILD scripts and associated building process. However, this comes at the cost of executing PKGBUILDs not validated by a trusted person; as a result, Arch developers have stated that the utilities for automatic finding, downloading and executing of PKGBUILDs will never be included in the official repositories. Users can create packages compatible with Pacman using the Arch Build System and custom PKGBUILD scripts. This functionality has helped support the Arch User Repository, which consists of user contributed packages to supplement the official repositories. Arch Linux defines simplicity as without unnecessary additions or modifications. It ships software as released by the original developers (upstream) with minimal distribution-specific (downstream) changes: patches not accepted by upstream are avoided, and Arch's downstream patches consist almost entirely of backported bug fixes that are obsoleted by the project's next release. In a similar fashion, Arch ships the configuration files provided by upstream with changes limited to distribution-specific issues like adjusting the system file paths. It does not add automation features such as enabling a service simply because the package was installed. Packages are only split when compelling advantages exist, such as to save disk space in particularly bad cases of waste. GUI configuration utilities are not officially provided, encouraging users to perform most system configuration from the shell and a text editor. Arch Linux strives to maintain the latest stable release versions of its software as long as systemic package breakage can be reasonably avoided. It is based on a rolling-release system, which allows a one-time installation with continuous upgrades. Arch incorporates many of the newer features available to GNU/Linux users, including the systemd init system, modern file systems, LVM2, software RAID, udev support and initcpio (with mkinitcpio), as well as the latest available kernels. Arch is a pragmatic distribution rather than an ideological one. The principles here are only useful guidelines. Ultimately, design decisions are made on a case-by-case basis through developer consensus. Evidence-based technical analysis and debate are what matter, not politics or popular opinion. The large number of packages and build scripts in the various Arch Linux repositories offer free and open source software for those who prefer it, as well as proprietary software packages for those who embrace functionality over ideology. Whereas many GNU/Linux distributions attempt to be more user-friendly, Arch Linux has always been, and shall always remain user-centric. The distribution is intended to fill the needs of those contributing to it, rather than trying to appeal to as many users as possible. It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems. All users are encouraged to participate and contribute to the distribution. Reporting and helping fix bugs is highly valued and patches improving packages or the core projects are very appreciated: Arch's developers are volunteers and active contributors will often find themselves becoming part of that team. Archers can freely contribute packages to the Arch User Repository, improve the ArchWiki documentation, provide technical assistance to others or just exchange opinions in the forums, mailing lists, or IRC channels. Arch Linux is the operating system of choice for many people around the globe, and there exist several international communities that offer help and provide documentation in many different languages. Arch Linux is a general-purpose distribution. Upon installation, only a command-line environment is provided; rather than tearing out unneeded and unwanted packages, the user is offered the ability to build a custom system by choosing among thousands of high-quality packages provided in the official repositories for the x86-64 architecture. Arch is a rolling-release model backed by pacman, a lightweight, simple and fast package manager that allows for continuously upgrading the entire system with one command. Arch also provides the Arch Build System, a ports-like system to make it easy to build and install packages from source, which can also be synchronized with one command. In addition, the Arch User Repository contains many thousands of community-contributed PKGBUILD scripts for compiling installable packages from source using the makepkg application. It is also possible for users to build and maintain their own custom repositories with ease. The Arch community has grown and matured to become one of the most popular and influential Linux distributions, also testified by the attention and review received over the years. Arch developers remain unpaid, part-time volunteers, and there are no prospects for monetizing Arch Linux, so it will remain free in all senses of the word. Those curious to peruse more detail about Arch's development history can browse the Arch entry in the Internet Archive Wayback Machine and the Arch Linux News Archives. Judd Vinet, a Canadian programmer and occasional guitarist, began developing Arch Linux in early 2001. Its first formal release, Arch Linux 0.1, was on March 11, 2002. Inspired by the elegant simplicity of Slackware, BSD, PLD Linux and CRUX, and yet disappointed with their lack of package management at the time, Vinet built his own distribution on similar principles as those distros.

Thank you for coming to my TED Talk. Taterman gay.

Joe-Mega responds:

Your explanation is a little dumbed down for my taste, but good for the general (low i.q.) populace.

[Soup's On!!]

This is now canonically how you got your name.