Note it says, "As always, it is best to avoid cloning repositories from untrusted sources."
Now consider how many languages will clone a repo of a transitive dependency, or direct dependency at time of dep resolution -- often before any dep analysis/presentation tools could give you a means to evaluate the transitive git deps.
Like #clojure, one of my favorites. I have not review dep resolution/fetch code in other languages, but it seems that they should all heed the advice in that advisory.
My world was built by men and women sharing their labor and their art, not by capital, which came along later and tried to steal the work and take credit for it.
@craigbro Isn't that a very naive view? IMHO work, art and capital work together. They are not antagonists. The worker needs money to eat and life, the artist too. And work or capital without art is dull. And capital usually is accumulated from work (directly but too often indirectly). It's like end endles band between those three.
If you look at great buildings today, may they come from ancient Egypt, Greece, Rome, from medieval times or later ... without capital most of them wouldn't have been completed. They are actually an indication for historians of developed a society was.
Former socialist east european countries were capital starved. And that did generally not lead to better housing, infrastructure buildings, modern and efficient production facilities etc. They had some lighthouse projects, true. But a lot was missing, a lot was derelict. You clearly could seethe role of capital there, since it was missing.
And if you look at how expensive it is today to build e.g. a school, you see that work and art alone would stay hungry and dumb. They alone wouldn't build the school.
So an attempt to play out capital against work and art doesn't seem to be based on historic examples. Or on current circumstances.
@holgerschurig no, it's not naive. It is based on a strong definition of capital, which is a specific form of economics. You don't seem to share that model, confusing capitalism with all of the economic systems of the past, capital with property and/or money.
Over the last decade, I had to adopt several "modern" professional tools, pulling me out of the #Emacs bubble I had built up over the first 3/4 of my career. Graphical Email, modern browsers, video conferencing, Slack, Outlook, Calendaring and Jira. My return to #Emacs in #tmux on my #OpenBSD server, my happy place, has been eye-opening.
I still have a bailout for interacting with modern shit, and my work laptop is still MacOs. I am still cursed with Slack and Jira and Chrome for work. But now that I have my safe space back, I don't find myself as frustrated during the day when I have to use the modern sub-standard tools. It's saving me some stress budget for sure.
@craigbro I'm kind of oscillating towards a similar setup. Although I have a hard time giving up my macOS M1 (yet), I find it increasingly frustrating that I miss out on so many great tools that are not yet or never will be available on the Apple platform. Also, I think that Apple has no interest in improving on macOS any further for power users and keep the OS as open as possible. Maintainers of FOSS tools have a hard time keeping up with the increasing artificial restriction that Apple is putting on them and I understand why they just abandon the platform.
Which makes me switch between my Thinkpad X1 on Linux Mint and the Mac all the time - and keeping my setups in sync costs more time than I want to spend.
So now I've set up a remote #OpenBSD server and installed all the toolchains I need for development (which is essentially just Git, Emacs, Go, SBCL, npm and OpenJDK). With tailscale it is super easy to keep everything connected to the various services I run.
But something is kind of holding me back to fully commit, not sure what or why. The all-new Emojis and iMessage features that Apple is selling as the next "major release" are not it, that's for sure.
@louis Heh, sounds like we are on a similiar trajectory. I am considering a X1, but first I'm going to take a crack at dual boot #OpenBSD on the M1 Air.
I'm already compiling a list of tasks for that, starting at gettting my #Rustlang pwget util able to handle write operations on pwsafeV3 DBs, then figuring out why #tmux is munging lined with wide utf-8 characters, and then on to whatever drivers I'll need to touch up to get the M1 usable as a daily driver (if any?).
Decided that I'll limit several sources of content, youtube, patreon, podcasts to my phone or AppleTV for now, makes it an easier leap. The M1 will always be dual boot.
To keep my setups in sync, I previously used #nix. I had a single flake that would produce nix-darwin or nixos systems and home-manager modules. That required gigs of disk space, and the declarative power came with several layers of abstraction to learn and debug.
All of this leads me to unwinding a decade of Apple patronage. My mind if just calmer, my soul happier, with text and a ps auxww where I know every process, and have read large parts of it's code and man pages in the last couple decades.
It all let's me focus on the "problem domain" that interests me most -- connecting with humans, collaborating, and mutating our brains together.
My parting shot, err, question. What is it holding you back? And what if you didn't have to make some clean break, or declare some purity, but just make it a game, an experiment, an art project?
As a birthday present to myself, I'm installing #OpenBSD on my m1 air and an intel nuc.
I enjoyed my #nix based environment that was portable across my #nixos server and my #MacOS laptops (work and personal). It works well, will keep using it for the work laptop. For my professional work, it's still the best solution I've found and brings amazing wins.
But it doesn't bring me happiness, or make me feel calm. I got that for years from my #OpenBSD workstations. All the code, all the manual, secure, conservative change, an rc init, and a handful of processes.
A little more than a year ago, i joined emacs.ch along with others leaving Twitter. I had tried mastodon before, but bounced off it. I was intrigued by the protocol, but protocols and platforms are not the real draw. It’s the people, not by volume, but the sufficient intersection of interests and practiced art of sharing, commenting and discussion.
The choice of mastodon instance matters to me, because the #emacs community, and its size fit my needs and has a great overlap with the other topics i am interested in, #lisp, #nix and #clojure
Decades ago i got interested in computers because they let me talk to people from all over the place, getting diverse input.. Johnny 5 Alive!
As the AP network grows, we need to remember that its people that build it, run its nodes, interact with us, and share bits of their humanity to make this social network. They are not “users” to count, or to sell or to analyze. Our conversations are not “content” for monetizing, or decorating with ads, or manipulating to drive impressions and clicks. The people running it are not our servants, or our overlords to fight.
The AP network will grow, maybe beyond its own capabilities, and some set of people may be diverted into attention monetization machines, but the social ties can migrate, with help from the tools or simply thru memory and rediscover.
Remember the people, not the followers or likes or boosts, and help each other build, run and use the tools, free software, to control our experience and keep one another at the core of it.
When you program professionally, it can be hard to approach it as a purely creative and playful activity. What started as a fun and rewarding project turns into a disenchanting slog once my brain starts telling me I have to "do it properly".