It really was. I forgot to mention in my comment that the sun machines were also really cheap so, you know, capitalism.

Unfortunately, the lisp machine didn’t gain traction because the start-up times were so long and I believe this is due to it doing lots of internal checks which was awesome but unfortunately things like the Sun SPARCstation won because it was crazy fast although buggy

Yeah, fully agree. I was hoping the weights would be available by now as I’m keen to use it. Most of my use-cases for AI image generation end up being vectorised before I can use them

No worries, l definitely plan to use it in Docker, so I’ll give it a go and if I can I’ll submit PRs for anything I find

Oooh, I never considered doing this. I’ll check it out!

Nice, I’m currently looking for a good vectoriser model and it seems this will do that and other stuff nicely

D) spend millions developing an AI to generate the boilerplate generator badly

Yeah, I’d say Kitty and Alacritty work pretty well on Linux. Makes this comparison table seem like bs

“Do no evil (alone)”

I’m tempted to publish an NPM package to do so as a joke, but I fear that it’d get used seriously

However it should be noted that the remote development connection is via their servers, which makes it somewhat less useful

Ah ok, the name implies it’s a security guard

I love that you’re thinking about how to secure sensitive parts of JS applications, however I wonder what threat this is guarding against. Can you give an example? Surely if an attacker can modify the source to call the sensitive functions, then they could modify the allow list

Nice article! I’m a fan of the “don’t optimise early” mantra, which seems particularly relevant here regarding clone

I feel like this is a perfect encapsulation of how an experienced self-aware developer thinks. Experience really beats the hard stances out of you. I find myself saying “it depends” and “a bit of column A, bit of column B” often, like a cheap kids toy

His take strangely acknowledges that defects are caused by programmers, yet doesn’t want to improve the tools we use to help us not make these mistakes. In summary, git gud.

Experience has taught me that I’m awfully good at finding and firing foot guns, and when I use a language that has fewer foot guns along with good linting, I write reliable code because I tend to focus on what I want the code to do, not how to get there.

Declarative functional programming suits me down to the ground. OOP has been friendly to me, mostly, but it also has been the hardest to understand when I come back to it. Experience has given me an almost irrational aversion to side effects, and my simple mind considers class members as side effects

I guess a porch pirate isn’t gonna look in the bin, and if they did, it does look like recycling

So I guess that’s something?

Yeah, this is my colleagues waiting for me, poor bastards

I recommend LunarVim for VS Code users too

I’m thinking evaporative cooling (paired with refrigerative cooling)