Theory reuse > code reuse almost every time.
Any conversation
I truly love the experience of using apps with rich, deeply interactive, beautifully animated, gorgeous user interfaces.
Then I see a beautiful text-based interface and something about it feels so natural, so inevitable, so perfectly clear, and I'm instantly captivated by its simplicity and clarity.
Hypertext is fascinating.
ive been rocking my thinkpad 460s since 2018 or so, but ive just recently yolo purchased a chunky t420 for 80โฌ. I gotta say this is the best laptop ive ever used, keyboard/io is unmatched and it still runs super snappy on omarchy right now, even with only 4 gigs of ram :D AND this thing has a cd drive!
๐
let N=6,D0=[0,1,0,-1],D1=[1,0,-1,0],s=[],g={},d=x=y=xa=xb=ya=yb=0;
for(let n=0;n<N;n++){s=s.concat([1]).concat(s.map(x=>!x).reverse())}
for(let i=0;i<s.length;i++) {
x<xa && (xa=x);y<ya && (ya=y);x>xb && (xb=x);y>yb && (yb=y);
let t=s[i]?1:-1,e=(d+t+4)%4;
g[x]||(g[x]={});
g[x][y]=g[x][y]?"โผ":"โโโโ"[(t*(D0[d]+D0[e])>0?0:2)+(t*(D1[d]+D1[e])>0?0:1)];
x+=D0[e];y+=D1[e];d=e;
}
for(j=yb;j>=ya;j--) {
let u=""; for(i=xa;i<=xb;i++){u+=(g[i][j]||"ยท")} console.log(u);
}ยทโโโโยทยทยทยทยทยทยท
โโโโผโยทยทยทยทโโยท
โยทยทโโโโยทยทยทโโ
ยทยทยทโโผโผโยทยทยทโโ
ยทยทยทโโผโผโโโโโผโ
ยทยทยทโโผโโโผโผโโโ
ยทยทยทโโผโยทโโผโยทยท
ยทยทยทยทโโยทยทโโยทยทI'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing
130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later. signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake

