From 175612b82f19138c59884caf29560c3f00f1030e Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Sun, 3 May 2020 21:50:56 +0200 Subject: [PATCH 1/4] add gzip size --- engine/update-file-size.sh | 13 ++++++++++++- project.el | 5 ++++- project.el.sig | Bin 586 -> 586 bytes 3 files changed, 16 insertions(+), 2 deletions(-) diff --git a/engine/update-file-size.sh b/engine/update-file-size.sh index b0ce241..341ea88 100755 --- a/engine/update-file-size.sh +++ b/engine/update-file-size.sh @@ -31,6 +31,9 @@ for fic in $filelist; do htmlsize=$(sizeof $fic) debug HTML: $htmlsize + + gzhtmlsize=$( gzip -c $fic|wc -c ) + debug GZHTML: $gzhtmlsize xfic=$tmpdir/$fic mkdir -p $(dirname $xfic) @@ -49,21 +52,29 @@ for fic in $filelist; do css=( $( < $xfic hxselect -i -c -s '\n' 'link[rel=stylesheet]::attr(href)')) csssize=0 + gzcsssize=0 for i in $css; do isize=$( sizeof $webdir/$i ) + gzisize=$( gzip -c $webdir/$i | wc -c ) debug $i '=>' $isize (( csssize += isize )) + (( gzcsssize += gzisize )) done debug CSS: $csssize + debug GZCSS: $gzcsssize total=$(( htmlsize + imgsize + csssize )) + gztotal=$(( gzhtmlsize + imgsize + gzcsssize )) # the space is important before the toh total sizeinfos=$(print -- " $(toh $total) (html $(toh $htmlsize), css $(toh $csssize)") + gzsizeinfos=$(print -- " $(toh $gztotal) (html $(toh $gzhtmlsize), css $(toh $gzcsssize)") if ((imgsize>0)); then sizeinfos="$sizeinfos, img $(toh $imgsize))" + gzsizeinfos="$gzsizeinfos, img $(toh $imgsize))" else sizeinfos="$sizeinfos)" + gzsizeinfos="$gzsizeinfos)" fi print -- $sizeinfos - perl -pi -e 's#(
)[^<]*(
)#$1'"$sizeinfos"'$2#' $fic + perl -pi -e 's#(
)[^<]*(
)#$1'"$sizeinfos"'$2#;s#(
)[^<]*(
)#$1'"$gzsizeinfos"'$2#' $fic done rm -rf $tmpdir diff --git a/project.el b/project.el index 34d55e1..b9a2a8e 100644 --- a/project.el +++ b/project.el @@ -171,7 +171,9 @@ (format "
%s
" (format-time-string "%Y-%m-%d %H:%M:%S"))) (size - "
XXK (HTML: XXK, CSS: XXK, IMG: XXK)
") + "
XXK (html XXK, css XXK, img XXK)
") + (gzsize + "
XXK (html XXK, css XXK, img XXK)
") (generated-with (format (concat "
" "Emacs %s, " @@ -195,6 +197,7 @@ ("tags" . ,keywords) ("rss" . ,rss) ("size" . ,size) + ("gz" . ,gzsize) ("gen-date" . ,generated-date) ("get-with" . ,generated-with) ("src" . ,website-code) diff --git a/project.el.sig b/project.el.sig index 5b4f1b237f0266bcdc21e7c83f56292d46e39a7e..b1d3f506962ed2aa4d2305cded145c4559f1576b 100644 GIT binary patch delta 534 zcmV+x0_pwA1j+=EBLlA>j*%uHf7JpH|9&1O#FPYUt;@Ez;^^7BpwH@Z8Af5GAWoXY z_SHl2zwgDbit@~o{!j?uU`H*D2PMrQC!L6V1Ww6=UYDu@QjXF}E=0l-!Z2eeORXN2 z9rf>0rwn5eb1?gj=bp%Kir;RcreHX8;p*~YiZE;LY z&Y%MV4zn$3xh%t_y_taSGWPF4)-|@-{Nk2I@Mk z!lMwGCsNrN^{x`d)vqd-e;7DvzRNz;7&4QQP?5MK^R*u4EHR4i;ODnvv|CpBOYp#% z=quHgnEPrA0sXSdD&V}HLJR|!`g5AdU4GK|kb8;mF@i_h$GAAT&i99LJmy~XjHe|dMIL3$A9tyS=M z>cJNJ3$hcL(I&%A$Snog{&K$u6(6_aKs$_f7xfT<)`{nGWaYyzH@`HOTiUIWOHkg1 z4MrBR-O&AUehB*{0|r<%6rhPGb4Mtv!)O(SzM1?LFTEG;%O8kC!5~-QqVSH#07;Xd(BFjT(FmNCExj0Cy8 z8b#3Yl=EBrG-X#8B>`XU$0y7irdR5zOMo`p&d{Sq!e3;3_Ur}&@%hF3 zH)ACS&ZIeHcugE#hG}C6qT?>hA>C9|=HN>=M@qS`uaTjwpp?odB4mO|e*q@r?7k-P z*ZDCi6@)|!+W&XBadV3 zDAA3%`P1&8!U8y_;v%o;f6c~hqg%-poaKK}UOG_Y8M|xjun=6 z!q=j`NaK?aVP0o7g9pwP%+{!i+g;>r4i+VbB$2BTE5yqw^SRw3f6#%I)|0cPvYDVK z={kuV-i;}Cg2gOcLG+;8n=aE`4ie^MfMCPoJw=_`g`I&0fW?{AcADv>Pb(7(vl=sL z$nnl71MPa^S>XSbD+@e+aHNUWAt%>@MjmRQH?s#}L*KhBlATAaePNR`RR=XM<)6BO Y Date: Fri, 8 May 2020 17:58:10 +0200 Subject: [PATCH 2/4] wip --- src/drafts/XXXX-roe-colorschemes/index.org | 17 +- src/drafts/XXXX-roe-colorschemes/mo5.jpeg | Bin 0 -> 17884 bytes src/drafts/XXXX-who-control/index.org | 233 +++++++++++++++++++++ 3 files changed, 245 insertions(+), 5 deletions(-) create mode 100644 src/drafts/XXXX-roe-colorschemes/mo5.jpeg create mode 100644 src/drafts/XXXX-who-control/index.org diff --git a/src/drafts/XXXX-roe-colorschemes/index.org b/src/drafts/XXXX-roe-colorschemes/index.org index 04fa819..acec92d 100644 --- a/src/drafts/XXXX-roe-colorschemes/index.org +++ b/src/drafts/XXXX-roe-colorschemes/index.org @@ -1,9 +1,16 @@ -#+title: My story about colorscheme -#+date: [2020-05-03 Sun] +#+title: Return of experience about colorscheme +#+date: [2020-05-04 Mon] #+author: Yann Esposito #+EMAIL: yann@esposito.host #+KEYWORDS: colorscheme -#+DESCRIPTION: A generalization of solarized (https://solaryzed.esy.fun). -#+DESCRIPTION: I tried to make keep the same fundamentals and to free some variables. -#+OPTIONS: auto-id:t toc:t +#+DESCRIPTION: The list of colorschemes I used, why I changed. +#+OPTIONS: auto-id:t toc:nil #+STARTUP: overview + +* Local variables :noexport: +:PROPERTIES: +:CUSTOM_ID: local-variables +:END: +# local variables: +# org-download-image-dir "./img" +# end: diff --git a/src/drafts/XXXX-roe-colorschemes/mo5.jpeg b/src/drafts/XXXX-roe-colorschemes/mo5.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..5092f5b89423a5281a1e6705e1d59118c3abb9ae GIT binary patch literal 17884 zcmeIZcT`i~yCxoNsMtV?jiP{b5TpqRA4|Z95vdU(paN1ti1beEN|!EOKtRBN0!bj0 zC{?7eYq8HJXTRrt_df6YJkQ|{bAJGi zTsH<81Nis=06yLifXe~sU$FpQvNE&KlX7)d@p$OsDixrvdQM8--`CyCRSI<7MC$r2 zpovs~wuXYTl(+vqPj|mysf$t<&h6(?09ODzckKA{%R6@Qes}NPy?fWL-TV3Z_v}5e z|G)u({Q?394+$MPcu4S&fWQ&aBZ5bTMMOjn92Pq!Dtt^xSVZ{Gm+>4 z{C%G%`}T{99XozP_N<(|f}*CDwvO%vy(?FN#wOQ5*DbBAZ6LR8?VOxl9=N)>d-(eK z2LuKMhdh1u{Kd;xkx_|B$tkI6Z_+dJ3*HqL6~8Yjt*oj>W3V-~xTfZo*0%Pq9i0P% zLj)pec!WGUHvV&Ba%y^Jc4>L#_bPL3ePi>FU3`F@|7I5N^WO~nU+fa(*|lTWuARI1 z|JcR1Baqj23hvr{T78euC3F6J-bc@9Jl-pOIU(=UmwnRbEq;mI_vzm+Dx*0nyY$Dj ze_6IY!=C(KS@u5+`=54^0S9*S@tn6)5MTsYBg^OGgN(YQ@}uMd|E}%aGqBcrxV##o zXP9s(c2ZZ&+oQ7M;VsvD%izj#v#x|m@1!TgKdT#-uFRoCdgI?+DF}|+{oU?EOM1>oX{Ea=)gcFQ2aQ~kq<@D!hjJMrgZvP9eUhi=V& zp|8PU;T8BX`mbevyG;B-0lJaM=BRK1ho%1?I_ag&AugZ}3T1@7jrqzJE=Eb(yOsNepAkRV{ZMs`;F9>`ZEy3>OqV;kY0}-}a=SnEt_tgY z3}lme0kHVTDUXRoi>&ty1R9V0tbwIfT|hQcYmtDAu1SG(NbEsdj85Fnt?11qW|&8&i|Wr#G9^2 z@?_DVx#<8G5P{+X5>h~IaNRE^|NYOj*XBTxbl!(B0P+OZC`}k!YK$GFswme}!Few( zsO@Cf$|SdGSp90yKT2#^XuP%F&IL$ctY8OMa9*rVJ~*1JP%Ikp_{;A+h@gd*2qA6O zpQ)D{U9rlGsu{uZS6IX2=(@W4fTNxXDs;~$=d%()`8DsjW8<#>K^iy^Z-v!xN zs-^EeX6^6t5OQHx*cwrh3sB$e8#+h-`W*8sw^d-n;GF00aE;|bM|9l6$!Sr`-IW?I z&IHJau!e0Wihbow3j3vvnHhPA0O@r7#< z<`cjIFF;4WKRJHw$CJHMQRL?#i6z26y`9blg#-n6o&&uL7Xb=GNRqwxfWo)<{=c+4 zE>q3oM&`+&01U~3uiAhZ_4DwJq`@TnY!RVnu1nHY2V*Lp!oQ`dun&oGL=HuB0fwoP z>pPN>O?myusexuL0ANv9s$_J}Y~v;u!1&P2iNH5+#r^xSDHn5jm$;eS;f5hr3Rc%^ zM?H(b@pSO9eYP;+1k5dRN|*Uz7GH}@7^eyUDvmB+?N~hy?#+2>-|*Vee*MX&3Cy}7 z&C}_oA4}Kd*k47NxfSui|{&UylcnwRJaxZis-oGJTybgeuG((MND z=A_4KJ(BX>J4*vQ0@puk)5~&LIn|U0!8P=~^ZxAB9YYVM(Pa$qtF@_e86`0~@;P z`i?_kCkk5vA?I(qZ!!wA3txY9{M`k8fjQqL{k%)&%-F41i5|S`SxdDZTTG7p(xvqe z#O}=oW-Jr?a(?NyDcq~%NnVx8Ba5SpVq$p1fv<-qUXJr}Ya z8$3p7Eov;%#%JBSIzAs06;?T*I(B;iH&t22rUea2g=peFepZm8p*lC0h8JC3Im=}W!-8WZ>GeL`5Fb@U`T z=;@evdkeAZwJFR)OYRa}`TWVF&XuPOR|h*cVgZMY2Gu7&?mBeu_}D`v6#ngJ)RVv} z4~7>L?={Ej?mGTx^LJ)5OSjaW)>Brqz<@DH*6hg>emc0ob~e-wd>&GbZHUts_^k3X zai7yI(c`b;sM2!5cTAblFRxKk3SzHhB3;Y992tk#ZAI~}EHfsAc?0i7ulu@EKh5c> z3hcro$ZNr2cwjyrUQJ-t z7r*%nuYm)D$CcntRyA?6ldywE_SIF@m7)Tibl5{;Td?!PTIXkXt_v27VCR2!x@?pU zxD|b>9{XJ&?nR4S7z`K$7J&TBLT4?y-GMYsX%q!#7LaKQ7LAp`@Oniij|3IBxG&j_ z(V*cD7XjC#++-@<^Z&V=fBi#hC%}C_X4LnBwQr;R=K$>QO{KKMcEZ6MKMK216=qtE z#iC+@H(%ZBbBbN)6aNC&&9MhBj(85E#=QOMY1_B&7PtG!d2&vETs zMYUvg3o2R!Pdc+!gn?a6T|zUb7g%$!;pxpS`^I%*3P z*9^?HOod{#Gh_+h!3A%!CvaI`{P%s?xGJcY_2XcZ@%QUMR>tttRzqpCD3a(hWp-(L z$EBT@WRt)`J4A%6oiVp|UbDsuq<5BOFB$Jdn#0z z7GjwTm_Yd@Lxex=YXzFPEz`@_a16?pot0A0HHXGFba?5@U zWeG`n&aCkE%Q=m!#14|KT`KA-ZhsFtkO=a5Kb)wWYX7$DsOSsziAKht=U+r*NVo{a zApCe==CE-GjT}yv4O)X@>o70#EYIgzgwbuHKs2%nP9Nx?O|@gpQX2*%hY+e#>m7M5 z(v2CN_M!_q-bG^ACzhHAa%V29y~eex{?vdQS~<$!FRU#y6ApU2WdnNx~TZ@jS=ej%d`!qXXfi7mpZwgMN$f^aVK@kBP7`nsSih5yu!Cs%< zsI=NH6t*sm;;>0E&dqMBZ#pcz9&4y{2ik=wYk#|M*TG$>V9jfLtw7d^BmW#cZS!5# zRk1v<_1GaICl}~5I(IqV$UwL@1wAu~9U5;MQ}{Mztx&RZ7CjSD79NTOt^f7?m5^Kt zj6#DQY{bY7tphsnpp-Tl`(W`09%e5!UHV?XIv%Y@Lu*{e1ru;+&WQ}yP~TS!Pe zu7CnLIXj0fk@@;&N z?3OVBwkKaVJk>!n2R?*+nCr_-ksXo2%T%lw)ZaWk_F$?rA19NDO^tLU%m)93r({Th zIT{$Emg%d7@&_LWS1G3Yrl;@XXHu~TJzY~x1X8a7Tk=j^%#7&0QRJA>a5ifGHrYGG zJPwPvy5?Tzp5OltC)cogQRK})biJDi6ziA6&`!-zIRWy_SsVH*kA3$;(mWi0pG*aqgxiXR2jgCg0R8}m@uw(54YkjJxd^zej zO?xRh7~cJXL9M22P+VNd?G?(+8Rz3=Yx4)Iu=U@esnlSL2^-TwwC+Xerg+$rlU>94 zIr!aFQLJ{CVM!1Z>6QxpqI;Ws<#^L8!yESuFX#CjL~IXcxJ_u)>&wV*j8wuFrj(-{ zaMU|Z7!B)*9vg$c6rg>BGRpr!gFmir_{VSF&G>~21LZRCRY>QN4F@E}sA`L`yuq`(A6;jgw~-$#v1ufgz^?&I#n=;yb!QM=z^9!AG6H;6BgBJvz$`6))D zdL(=mepHo1;H9*wlzAfS1?Y- zZ}5j>=UI(ketL2N5T0-Kd+1xxt%~pcT!08Vl~+2bt6Uc76AdjSJjcyBK29Vs(!Re% zj74$*zVn(8S7ye*kW+zKd6!Gs7K%*7g)i#b**(*AUmfv8hd?{28R)^K#q~^bm^sVJ z5*G5Thzsb_bD`!GoD$e69xGJ~;(RtgbJp5Yl)3jk9WPrp?3Q2i>2`7CPaIYeyS3Z7 z+FmD|GC&JBe{3l$&1S-8BfthEgY#M?nwbVqJqhzve%_W)Mp=K1K9BMce3v*)8URjc z{ia=7*(x{|-|6;?f+-z;&3|$;_c{8YS-YJon%&^*Ug-Y%CVoV;EZK z2y%T2pK?4!?;1O~DBK|pgFGP)=&ShOzr-Z5F1V*!x_t}27qm>!PN?~z?bk?H+R5@| zAzA0wBq{h28iX0!zV)<`!VIV1UDigHvAKZk$wiI|2eJSgb}QeQ%v$kH(Wjg05N(1aXgC6QCW+IwAP zNvpgxNTi@B+6GO?il`W^%d8N04}3kFkt`W82F4!U*e85ni>24}7MiR6?tz;2jCYMm zzr!IIE3k$BD=8T1!J7pdiLTF`cbrdPCov_f87mQ_pS+b-8Nrg|Z70xWI2Vv=JzH(_ zd#S!e@wG)|WkWryxClq?t4_sE7ryanHAZRaD=AUx7IHFXQ*y0k1Ci(ImeO7^;9}QB zPt&IdBil!g3val*vv2vhTgG{0+xbeJhkOt&5N>gO)-f!l z&Mgf%*tjO4mqLjZE-$78E4dd%>9_ikSs32tI4SYZADHF;(D+7k4q~&ze35Fe5cQTa zu_y-t=(Tw?A(EfsI6qNj3of`c@qE0?iflaoXoLsgL^c$+N}_?<*!R~FTUAB&BeUwC zKdKK82qfpu?-n}aVy%w28x_l1wrhA1wN{)_+iU3^Qf41^a;XDE)=%wBf1u2yK35A#kyKa+t<`KaI9DO z(z4UOWf6hbu#oNHrz@pn*{(h2j#pDC1Dzzh3VW~eV69Jy6{;SeCc{b<88a@hGOalj zf!3bl4&_DRStP?~-4s76&mm^Iju?)xbD3t<*raUww7y|iRp3@NYnaVZ;{SqKsfa^N zEFD~na!x>(eSx`)r{X?Iv0&`1>Mn(9H-nG$!5*2{zCS!^I0X#+(DS}iQN>p^*1a*> z#Elt62)wA3rFFa&SndLsDaWok1=U@#KZADc7MXA)&e-SRS24e^0#vYn@@~-n>W)lPLWI0 zZqrEpG`-ns1lW9>z67;(!>CaCGMIB2-?!!X~z+hHdWdh3%M$0PKhBG5^@dQnWm2&_!#Fa|%;b)z!V_-U6w zdumB_Y&&1of*+(nnQUosQ+smI1ce@8fGGAUsTr~;w!3RpmaEty2e_ITuYcLX9abG| z6V(w);yo--AF3TUB0Y{c1XWR0Kd6xGwhp9Lcs5S#L<*a+k~n9Pl-v~!E}+SYUB?BO z;YV^u=)CRZv)cMEF5vMZ7f?i)*R*jYhjJK7nBN0y)2w#fV5Tv3fo4QG$(i|AA4_BL z;Kk{g9%o7eWx0Z3@5(ab2vRfXTQWw!64}MQES0_lrX<7BND@Z*InRIGKK$%!(Gn-@k*`~w%y z_Zb`=zvrx~8S6lAIarbnyA>;wX55&lrchC|d^mUFSWASZ$qOnPa_W)p_DBBKQ?P3J zR?-)OpaoLhRw-19eS_ASaZYxuBDxUH7!#!m33LeYn(se z+dgD{!h@=s;Q*5P(6~n3{)6KH>~DZIha{k05b2~sD@Yb@5ssjMH8<$q1Kp=CSYK0k zmq?H+TrA3PFYamRQ{+&Wbhcz@j$|~R;mAP9vBX$1NN4s-hJF|wy&;L5&uwfc8xglM zkrOF*>gtzLFrP~AnE3l@y~r&m+mdYsc5?wY&^0h8gG${ym6ugz_x8_Im_9BVTZ9=+ z8@$8wL8}6+3l&~Ow1IX(f-kDnb@M9B_r^pLkg5Y0NlCiCmRRQnCbtTkJAg)?3!DG5 z`+w6;Nk(m%`IdI3@Bf-Z)hDbKXs`mwsMGyQ!|@`h<$X zrKLmTV=&vVvS{>)q_>#Vqx0kA{Uzwv7c+OsYAn?$)$DdjRf)zQ4~ir9`{ms$>#K-Al5c8Y=X5ft znl#i#T8Y}56`qh_mTCw5ZVIq4Hv9DaSpSpa{oW~DKxRRRFOSj+%tx~s5PxJt@yqA? zJyP_{bG1kfIE0B-0h<`rL$)hsrmzj`$qOrOHsrPvZ*f95@kB(OyQ{mivKU)~IEso{ z{yOT@v9~5!+N26G(vjS?Vso(gmEq~{VPM#WT^LM(g`em^v-&4()6>n1_68Miz5&MB z=Oti(eDo)7<@Pk8qL)HLU$$%#H|W{=VX8 zIfnu=Vrugz=)elNY7)f$w*f9lF+KdIUDVOZr)eunYN4U-ep#0Gzr%0pZ5N|vhA6dd z*C8?Ajj9)>n>0710|(eNdJfg0=w>dnb>i}o!ujz)R0WlRY-G-^YO83Wg12n?@6gwu zh+koW#!eX6o#`k%c}d+WiD4{zT$|z|$G9LQv_oCu(#yZiw+AYITWyx)X z@~TX-48KzmYNyxPfqm>g7B4Ir)#KS$Mt7sbf+G4vo?(cyZxl~z z4DUW|xa1wW!ccy+a2rOPt~j@S*fmq0habR<_n%52_0l3e*oL7JSKn5dgk98a9%*)1 z#@Y)J=-56d$!3n~l1)ijXA=ujgEKoqwS~^iy^|Vr85|#yc>$8Cwekd=GFAQN5*dBv z*fKp}1|zj(_G)kp-CB>?tPcUa{^uLWdGP9^=T}o~RgwV%BJie3pVFx?^G6JX7Ii8H zg^slt(=SW^pvevx=pFcaTW!+?)eJp8kVsf%IEjZStHdU|y z_F`qImh5$(B&)YWc{;@-{iYihxY!Tm2FhAv=OoI&eC+9xEh>FAlyQ=QI6N};F_lcU z+tF~qsQrZ&K2m+yt!mb%D`0Z)Dy}ZF+V^NZ*7A*Np01Jn z6WNt4zM5;4$ZL3C==P(s{rD4qSC2c21~0_RPK4 zFUjZ0bYst0wfpoyoyP#eTAtSRcQi%_SQwINhx?FUD};4{O=Gbch^gsd-I(hw#!3mm z@(!ixRLlx^i&1Iv=F(WMU~wxfIvBnh^qWuW@!Q0XqDa2|k&2a2dA@gwl;_5cfk5W zquW5#L=@Oof20guv z_gUbet!X~BZ9%h%`Rn?F$4P8?;Ii25iSIAK#huX;2duE-qp^sw8v!SjH?u0KwblKq z?DTP;HXWa*#DOF)!?`e&{)Oq(_zdPf{-`kHT#<5>2`pj! z+pZ^jo|vA^klCduQ`+JAcF*fFFR}9}5dEXGs+VHG!6CB=eBER(rZ* zodd^{pkqH+R1jpD5r(buP=f@O)y;)AW>8@bT);lLEgQ*U$&rw>t)TEamgPJTf;F1c z4mR{c@}L&c?r@r~$(Bs+(rx5jq|2=1(kOG0VOGTjyyXHujQrfFv4!169TYJ*6`nfv zm35d|ksFU@EC+avT=}?edq23=&SnwW zudm7&QAJ7Ei18aZ>c}Kc{OOV<-t4!tFUu(d{tX`>S3FShB1c?K8x2?TN27lS_OFV{ z@muas%Cy6z;0od4;%pMZLm2Y6aGn`Q38o^(xo`JOEJu0Gv`oOCh~Ft&Mp3K%hu(UW zGu7Y{yJ)T!(z$7m)L0IoG<+zZj|Vv~BSmhPb)`6(mM1wOUMhcf3=lY!D&wWuo2n2(=`cnSY;nf}!^c1q>-&P?kcqiyF0y%mbW16i^ zF>QUO=QAtFNLPKLAp1iw9guow-vgUSVfAO*mmx$kY*V!O`7f)Pz(r#zT`pcYE+7>D zwkkyN(BXsp1(;}KMma^vzaF!OMLgvYmUPnD&nu@`Fcy?yL^g7fbmDZgT+`!qyn46* zS1!P0goEwg_*At zXfV21+!|xL5r)MztW~*d6$Rth$ZnOh5IrZc4ethE#!+MbCu>n04L9#L zTrD~mSQq!BU8HMxU)c1C9W6WegV0`$PA}T{j5K!g_`_t6QZS~%k3>VQBW53t&M68d zd8~oMXUev)tJnUDgu?y@5^C^2l29X)e?^*=@Cd5)OpXvjjbTS;Rxq(i>}YnP5igLL z*^LPDRy>|*Mt5RJ&P9On%bg82Q8e9YS$B)*!OD5;;DZG!O2sen6X8^6Mr`3_6-woN zD$bKiK^LNu6HQ`*oS^GT;xD2NiH;?Dm!)8Pwph0(+MT3ha`g(2A)m|O-1F@%k@}tq;}TMYEqm{> z)?E+@DJXsY8a#0dj2T$EcPI<@EcAit+bB@bt_T0frtPpz$p;>|x83S8-Zj52)dhU% z%eUx$3a}txc?4RHr!CGX)1sa}ZN4FM7T5`oE(G-GV#-dp0|aC4T*43-y?;ADo=vocu*SsD6$DW!7hVx2pr-v@)NSs zglRS$F^KJ9IVP;}w%qyf0yd%p%dxfoD?Jqt_6cBzh=DEQsA>L~Oj}!oiv7>u*mo<6 zVI8G{Xmo!dm;!Wh9%%SkPDu**(>8@@8JscJ+cwoi8t>>|4keB5BZ)Zn0ZglF65ZHhKZyW#BFE9BWap3@pbq z*HPXGmBtE*M>0n=g={tZrB0j6+L*ckG@nBs)@GH~(uMEpLpQ@k`VE@0K{qY(#4YV) zP@(X`@(=Tj@K7aj>+{#OTrQX%+})jF1F~ZhZ0%-yieY7oE>4j{UXxg!9;E%m>?AQ< zbV2{=DTvx#*_F3$0!I!goF(8k;!Ymhwe|H-GX76is}j-oudFsbf{Oo>)%LS9A1v~+ zTJ*y5MqA%`jx7WP^ftI$Z4uY+O@dMzA|QiRpx*{-(O{rFLrmPifkN_1<8{$ZPi>!$ zYKl@iky2<4G@UO)I+7-R2^EU{&s><+c*(hy+5flsNcfAW-^BX`XxSxS{ke)%BGfi4 z)4e)WKs(0pggWug!sZ-7MWg_oit_xPSRAb%J?%#35 zvQX9GwyYWE!}z^|WqUTPiPjsBM0g~tgru0Vrrfc@MJPTur_A0G7jCJ0u4ZQRwC-hv z6(}SkZ8`(2KU)}7=aJ5%C(d)ea{=jToTHKq`erz%o72leaQKis!OLMJTf02XgwB&H z6}O~wC@dW&I5%aAUBxo$rK{ymc(L2qxz4OC_LlD?DH!Ny)y}%sX;4>$B{TF@G@~#H zGl3-}$a!W$axK2!b$~mZyMU?oAJLec!(0bGy?uRSV=t;cJm8 zR;>+B6m=FmJeVhx92q)9BiFPdDrP+_t%1#s#bYFIhsS}5^sZkshh^Ql033bw{(`Sasjo>6Y`uv%9{H~ae18|)J`dXrW9WE&0rism3xqbV=$et%3>q&U`x36 zlc>MJ%>SnTN%3jlr`r}-SqIl_gi-@j6DanV8*k3^G#zb7p?D`cs_-N`UDr@r1c_YW z-|1Vlx4$cW{e`Sg(bD{Gm5JtbQmpV@-J?MQ)+xt^EW9nez7y9h;T~yl=8C?DQisa6 zQ4M3ceFoA|nGVZfXw_oqd4mUgig@LO`--frS0Bz@QyB7Jr>e|zA*i|Pq8Mc)t0X(m zg%2zkrr562gEo+5!>kLLO@x7SHL3z|B)AzUzyALA0pNDAr#S~(Z-Q2orWf;iVn17b z)>TY2OSiYBo6TV!1B22cx9*Lr$la+t_kGs9M=cWm0Wt3~Xywi%JExTi`!qkizcG<; z;=9JifXK>3(`hp*;xA-;{#^V=b-Td2&tR*Bypc%8NG_zYzmfQhoujl5jv}11(suc{|8n@)*xD4? zmhbz=!BlfQowa;64Zaydre#pNeZGDY#N)->e5YwN47Lap-UrRE(fJEBS%$oAs6uXt zl6W0d?f{$Xx35SVVA*ShPCsN{z6ml06(0(n8_ehJks7v`!im zgeqzS2;?L4ITp+4{qk@IAvo!~N<4W0~g+&=f zwD{4Gk?G!-$wLS4=YW4(@t&FtS;9z9aL@bSx!so11vGD$1=>Du7Eht zJ&u;=GM`_NA%$`x*)03QIuHvkGAS0Ju_TVlpSj!&$#s-CeKj?xx=nk@y`m(xVoF$0 zmnD5BSGhX6CKd25CR1;_w;B`AXRZ@~Nm@0B;0vZV*`)r7l>6l5)WLB3A?t-|vZKo? ztAb(<{Cm-=>x(aaM~`1ukv)lsz|QBwp_TSGKEB!i=IhOeiPyDhY{ZCRFJnZuEZ|~J z)b@*wvR_5HW7M0V)r%%AI@*mks8C@&s|-Jdog;-mOC-}%gsR>=QaGchYLIXKYw~8) zi08*8ixLaPnTwQ$MR*dUk>=_kEuSO0-{0fQ*(5t`D2-U{=vq#54dz+6eOwl}-PKmr zsptzfekZ92pWU=&Huk`<**!EMG~=C<&EW*?dHU5{tDGJf4EA6#kEbc!^H+tTQWwf( zczHI%{h|SpE>|$)M=}noiP6vN+(@zjQG-#C4ys`q*wI)R@?Tb{1CyD=gcmexjS1I@@v_gI7_Q=fd>#^xV3;l0#CFc40#sD(;@y3kqzJ97EJU0C%ax5 z@=Dvii$#@bz`EG)?#~%Nl6!W_ZQhFhsrsp__CTgtidg5d63@fir~P?lW-Ht!p9|s zY3-epS4kNnBoi}QZEG+K46g@k8Qa`qiL8#YX}qYKms~D%NHg|k(}2LqW2ZsNqvZ=f}uy+HWI!hg_dqS7d-mv7rcIMJaZ%LO88j14BX?F9ofXC{KGXvG7sZW(ddMq zIIOHDVOKPub81gtElKsB-fj2ymoutfDg~gai++sq5|2b&LrzJ#@_^q%e-WNOH0uI% z0!?;bk%RkRXUO{d@y^Ma*VjB9Kl}1X+$K!H4_ZTQd*eXccjKD|vT$$X<+)RJuRE$Y z%)|1cQoH|-yL+OlRTJj&ps2k?EM#TQQXn13_$_*CnEif3_GoA5asCnY8c~z4Qj!Kg zuN1h^RG;1fUk`;}-|MoZG9V5_cg?+wBQYwU9W2t=I3pJ$b9yK{TCwNRk(AlE6Pn{< zs!;jD3f0DyurBCwbp}}OEZW?w-Sgb*!eg~QBR~_{t+iau%tYcAO72*7*3ay5(fKRo z>uW7c$)ldXGwr<;5QBCv^c#-$eoUl+^*}qG9#G(9$X#=e3v^dMwmfScN;mWi~=6!{GSu++^KeB>F$UiMY zsKtm7ee4!()*?i1+dMmA-O_Byt5{|;r(o=4rlXQgLzK88SWo!z{J^qRe0OK0ZTCOI z3F2ZB=JM;la#~!#Q6om*Mmlm-okQgUis|!x^NScR;D^{&5b`rm9zN(%%P#xyFVw9` zzltXod-jqe4A1QMj&W;JA2IU3s8vr` zT!6a=d->ciDSaK|X8Ft!mpNeu4lY$HW;IwBH)d23VDX%9Jn`%(g8j002>%iPv7QT% zW2qZ9GvlkB0?BJ$D*@g=8Ey2;3u7hIEZ#uB^&}$-@&Tu#YMD0_gLK`XOss67=r#1J z`CQ*zd|Vj$=@&z7(aYo42#l?N$mvA%-T{ywZ05{z#wJ2)gJT|JGNBm+r&xP`-5D>T z>pl>ZCEXX)Ui7_l4Z5Z82zI>k<;5XCrwf+x`rdI_Sgb*CZ7LUV5EZT!e)vj${mQn# zJkDtQiaFH_o}_AKY`Hy3bOTEWc5kE{x^Q){i~+rqX{WM+D5X#b$0*j{*YxBojxFt} z7@LcAkUvwiw1dV2^{;rQ>A^8+(R=+ShNLMP_PZ=hKTB)yDc1;fqlDz04xc@`cge@w z;yQJa2UCuCR+Q>K)IIK0G*(mqLqs%2vKKm;U~0k0bUDKE7bdS{eGW*(W6R;1D2;t2 z))|tI?Dqjc-4vWZEl-YaEZ$nGv)-WktaWb;^t2T0d&Ebr}0{CG2mAJ55zz`E`ijh=|4ptI|# znbl%8tM*Q%7mvG~vwRq9#c24zz}GX*CX1kx!ukh(K_I+p_-Q|H0X5Amoke0eJ?tdc ziC`|klhe0??V8$v;=S=aspXUr^3(>p2iZa!9E&ICXF`W$bvU+zs`IPIe%wAb@4ma! zjJYFHP^0t>_9M`ky`f@z1yCp_0nabQ`eoOrnaDZg-ZU#)CKvRRAnRXK4|O$kREPf4lVm zkrWDlQS(XHv5bvYu^a59Pw_lvn-ieMziNgl{E(VU#ZvL3{(gfl!sd76vV_fnfd935 zZ{lApc-8wC(yo+x+zMw!YJWHTDP#VMG(Wfhu~%4I!kct=^pEk*|lsuJDnBJpwBNVv5dz#m*{Yo;o`^OlSTv% z7tp&B_^-G2m3Y{(ra5%XTS*Xh$(UM!1(t=1>vrF7T_$Hdui(8WhejYsck`o^o~=BI Rl7GA7|8IYF4-Ruj{u}7_vlRdU literal 0 HcmV?d00001 diff --git a/src/drafts/XXXX-who-control/index.org b/src/drafts/XXXX-who-control/index.org new file mode 100644 index 0000000..99a04c5 --- /dev/null +++ b/src/drafts/XXXX-who-control/index.org @@ -0,0 +1,233 @@ +#+Title: Who is in Control +#+Subtitle: How I started to take care of the tools I use. +#+Author: Yann Esposito +#+Email: yann@esposito.host +#+Date: [2019-08-17 Sat 20:00] +#+KEYWORDS: opinion +#+DESCRIPTION: Modern tools disapears +#+DESCRIPTION: I include applications, web applications, websites, editors, programming languages. +#+LANGUAGE: en +#+LANG: en +#+OPTIONS: H:5 auto-id:t +#+STARTUP: showeverything + +#+begin_notes +This post is a reaction about a few articles I read in a short amount of time. +So do not take that too seriously. +But it will certainly. +#+end_notes + +I had to work a lot this week and I mostly didn't read any news. +This morning, I started to read the article I missed. +Here are the articles and threads I read: + +- [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] +- [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]] +- [[https://news.ycombinator.com/item?id=23092904][Github Codespace]] + +I don't think I read those in that order. + +A few years back, HN comments made me look at Clojure. +That was also many positive HN return of experience that made me confident +to use it for a serious business work. +Lot of great advices regarding every aspect of the life and software programming. +Project architecture, etc... +Most of the time, article were good, but HN comment were really great. +Of course, even after a few years, people started to explain that HN +quality dropped. +This can totally be an observer bias. +HN quality might not have really droped but the reader has changed. + +So I get it. +I changed a lot accross those years. +And also, yes, HN is mostly see by startupers. +So this is also another big bias. + +Still, I'm sad to see that the most popular opinions expressed in those +discussion threads have diverged so much from my point of view. + +When I see those news I see a common pattern. + +One big corp kill a product that should exist for the common good. +And of course, each time this is because having a common product is +incredibly hard. +Most "common good" products do not have what it takes to be sustainable +enough. +Either you create a very big open-source ness of developers that give their +work freely, or you can grab enough money from different source so you can +pay a few of them. + +And this is why the startup model is a lot more efficient. +You want a great product, buy the best best people. +For that you need money and passion. + +Most /Free Software/[fn:1] must deal with community driven development. +They should often find a concenssus. +They generally don't have money to pay the people working on that product. +While startup looking to create popular product must take a lot of care +about UX and UI. +What that mean is that the product should need the least possible amount of +energy and learning from the users. +And this is a great thing. +The problem with this approach is that most of the time it also forces +users to follow the workflow and limitations imposed to make it easy to use. + +And sometime worse, product simply disapears or change so much I simply +didn't want to use them anymore. + +So here is a non-exhaustive list of ~/.*ware/~ that, as a user you don't +want to deal with: + +- /bloatware/: remember digg, readitlater, stumbleupon? +- /downgradeware/: Swagger-UI v3 (v2 is neat), reddit new redesign (looks better, but slow) +- /payware/: You rely on our feature, but now, we want you to move or to pay. Fair ;) +- /crapware/: Nothing works as expected unless you pay: Twitter streaming API? +- /dieware/: Remember Friendfeed? Google Reader™? +- etc... + +Regarding the integration of VSCode™ inside GitHub™ I think this is even worse. +This is what I would call a /trapware/. + +#+begin_notes +/trapware/: +A software that is intented 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. +#+end_notes + +Furthermore, the fact that Microsoft is involved really give this situation a taste of [[https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish][EEE]]. + +So what is the real concern for me. +I imagine a new working environment where surveillance and control on the +developer is a rule. + +For a startup CTO/CEO this GitHub™ full work environment offers the +following advantages: + +- /security/: impossible or very hard to steal the code by a single dev. +- /homogeneity/: all dev must use the same development environment. Thus + the integration of new dev is faster. +- /cheaper/: don't need to pay for a full featured, fast machine to each new developer. + A simple machine able to display an electron app will do the trick. +- /stats/: you can observe the throughput of your developers. How many + commits a day, how many lines of code, etc... + How much bugs involved which part of the code and thus which dev to blame? + How much time the dev is typing, moving its mouse, how much copy/paste is + involved, etc... + +For the single developers and open source developers this offer: + +- /homogeneity/: if I learn how to work in this environment, I'll be easier + to recruit and I'll know how to work fast. +- /lower barrier to entry/: for an opensource repository, it will become much + easier for anyone to propose a PR to fix some issue. No need to local + clone the project, no need to download all the dependencies to test it + locally, etc... + +But the price to pay is hidden. + +1. First, you are now, not able to choose your local working environment on your machine. +2. GitHub™ can still change so much to become one of the previously mentionned ~/.*ware/~ you + don't want to be involved with. + Like forces you to pay a lot more, remove features, start to become a + bloatware, make it harder to interop with other platforms (prefer Azure + to AWS etc...). +3. If everything involve machines in the cloud via the browser, + it makes it harder to play locally with your machine. +4. Sureveillance on meaningless or wrong metrics about your work. + Instead of being evaluated on the feature you shipped or on other higher + level metrics. It will be very tempting for your bosses to find flaws in + your working habits. + We are already living in a world were surveillance, metrics and stats + are too easy to grab about a person. And anyone involved know this is + all bullshit. + Human are very good to play those kind of games. + So people really working hard for the best will certainly perform badly + compared to other people that simply trick the system. + +So if the endgoal of GitHub™ is really to help open source and single +developer. +And more generally provide simply a better working experience by adding a +new tool without any hidden marketing plan. +Yes great. But I really doubt a company offer anything without a plan to +make it worth it. + +Until here I mostly talked about the Github Codespace article and HN thread reaction. +Where I saw a lot too much enthusiasm about this news for my taste. + +But the other articles and their reaction in HN show that yes, HN might not +be for me anymore. +Most of the top level comment in [[https://news.ycombinator.com/item?id=23092657][Name one idea that changed your life]] +are about how to not fall for the trap of the [[https://nesslabs.com/confirmation-bias][confirmation bias]]. +That's really great. +But as a former scientist, this is only the very first step. +I might be totally wrong. +But I would have expected that the same question being answered a few years +back on HN would have also provided those answers but also deeper ones. + +The [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] is just again a confirmation that, yes. +When you chose to adopt a tool. +You should ask yourself if it is worth to invest your time and energy in it. +Because most of the time, the tool has a finite and short lifetime. + +Finally, about [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]]. +The first comment was about how VSCode is easy to start with as compared to +Emacs that need a lot more time to configure correctly for your needs. +Yes, VSCode certainly just work and is easy to use. +But Emacs is another beast. +VSCode can become bad very fast, you don't control how it will evolve. +Emacs on the other hand is 44 year old and was designed so that it adapts to you. +You are the one using libs and customizing. + +It's a bit of the same Frameworks vs Libraries argument. +Framework are easier to start with, but soon you find corner cases were you +cannot use them correctly and are fighting agains the framework. + +A Library on the other hand, is just a bunch of helpers you can use. +And if you need another functionality, just make it using the libraries. + +So libraries, programming languages and tools have generally subject to the +same debate. +- Easy now, but more difficult later VS harder now but easier in the future. + +So if you are going to need a "solution" for a problem for a very small +amount of time. The "Framework/3rd party tool/etc..." is certainly the best +solution to choose. +If you're going to make a living with it, and pass most of your time with +this tool. I highly suggest the second option. + +Emacs is like that. +Hard to start, but with emacs come a huge power that you will probably +never be able to get with any other IDE/Editor. +And above this, choosing a Free Software gives you a lot more control about +its evolution. + +I wouldn't be surprised if in a few years VSCode started to show ads during +startup ad why not in the middle of your work. +On the other hand this will never occurs within Emacs unless you are doing +this to yourself :). + +[fn:1] note I said /free software/ and not /open source/; c.f [[https://www.gnu.org/philosophy/open-source-misses-the-point.en.html][Why Open Source misses the point of Free Software]] + +* Conclusion +:PROPERTIES: +:CUSTOM_ID: conclusion +:END: + +Choosing a tool: + +- will I use it a lot? +- do I trust that I'll use the same tool in 5 years, 10 years? +- who is in control? +- Is it worth to invest my time in it? + +Most of these new tools from startup disapears after about 5 years. +So if you plan on using a tool for something important for you. +Take care that it will exists as it is today, or even better in a few years. + +* PLAN :noexport: +:PROPERTIES: +:CUSTOM_ID: plan +:END: +- common point, modern tools deprecates and disapear. +- how to chose a good tool From b720452dbcbe96d44b0d9b860da62ef5866e96d2 Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Sat, 9 May 2020 00:20:44 +0200 Subject: [PATCH 3/4] update --- shell.nix | 2 + src/drafts/XXXX-who-control/index.org | 244 +++++++++++--------------- 2 files changed, 101 insertions(+), 145 deletions(-) diff --git a/shell.nix b/shell.nix index 57a9006..fad7781 100644 --- a/shell.nix +++ b/shell.nix @@ -1,5 +1,7 @@ # { pkgs ? import {} }: { pkgs ? import (fetchTarball https://github.com/NixOS/nixpkgs/archive/19.09.tar.gz) {} }: + let my_aspell = pkgs.aspellWithDicts(p: with p; [en fr]); + in pkgs.mkShell { buildInputs = [ pkgs.coreutils pkgs.html-xml-utils diff --git a/src/drafts/XXXX-who-control/index.org b/src/drafts/XXXX-who-control/index.org index 99a04c5..2a4dd10 100644 --- a/src/drafts/XXXX-who-control/index.org +++ b/src/drafts/XXXX-who-control/index.org @@ -4,88 +4,47 @@ #+Email: yann@esposito.host #+Date: [2019-08-17 Sat 20:00] #+KEYWORDS: opinion -#+DESCRIPTION: Modern tools disapears -#+DESCRIPTION: I include applications, web applications, websites, editors, programming languages. +#+DESCRIPTION: Modern tools disapears. +#+DESCRIPTION: Some tools are worth a big time investment. #+LANGUAGE: en #+LANG: en #+OPTIONS: H:5 auto-id:t #+STARTUP: showeverything -#+begin_notes -This post is a reaction about a few articles I read in a short amount of time. -So do not take that too seriously. -But it will certainly. -#+end_notes - -I had to work a lot this week and I mostly didn't read any news. -This morning, I started to read the article I missed. -Here are the articles and threads I read: +This week I worked a lot more than usual. +So much I didnt take the time to take a look at HN. +So during my morning in the week-end, I started to read what I missed. +And here are a few articles I read along their comments: - [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] - [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]] - [[https://news.ycombinator.com/item?id=23092904][Github Codespace]] -I don't think I read those in that order. +Such article have existed for years on different products. +What is their common point? +/Software tooling and their potential change and disparition/. -A few years back, HN comments made me look at Clojure. -That was also many positive HN return of experience that made me confident -to use it for a serious business work. -Lot of great advices regarding every aspect of the life and software programming. -Project architecture, etc... -Most of the time, article were good, but HN comment were really great. -Of course, even after a few years, people started to explain that HN -quality dropped. -This can totally be an observer bias. -HN quality might not have really droped but the reader has changed. +Accross the years, to many times I saw tools I used disapearing from my +environment. +By tool it could be: applications, web applications, web sites, I think we +can also include programming languages, control versionning tools, building +tools, package manager, etc... -So I get it. -I changed a lot accross those years. -And also, yes, HN is mostly see by startupers. -So this is also another big bias. +The story can be quite different. +Sometimes the disparition of a tool is positive, because I found a better +one (for me at least). +But too often the tool simply disapears or worse downgrade its quality. +I think we can find different names for those softwares: -Still, I'm sad to see that the most popular opinions expressed in those -discussion threads have diverged so much from my point of view. - -When I see those news I see a common pattern. - -One big corp kill a product that should exist for the common good. -And of course, each time this is because having a common product is -incredibly hard. -Most "common good" products do not have what it takes to be sustainable -enough. -Either you create a very big open-source ness of developers that give their -work freely, or you can grab enough money from different source so you can -pay a few of them. - -And this is why the startup model is a lot more efficient. -You want a great product, buy the best best people. -For that you need money and passion. - -Most /Free Software/[fn:1] must deal with community driven development. -They should often find a concenssus. -They generally don't have money to pay the people working on that product. -While startup looking to create popular product must take a lot of care -about UX and UI. -What that mean is that the product should need the least possible amount of -energy and learning from the users. -And this is a great thing. -The problem with this approach is that most of the time it also forces -users to follow the workflow and limitations imposed to make it easy to use. - -And sometime worse, product simply disapears or change so much I simply -didn't want to use them anymore. - -So here is a non-exhaustive list of ~/.*ware/~ that, as a user you don't -want to deal with: - -- /bloatware/: remember digg, readitlater, stumbleupon? +- /bloatware/: remember digg, stumbleupon, windows? - /downgradeware/: Swagger-UI v3 (v2 is neat), reddit new redesign (looks better, but slow) -- /payware/: You rely on our feature, but now, we want you to move or to pay. Fair ;) -- /crapware/: Nothing works as expected unless you pay: Twitter streaming API? -- /dieware/: Remember Friendfeed? Google Reader™? +- /payware/: Useful free service ask for money now. Or cost a lot more. +- /crapware/: Stop to works, quality degrate unless you pay: Twitter streaming API? +- /dieware/: Remember Friendfeed, Google Reader™, etc... - etc... -Regarding the integration of VSCode™ inside GitHub™ I think this is even worse. +So regarding Github Codespace; the integration of VSCode™ inside GitHub™ I +think this could be worse than a disapearing tool. This is what I would call a /trapware/. #+begin_notes @@ -95,22 +54,23 @@ By slowly but surely add features that while looking great for the user at first sight will ensure to entrave other tools to interoperate. #+end_notes -Furthermore, the fact that Microsoft is involved really give this situation a taste of [[https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish][EEE]]. +Furthermore, the fact that Microsoft is involved has a taste of [[https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish][Embrace, Extend and Extinguish]]. -So what is the real concern for me. -I imagine a new working environment where surveillance and control on the -developer is a rule. +I think the real concern is that it could become a /work framework/. +So if sufficiently businesses start to use this. +This could impose the full tooling on a lot of developers without giving them +the freedom of choice. -For a startup CTO/CEO this GitHub™ full work environment offers the -following advantages: +For a startup CTO/CEO this GitHub™ Codespace™ could offer the following +advantages: -- /security/: impossible or very hard to steal the code by a single dev. +- /security/: impossible or very hard to steal the source code by a single dev. - /homogeneity/: all dev must use the same development environment. Thus the integration of new dev is faster. - /cheaper/: don't need to pay for a full featured, fast machine to each new developer. - A simple machine able to display an electron app will do the trick. -- /stats/: you can observe the throughput of your developers. How many - commits a day, how many lines of code, etc... + A less performant machine able to display an electron app will do the trick. +- /stats/: you can observe the throughput of your developers. + How many commits a day, how many lines of code, etc... How much bugs involved which part of the code and thus which dev to blame? How much time the dev is typing, moving its mouse, how much copy/paste is involved, etc... @@ -126,15 +86,17 @@ For the single developers and open source developers this offer: But the price to pay is hidden. -1. First, you are now, not able to choose your local working environment on your machine. -2. GitHub™ can still change so much to become one of the previously mentionned ~/.*ware/~ you - don't want to be involved with. - Like forces you to pay a lot more, remove features, start to become a +1. First, you are now, not able to choose your local working environment on + your machine. +2. GitHub™ can still change so much to become one of the previously + mentionned ~/.*ware/~ you don't want to be involved with. + They could forces you to pay a lot more, remove features, redesign to a bloatware, make it harder to interop with other platforms (prefer Azure to AWS etc...). -3. If everything involve machines in the cloud via the browser, - it makes it harder to play locally with your machine. -4. Sureveillance on meaningless or wrong metrics about your work. +3. If everything involve machines in the cloud via the browser and via + authorized plugins only. A lot of tools, features will never be allowed + in this new ecosystem. +4. Surveillance on meaningless or wrong metrics about your work. Instead of being evaluated on the feature you shipped or on other higher level metrics. It will be very tempting for your bosses to find flaws in your working habits. @@ -149,85 +111,77 @@ So if the endgoal of GitHub™ is really to help open source and single developer. And more generally provide simply a better working experience by adding a new tool without any hidden marketing plan. -Yes great. But I really doubt a company offer anything without a plan to -make it worth it. +Yes great. +But I really doubt a company like Microsoft™ offer anything without a plan +to make it worth it. -Until here I mostly talked about the Github Codespace article and HN thread reaction. +Until here I mostly talked about the Github Codespace article and HN thread +reaction. Where I saw a lot too much enthusiasm about this news for my taste. -But the other articles and their reaction in HN show that yes, HN might not -be for me anymore. -Most of the top level comment in [[https://news.ycombinator.com/item?id=23092657][Name one idea that changed your life]] -are about how to not fall for the trap of the [[https://nesslabs.com/confirmation-bias][confirmation bias]]. -That's really great. -But as a former scientist, this is only the very first step. -I might be totally wrong. -But I would have expected that the same question being answered a few years -back on HN would have also provided those answers but also deeper ones. +The [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] is just another story of a dying product. +Apparently the keybase team will probably stop maintaining keybase. +The idea behind keybase was pretty nice. +And they filled a gap in the current open source world. -The [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] is just again a confirmation that, yes. -When you chose to adopt a tool. -You should ask yourself if it is worth to invest your time and energy in it. -Because most of the time, the tool has a finite and short lifetime. - -Finally, about [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]]. -The first comment was about how VSCode is easy to start with as compared to -Emacs that need a lot more time to configure correctly for your needs. +The last article I mentionned was [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]]. +The first comment in HN was about how VSCode is easy to start with as +compared to Emacs that need a lot more time to configure correctly for your +needs. Yes, VSCode certainly just work and is easy to use. But Emacs is another beast. VSCode can become bad very fast, you don't control how it will evolve. -Emacs on the other hand is 44 year old and was designed so that it adapts to you. -You are the one using libs and customizing. +The fact that this is a succesful Microsoft product does not garanty it +will keep its currently quality. +Emacs on the other hand is 44 year old and was designed so that it adapts +to you. +You are the one using libs and customizing it. -It's a bit of the same Frameworks vs Libraries argument. -Framework are easier to start with, but soon you find corner cases were you -cannot use them correctly and are fighting agains the framework. +The argument to chose VSCode instead of Emacs look similar to me to the +debate "Frameworks vs Libraries". +Frameworks are easier to start with, but soon you find corner cases were +you start to fight against them. A Library on the other hand, is just a bunch of helpers you can use. And if you need another functionality, just make it using the libraries. +But you have a lot more work to do yourself. -So libraries, programming languages and tools have generally subject to the -same debate. -- Easy now, but more difficult later VS harder now but easier in the future. +The common pattern I see during choice decision is often reducible to: -So if you are going to need a "solution" for a problem for a very small -amount of time. The "Framework/3rd party tool/etc..." is certainly the best -solution to choose. -If you're going to make a living with it, and pass most of your time with -this tool. I highly suggest the second option. +1. Easy now, but less extensible and more difficult later +2. Harder now but more extensible and less potential blocker in the future. -Emacs is like that. -Hard to start, but with emacs come a huge power that you will probably -never be able to get with any other IDE/Editor. -And above this, choosing a Free Software gives you a lot more control about -its evolution. +And mostly the answer is not hard to infer. +If you are going to use a tool a lot, the difficulty to start learning it +is not that important. +If in the end the tool help you to go farther. -I wouldn't be surprised if in a few years VSCode started to show ads during -startup ad why not in the middle of your work. -On the other hand this will never occurs within Emacs unless you are doing -this to yourself :). +So if you're going to make a living with it. +And use this tool a lot I highly suggest the second option. -[fn:1] note I said /free software/ and not /open source/; c.f [[https://www.gnu.org/philosophy/open-source-misses-the-point.en.html][Why Open Source misses the point of Free Software]] +I consider Emacs to be of the 2nd option when compared to VSCode. +Harder to start, but with a lot more control and potential power that you +will probably never be able to get with most modern IDE/Editor. +Also choosing a Free Software[fn:1] gives you a lot more control about its +future. -* Conclusion -:PROPERTIES: -:CUSTOM_ID: conclusion -:END: +A few last words about Emacs, because for now I can state that this is an +amazing tool which when used correctly will improve your coding experience +and project management a lot. -Choosing a tool: +If you want to start using it from something like VSCode I suggest you to +start by using either [[https://www.spacemacs.org][spacemacs]] or [[https://github.com/hlissner/doom-emacs][doom-emacs]]. +It will take a few weeks to absorb vim keybindings. +Slowly you'll start to learn how to configure it for your needs. +And I really suggest you to take a look at org-mode. +Mastering it could change your carrier. +org-mode alone would be enough to use emacs. +But there are a lot more to discover. -- will I use it a lot? -- do I trust that I'll use the same tool in 5 years, 10 years? -- who is in control? -- Is it worth to invest my time in it? +The first difficult aspect when faced with open source is the lack of +centralization. +Instead of having a big bundle with everything prepared to work you +generally need to install each part of a big system separately. -Most of these new tools from startup disapears after about 5 years. -So if you plan on using a tool for something important for you. -Take care that it will exists as it is today, or even better in a few years. - -* PLAN :noexport: -:PROPERTIES: -:CUSTOM_ID: plan -:END: -- common point, modern tools deprecates and disapear. -- how to chose a good tool +[fn:1] note I said /free software/ and not /open source/; c.f + [[https://www.gnu.org/philosophy/open-source-misses-the-point.en.html][Why Open Source misses the point of Free Software]] From cdcb7a5a55a120ca8d2388b56276d92ed8d0ae6d Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Sat, 9 May 2020 12:15:46 +0200 Subject: [PATCH 4/4] Renamed --- .../index.org | 166 ++++++++++++------ 1 file changed, 112 insertions(+), 54 deletions(-) rename src/drafts/{XXXX-who-control => XXXX-how-to-choose-your-tools}/index.org (58%) diff --git a/src/drafts/XXXX-who-control/index.org b/src/drafts/XXXX-how-to-choose-your-tools/index.org similarity index 58% rename from src/drafts/XXXX-who-control/index.org rename to src/drafts/XXXX-how-to-choose-your-tools/index.org index 2a4dd10..ef634be 100644 --- a/src/drafts/XXXX-who-control/index.org +++ b/src/drafts/XXXX-how-to-choose-your-tools/index.org @@ -1,39 +1,37 @@ -#+Title: Who is in Control -#+Subtitle: How I started to take care of the tools I use. +#+Title: How to choose your tools #+Author: Yann Esposito #+Email: yann@esposito.host #+Date: [2019-08-17 Sat 20:00] #+KEYWORDS: opinion -#+DESCRIPTION: Modern tools disapears. -#+DESCRIPTION: Some tools are worth a big time investment. +#+DESCRIPTION: Modern tools tend to disapears. +#+DESCRIPTION: An app on the web will change, and could break for the worst. +#+DESCRIPTION: Quite often investing in long living tools which are harder start +#+DESCRIPTION: with will be worth the investment. #+LANGUAGE: en #+LANG: en #+OPTIONS: H:5 auto-id:t #+STARTUP: showeverything -This week I worked a lot more than usual. -So much I didnt take the time to take a look at HN. -So during my morning in the week-end, I started to read what I missed. -And here are a few articles I read along their comments: +This week I didn't take a look at HN to grab some news. +And this week-end, in the morning I read those: - [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] - [[https://news.ycombinator.com/item?id=23107123][Making Emacs popular again]] - [[https://news.ycombinator.com/item?id=23092904][Github Codespace]] -Such article have existed for years on different products. +Similar articles have existed for years on different products. What is their common point? /Software tooling and their potential change and disparition/. -Accross the years, to many times I saw tools I used disapearing from my -environment. -By tool it could be: applications, web applications, web sites, I think we -can also include programming languages, control versionning tools, building -tools, package manager, etc... +Accross the years, too many times I saw tools disapear. +By tools I mean applications, web applications, web sites. +I think we can also include programming languages, control versionning +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 -one (for me at least). -But too often the tool simply disapears or worse downgrade its quality. +one (from cvs to svn to git). +But, too often, the tool simply disapears or worse downgrade its quality. I think we can find different names for those softwares: - /bloatware/: remember digg, stumbleupon, windows? @@ -43,8 +41,11 @@ I think we can find different names for those softwares: - /dieware/: Remember Friendfeed, Google Reader™, etc... - etc... -So regarding Github Codespace; the integration of VSCode™ inside GitHub™ I -think this could be worse than a disapearing tool. +This is often quite frustrating because you lose a lot of your investment +with that tool. + +Regarding Github Codespace; the integration of VSCode™ inside GitHub™ can +be even worse. This is what I would call a /trapware/. #+begin_notes @@ -54,12 +55,12 @@ By slowly but surely add features that while looking great for the user at first sight will ensure to entrave other tools to interoperate. #+end_notes -Furthermore, the fact that Microsoft is involved has a taste of [[https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish][Embrace, Extend and Extinguish]]. +Furthermore, the fact that Microsoft is involved give this story a taste of +[[https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish][Embrace, Extend and Extinguish]]. -I think the real concern is that it could become a /work framework/. -So if sufficiently businesses start to use this. -This could impose the full tooling on a lot of developers without giving them -the freedom of choice. +My real concern is that it could become a /work framework/. +This could impose the full tooling on a lot of developers without giving +them the freedom of choice. For a startup CTO/CEO this GitHub™ Codespace™ could offer the following advantages: @@ -115,10 +116,6 @@ Yes great. But I really doubt a company like Microsoft™ offer anything without a plan to make it worth it. -Until here I mostly talked about the Github Codespace article and HN thread -reaction. -Where I saw a lot too much enthusiasm about this news for my taste. - The [[https://news.ycombinator.com/item?id=23102430][Zoom acquires keybase]] is just another story of a dying product. Apparently the keybase team will probably stop maintaining keybase. The idea behind keybase was pretty nice. @@ -148,16 +145,17 @@ But you have a lot more work to do yourself. The common pattern I see during choice decision is often reducible to: -1. Easy now, but less extensible and more difficult later -2. Harder now but more extensible and less potential blocker in the future. +1. Easy now, but less extensible and harder in the long run. +2. Harder now, but more extensible and easier in the long run. -And mostly the answer is not hard to infer. -If you are going to use a tool a lot, the difficulty to start learning it -is not that important. -If in the end the tool help you to go farther. - -So if you're going to make a living with it. -And use this tool a lot I highly suggest the second option. +As a conclustion I would state that when you need to choose between +different tools. +Take the time to think about the investment costs. +Sometime, the bit of pain in the begining is worth it. +In particular if you are going to use this tool every days for many hours +during the following years. +If on the other hand you don't plan to use that tool much. +Going with the easy option is certainly the best choice. I consider Emacs to be of the 2nd option when compared to VSCode. Harder to start, but with a lot more control and potential power that you @@ -165,23 +163,83 @@ will probably never be able to get with most modern IDE/Editor. Also choosing a Free Software[fn:1] gives you a lot more control about its future. -A few last words about Emacs, because for now I can state that this is an -amazing tool which when used correctly will improve your coding experience -and project management a lot. - -If you want to start using it from something like VSCode I suggest you to -start by using either [[https://www.spacemacs.org][spacemacs]] or [[https://github.com/hlissner/doom-emacs][doom-emacs]]. -It will take a few weeks to absorb vim keybindings. -Slowly you'll start to learn how to configure it for your needs. -And I really suggest you to take a look at org-mode. -Mastering it could change your carrier. -org-mode alone would be enough to use emacs. -But there are a lot more to discover. - -The first difficult aspect when faced with open source is the lack of -centralization. -Instead of having a big bundle with everything prepared to work you -generally need to install each part of a big system separately. - [fn:1] note I said /free software/ and not /open source/; c.f [[https://www.gnu.org/philosophy/open-source-misses-the-point.en.html][Why Open Source misses the point of Free Software]] + +** Post-conclusion -- Emacs is awesome +:PROPERTIES: +:CUSTOM_ID: post-conclusion +:END: + +To go beyong my opinion, I'd like to share my experience with editors and +emacs. + +When I started to code. +We coded with vi, not vim, vi. +At that time I only knew, =i=, =a=, =dd= and =cw= vi commands. +So when I started to use IDEs I was thrilled. +After a few year I started to work for a company that forced me to use +their shitty computers. +I started to have wrist issues. +So I decided to learn vim. +And I saw the benefits only after a few weeks. +They were tremendous. +No more wrist pain. +And I started to learn a lot of editing automation. + +Then I started a new work where we decided to code in Clojure. +And so knowning that Clojure is a LISP and most LISPers love emacs because +emacs plugin language is emacs LISP. +I tried to use spacemacs. +At that time I didn't want to invest much time in learning Emacs. +I just wanted to learn the tricks that will make Emacs more valuable to my +work. +And it did after just a few days, weeks. +I used Emacs superficially for years. +Just Spacemacs + a few useful layers. +And it was already quite efficient, at least as much as vim. + +More recently I started to dig deeper. +In particular, I read so much praise about org-mode I was really curious. +And it took me some time to really discover why it is so great. +First, let's just say that, basic org-mode is already quite valuable. + +But you can do a lot. +And unfortunately this is a bit hard to describe how org-mode is great +without really digging a bit. + +So you can think of org-mode as an extremely versatile todo-list / note +taker with agenda and time tracking integration. +Mostly you are in control of your working workflow with org-mode. +The ability to do org-capture and org-refile is also great. +Recently there is org-roam that is a step further to make orgmode a nice +place to keep track of all your knowledge in one place. + +Concretely, emacs has changed my workflow a lot and made me a *lot* more +productive. +It improved not only my coding workflow, but my full work environment. +I started with the editor, a few plugins, and slowly, I integrated more +aspect of my day to day tasks in emacs. +Emacs is designed to adapt to your own needs you can start to automate a +lot of small tasks. + +I really love Emacs and if you want to joyfully join the Emacs users here +are my advices: + +Start by using either [[https://www.spacemacs.org][spacemacs]] or [[https://github.com/hlissner/doom-emacs][doom-emacs]]. +It will take a few weeks to absorb vim keybindings. +Slowly you'll start to learn how to configure it for your needs. + +I really advise you to take a look at org-mode. +Mastering it could change your carrier. +Im my opinion [[https://orgmode.org][org-mode]] alone is a good reason enough to use emacs. +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. +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. + +Howevery I'm deeply convinced the investment is really worth it.