'wade in the water.' isn't this the challenge of being 'ahead'? so many of us are waist deep in the same sea, it's hard to see what's in front of us vs. what's behind us. then we see the yacht boys sail by with their new masters, splashing us in their wake. then we grumble amongs
Any conversation
kรฉsztetรฉst รฉrzek, hogy valami ilyesmivel (is) foglalkozzam, a kรณdolรกshoz egyelลre nincs agyam, de majd azt is szeretnรฉk, csak scripteket, semmi komoly programnyelv, de vรฉgรผlis a JavaScript is scriptnyelv
I feel the urge to do something like this, I don't have the brains for coding yet, but I would like to, just scripts, no serious programming languages, but after all, JavaScript is also a scripting language
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
โฆ
I think a trusted piece of software such as your operating system should be in charge of managing permissions. For example, I believe with Wayland on gnome you no longer need to promise you aren't secretly taking screenshots of the whole monitor and shipping it somewhere because to do that Wayland requires you to get user permission.
You would not download a car...
You would not upload a collection and ask the user to log in now...
Send api requests 1998 style.. lightweight and without tracking
github.com/alainnothere/mailBoy
news.ycombinator.com/item?id=50359814
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
spiral
for(y=-5;y<5;y++){
s=""
for(x=-10;x<10;x++){
r=Math.hypot(x/2,y);a=Math.atan2(y,x/2);s+=" .:*#โ"[((r+a*2)%5+5)%5|0]
}
console.log(s)
}::.........:::***##
.. ...::**##
######## ..::**#
###********# ..::*#
#**:::...::*# ..:**#
. ##**::. ..::**##
##**:.. #*::***##
##**:.. ######
. ##**::... ...
. ##***:::......:::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.


