Improved CSS, fix typos

This commit is contained in:
Yann Esposito (Yogsototh) 2021-05-01 15:33:59 +02:00
parent 8210724925
commit a22ec4e7ca
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
3 changed files with 29 additions and 142 deletions

View file

@ -83,7 +83,7 @@ figcaption { text-align: right; font-family: italic; }
--fg0: var(--b0);
--fg: #4c566a; /* var(--b02); */
--rfg: var(--b03);
--hl: var(--o);
--hl: var(--rfg);
}
pre {
@ -117,137 +117,22 @@ pre {
}
} */
/* light checked */
input#l:checked ~ div {
--y: #c18600;
--o: #d84100;
--r: #e62729;
--m: #ec0085;
--v: #6c71c4;
--b: #0095ff;
--c: #00b0a3;
--g: #879a00;
--bg: var(--b3);
--rbg: var(--b2);
--fg0: var(--b0);
--fg: var(--b02);
--rfg: #000;
--hl: var(--o);
em,strong,b,i,h1,h2,h3,h4,h5,h6 { color: var(--rfg); }
img {
filter: brightness(0.8) sepia(100%) hue-rotate(185deg) saturate(0.5);
}
input#l:checked ~ div img {
img:hover {
filter: none;
}
input#l:checked ~ div pre {
border: 1px solid hsl(218, 15%, 49%);
background: hsl(218, 40%, 96%);
}
/* dark checked */
input#d:checked ~ div {
--y: #ae8c51;
--o: #a9654a;
--r: #af6255;
--m: #ae5e7d;
--v: #6774b2;
--b: #3f8cc3;
--c: #15a198;
--g: #939452;
--bg: hsl(218,20%,16%);
--rbg: var(--b03);
--fg: var(--b0);
--fg0: var(--b00);
--rfg: var(--b1);
--hl: var(--g);
--b03: var(--bg);
--b2: hsl(218,15%,23%);
}
input#d:checked ~ div img {
filter: brightness(0.7) saturate(0.5);
}
input#d:checked ~ div pre {
background: hsl(218,20%,18%);
border-color: hsl(218,15%,23%);
}
em,strong,b,i,h1,h2,h3,h4,h5,h6 { color: var(--rfg); }
/* geek checked */
input#g:checked ~ div {
--y: #6A0;
--o: #8A0;
--r: #AA0;
--m: #6A6;
--v: #4A8;
--b: #0A8;
--c: #0A4;
--g: #0A0;
--bg: #020;
--rbg: #040;
--fg: #0B0;
--fg0: #090;
--rfg: #0C0;
--hl: #0D0;
--b03: #020;
--b2: #080;
font-family: Courier, monospace;
font-size: 14px;
line-height: 1.1em;
}
input#g:checked ~ div img {
filter: brightness(0.8) sepia(100%) hue-rotate(55deg) saturate(3);
}
input#g:checked ~ div pre {
background: var(--bg);
border-color: var(--rbg);
}
em,strong,b,i,h1,h2,h3,h4,h5,h6 { color: var(--rfg); }
/* plain checked */
input#b:checked ~ div {
--y: #b58900;
--o: #cb4b16;
--r: #dc322f;
--m: #d33682;
--v: #6c71c4;
--b: #268bd2;
--c: #2aa198;
--g: #859900;
--b03: #002b36;
--b02: #073642;
--b01: #586e75;
--b00: #657b83;
--b0: #839496;
--b1: #93a1a1;
--b2: #eee8d5;
--b3: #fdf6e3;
--hl: var(--y);
--bg: var(--b3);
--rbg: var(--b2);
--fg: var(--b00);
--fg0: var(--b1);
--rfg: var(--b01);
font-family: Hoefler Text, serif;
font-size: 18px;
line-height: 1.35em;
}
input#b:checked ~ div img {
border: solid 1px;
filter: brightness(0.8) sepia(30%) saturate(0.8);
}
input#b:checked ~ div pre {
background: var(--rbg);
border-color: var(-b1);
}
em,strong,b,i,h1,h2,h3,h4,h5,h6 { color: var(--rfg); }
/* ---- */
::selection {
background: var(--m);
color: hsl(218,40%,96%);
text-decoration: hsl(218,40%,96%);
background: var(--rbg);
color: var(--fg);
text-decoration: var(--fg);
}
body, body > div {

View file

@ -6,11 +6,13 @@
#+Email: yann@esposito.host
#+Date: [2020-05-09 Sat]
#+KEYWORDS: emacs softwares
#+DESCRIPTION: Modern tools tend to disapears. An app on the web will change, and could break for the worst. Quite often investing in long living tools which are harder start with will be worth the investment.
#+DESCRIPTION: Modern tools tend to disappear.
#+DESCRIPTION: An app on the web will change, and could break for the worst.
#+DESCRIPTION: Quite often it is worth investing into tools with steep learning curve.
#+LANGUAGE: en
#+LANG: en
#+OPTIONS: H:5 auto-id:t
+STARTUP: showeverything
#+STARTUP: showeverything
This week I didn't take a look at HN to grab some news.
And this week-end, in the morning I read those:
@ -27,17 +29,17 @@ And this week-end, in the morning I read those:
Similar articles have existed for years on different products.
What is their common point?
/Software tooling and their potential change and disparition/.
/Software tooling and their potential change and disappearance/.
Accross the years, too many times I saw tools disapear.
Across the years, too many times I saw tools disappear.
By tools I mean applications, web applications, web sites.
I think we can also include programming languages, control versionning
I think we can also include programming languages, control versioning
tools, building tools, package manager, etc...
The story can be quite different.
Sometimes the disparition of a tool is positive, because I found a better
Sometimes the disappearance of a tool is positive, because I found a better
one (from cvs to svn to git).
But, too often, the tool simply disapears or worse downgrade its quality.
But, too often, the tool simply disappears or worse downgrade its quality.
I think we can find different names for those softwares:
- /bloatware/: remember digg, stumbleupon, windows?
@ -56,9 +58,9 @@ This is what I would call a /trapware/.
#+begin_notes
/trapware/:
A software that is intented to put you inside a closed ecosystem.
A software that is intended to put you inside a closed ecosystem.
By slowly but surely add features that while looking great for the user at
first sight will ensure to entrave other tools to interoperate.
first sight will prevent interoperability with other tools.
#+end_notes
Furthermore, the fact that Microsoft is involved give this story a taste of
@ -121,7 +123,7 @@ But the price to pay is hidden.
So people really working hard for the best will certainly perform badly
compared to other people that simply trick the system.
So as good as Codespace can be, I think it is good to keep that in mind.
So as good as Codespace can be, I think this warning is good to keep that in mind.
Don't put yourself in a trap.
The [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] is just another story of a dying product.
@ -189,10 +191,10 @@ emacs.
When I started to be serious about coding, I was taught to use vi, not vim,
vi.
I only knew survival vi commands: =i=, =a=, =dd= and =cw=.
I only knew a few survival vi commands: =i=, =a=, =dd= and =cw=.
A few years later I started to use IDEs and I was thrilled.
Again a few years forward I started to work for a company that forced me to
use their shitty computers.
A few years forward I started to work for a company that forced me to use
their shitty computers.
Quite soon, I started to have wrist issues.
Thus I decided to use vim again but be serious about it this time.
And I saw the benefits only after a few weeks.
@ -211,7 +213,7 @@ It did after just a few days or maybe weeks.
I used Emacs superficially for years.
This was already quite efficient, at least as much as vim.
Recently I dig deeper.
Recently I dug deeper.
I heard much praise about org-mode and I became curious.
I discovered why it is so great.
Basic org-mode is already quite valuable.
@ -256,7 +258,7 @@ But there are a lot more to discover.
However, if you are used to tools from startups, with nice UI/UX.
Almost no configuration cost.
Be aware that digging in Free Softwares is a lot diffierent.
Be aware that digging in Free Softwares is a lot different.
Instead of having a big bundle with everything prepared to work you you
will need to take the time to configure each part of a big system
separately.

View file

@ -10,12 +10,12 @@ This weekend I read an article about gopher and gemini.
I already seen articles about gemini pass.
Somehow, it was more appealing to me than gopher space for totally
subjective reasons I think.
Anyway this time I really digged into it, and I loved the experience.
Anyway this time I really dug into it, and I loved the experience.
At first sight gemini is like a parallel web for nerds.
It has fundamental changes that I would have really liked to see from the
modern web.
The client decide the design, no user tracking, calm, minimalistic, simple.
The client decide the design, no user tracking, calm, minimalist, simple.
Right now, on the web, most news website make the experience terrible to
read the article.
@ -43,7 +43,7 @@ client within a few hours of work in your programming language of choice.
And last but not least, gemini is unfit to serve "big" files.
So we should not experience people going to gemini for music/movie piracy.
If you want to serve "big" files you should link to another protocol.
If you want to serve "big" files you should use another protocol.
Personally I started to browse gemini directly from emacs with elpher.
But I know there are a lot of clients.