mirror of
https://github.com/foo-dogsquared/wiki.git
synced 2025-01-31 01:57:54 +00:00
Add more notes
As of 2020-09-14, the following notes have been added. Fleeting notes are marked with "(F)". - Human-friendly colorspaces (F) - Computer graphics (F) - Software packaging (F) - Linked data (F)
This commit is contained in:
parent
8094b54f35
commit
3d1c0f5a42
15
2020-09-11-04-08-34.org
Normal file
15
2020-09-11-04-08-34.org
Normal file
@ -0,0 +1,15 @@
|
||||
#+TITLE: Human-friendly colorspaces
|
||||
#+AUTHOR: "Gabriel Arazas"
|
||||
#+EMAIL: "foo.dogsquared@gmail.com"
|
||||
#+DATE: "2020-09-11 04:08:34+08:00"
|
||||
#+DATE_MODIFIED: "2020-09-11 04:15:06+08:00"
|
||||
#+LANGUAGE: en
|
||||
#+OPTIONS: toc:t
|
||||
#+PROPERTY: header-args :exports both
|
||||
|
||||
|
||||
- Tags :: [[file:2020-09-11-04-11-59.org][Computer graphics]]
|
||||
|
||||
- [[https://www.hsluv.org/][HSLuv]]
|
||||
- [[https://www.kuon.ch/post/2020-03-08-hsluv/][This introductory article is a great resource on HSLuv]]
|
||||
- Human-friendly color scheme generation implementation based on [[https://terminal.sexy/][terminal.sexy]].
|
15
2020-09-11-04-11-59.org
Normal file
15
2020-09-11-04-11-59.org
Normal file
@ -0,0 +1,15 @@
|
||||
#+TITLE: Computer graphics
|
||||
#+AUTHOR: "Gabriel Arazas"
|
||||
#+EMAIL: "foo.dogsquared@gmail.com"
|
||||
#+DATE: "2020-09-11 04:11:59+08:00"
|
||||
#+DATE_MODIFIED: "2020-09-11 04:13:31+08:00"
|
||||
#+LANGUAGE: en
|
||||
#+OPTIONS: toc:t
|
||||
#+PROPERTY: header-args :exports both
|
||||
|
||||
|
||||
Computing graphics is consists of (at least in my study):
|
||||
|
||||
- 3D modelling
|
||||
- color graphics
|
||||
- algorithmic visual stuff
|
33
2020-09-13-19-42-06.org
Normal file
33
2020-09-13-19-42-06.org
Normal file
@ -0,0 +1,33 @@
|
||||
#+TITLE: Software packaging
|
||||
#+AUTHOR: "Gabriel Arazas"
|
||||
#+EMAIL: "foo.dogsquared@gmail.com"
|
||||
#+DATE: "2020-09-13 19:42:06+08:00"
|
||||
#+DATE_MODIFIED: "2020-09-14 00:15:26+08:00"
|
||||
#+LANGUAGE: en
|
||||
#+OPTIONS: toc:t
|
||||
#+PROPERTY: header-args :exports both
|
||||
|
||||
|
||||
I've been dabbling with software packaging for a few days (as of 2020-09-13) and all I can say that it is a rewarding experience having to know different tools (e.g., build systems, version control systems).
|
||||
It even made me comfortable in exploring the source code of several projects unlike before.
|
||||
|
||||
One of the most boring yet vital parts of maintaining a distribution (e.g., [[http://www.debian.org/][Debian]], [[http://archlinux.org/][Arch Linux]], [[https://www.freebsd.org/][FreeBSD]], [[https://www.microsoft.com/software-download/windows10][Windows 10]]) is software packaging.
|
||||
It allows for a more convenient software management process for the users and make the operating system more usable with more software readily available.
|
||||
As a consequence, derived distros can take advantage of the already existing package ecosystem of its parent distro (Ubuntu with Debian's package list, for instance).
|
||||
|
||||
What makes Linux more comfortable to work with is how most of its distribution integrates package management within its users.
|
||||
[fn:: Windows is starting to catch up with its [[https://github.com/microsoft/winget-cli/][official package manager]] (along with others such as [[https://scoop.sh/][Scoop]] and [[https://chocolatey.org/][Chocolatey]]) but it happened decades after Linux have it already.
|
||||
Better late than never, I guess.]
|
||||
To install a package, you just need a package manager which is installed on most Linux-based systems (e.g., ~apt install $PKG~, ~pacman -S $PKG~, ~nix-env -i $PKG~, ~guix package -i $PKG~).
|
||||
|
||||
Several of the problems I've encountered while practicing packaging (aside from unfamiliarity, of course) is of the following:
|
||||
|
||||
- How distinct each project could be in case they don't follow the standard.
|
||||
Not really a problem as most of them has documentation available for it.
|
||||
|
||||
- Some of them are built with assumptions or a preset environment which may need patching.
|
||||
|
||||
- Sparse documentation for building the software.
|
||||
Some of them are particularly intuitive but in case it is lacking, you're on your own (unless they're open for discussions and pull requests).
|
||||
|
||||
The process of software packaging might vary but in my case, it is pretty straightforward with [[file:2020-09-04-16-07-47.org][Nix package manager]] (though not-so-great with its [[https://nixos.org/learn.html][documentation]]) and even more so with [[file:2020-08-19-08-21-44.org][GNU Guix]] with its [[https://guix.gnu.org/help][open communication and well-made documentation]].
|
12
2020-09-14-05-54-45.org
Normal file
12
2020-09-14-05-54-45.org
Normal file
@ -0,0 +1,12 @@
|
||||
#+TITLE: Linked data
|
||||
#+AUTHOR: "Gabriel Arazas"
|
||||
#+EMAIL: "foo.dogsquared@gmail.com"
|
||||
#+DATE: "2020-09-14 05:54:45+08:00"
|
||||
#+DATE_MODIFIED: "2020-09-14 05:55:52+08:00"
|
||||
#+LANGUAGE: en
|
||||
#+OPTIONS: toc:t
|
||||
#+PROPERTY: header-args :exports both
|
||||
|
||||
|
||||
- [[http://lab.cccb.org/en/wikidata-the-new-rosetta-stone/][Wikidata is the new Rosetta Stone]]
|
||||
- [[https://github.com/Chocobozzz/PeerTube/issues/352][This discussion over at PeerTube]]
|
Loading…
Reference in New Issue
Block a user