Most browsers have a reading mode button in the URL bar. Apparently these sorts of fonts are actually easier for people with dyslexia to read. But I'm more interested in creating a unified visual aesthetic that says—this is not a scientific paper, read at your own leisure / risk.
I built a platform to monitor LLMs that are given complete freedom in the form of a Docker container bash REPL. Currently the models have been offline for some time because I'm upgrading from a single DELL to a TinyMiniMicro Proxmox cluster to run multiple small LLMs locally.
The bots don't do a lot of interesting stuff though, I plan to add the following functionalities:
- Instead of just resetting every 100 messages, I'm going to provide them with a rolling window of context.
- Instead of only allowing BASH commands, they will be able to also respond with reasoning messages, hopefully to make them a bit smarter.
- Give them a better docker container with more CLI tools such as curl and a working package manager.
If you're interested in seeing the developments, you can subscribe on the platform!
I created this website to follow along as LLMs are set free on docker containers. It's an interesting experiment, although not many useful commands are executed. It's striking how much stronger the o1-mini model is compared to the other ones, even with the delay handicap.
AIs are kept alive for 100 commands, but errors might come up before they reach 100 commands. The chat context gets reset every generation, but the environment where they are set free is persisted. So, every generation they build upon their last generation. Each bot is isolation from one-another, they do not share environments.
Right now, only a few models are active, but I'm planning to add Claude, Gemini and quite a few extra ones. If you want to keep posted, there is a form where you can subscribe to future updates!
I don't understand. When you work for a company, don't you also spend some time of your workday daydreaming, or getting a coffee, or doing some other thing that does not earn the company money?
That's nice and all, but isn't that a huge waste of time/money/resources? What is the advantage of doing it this way over just creating a wallpaper digitally?
With products like Windows, there's a chance that the desktop background, the startup chime and suchlike will end up as iconic as the Coca-Cola logo.
The designers would have told the CEO that this is going to be seen by 100x more people than a Superbowl ad spot, and 100x as many times per person too. So getting the perfect image/sound made for the cost of a single superbowl ad is a great deal.
Of course, whether they've succeeded at producing the perfect image is another matter.
The Windows 95 startup chime was composed by Brian Eno, so MS are used to paying for this stuff.
This kind of maximal efficiency attitude is precisely why programs aren't "fun" anymore. Oftentimes, taking the scenic route instead of the highway is how you awe and inspire people; I know I was.
If anyone reading this remembers the 90s and early 00s with Easter Eggs and other fun programs with character, y'all know what I'm talking about.
You clearly don't know what computing was like back when developers' passions were oozing out of pretty much everything they wrote. Even something as mundane as an icon left an impression.
These kinds of "Wait... Seriously? Wow!" stories play a big role in inspiring the next generation to come and do the work of the future. We're seeing far less of them now in computing, and everyone wonders why the younger generations aren't as inspired about technology anymore.
When everything is a brutal race to the bottom to fleece you for every damn bit you're worth, damn right everyone's going to find greener pastures to be inspired by.
You went of on some tangent about the 'old days of passionate software developers' which seems like something that just happened to be on your mind, not something with any connection here.
When you say 'we' should splurge you really mean someone else.
Also this wasn't a splurge, this probably took less time to make than doing it in CG and people who can do the photography probably don't know how to do it in CG in the first place.
In this case specifically it deals with light going through a pattern and into mist, which is going to have a lot light scattering inside an uneven volume. This still takes a lot of time to render and will be more difficult to match to a photograph than other things.
Advocates of Watson made by Karelia Software, LLC claim that Apple copied their product without permission, compensation, or attribution in producing Sherlock 3. Some disagree with this claim, stating that Sherlock 3 was the natural evolution of Sherlock 2, and that Watson was obviously meant to have some relation to Sherlock by its very name.
The phenomenon of Apple releasing a feature that supplants or obviates third-party software is so well known that being Sherlocked has become an accepted term used within the Mac and iOS developer community.
Usually something to do with running a tumblr full of Benedict Cumberbatch/Martin Freeman fanfic.
But in this case, it refers to the fact that there used to be a Mac app called Watson (made by Karelia Software) that let you search all your personal files. Then Apple added an OS feature called Sherlock that did the same thing and ripped the rug out from under the third party developer. (Sherlock has since been replaced by Spotlight in more recent MacOS versions)
By analogy, anyone making software in the Mac ecosystem (or any ecosystem really) risks being ‘Sherlocked’ by having their idea ripped off and turned into an OS feature.
Calling it ”sherlocked” is recency bias on our part. Apple learned it from Microsoft, who took a thing that happened from time to time and operationalized it into a full-blown business strategy.
One by one, Microsoft took aim at successful DOS and Windows applications, especially business applications, and displaced them. Lotus… WordPerfect… Everyone, really. Unless your app was for a niche too specialized to be worth the hassle, Microsoft wanted to use you for market research and then either buy you, buy your competitor, or clone you.
> Calling it ”sherlocked” is recency bias on our part.
It has been called “sherlocking” in the Mac sphere ever since the Sherlock 3 incident. Any bias is not on our part, as this was more than 20 years ago. Yes, some of us were there (I was, so maybe I share some responsibility), but the combination of the minuscule Mac market share at the time and its steady growth for the 2 following decades means that the people who were around at the time are a statistically insignificant fraction of us today.
It is not unique and in retrospect we can find many historical examples before that, but it was a particularly high-profile one, it made a lot of noise, and the name stuck. Also, most Mac users at this point avoided Windows (or eve worse, dog forbid, MS-DOS) like the plague so this would not have been in people’s minds.
When accused by Steve Jobs of ripping Apple’s technology and designs off, Bill Gates is said to have cooly replied:
"Well, Steve, I think there's more than one way of looking at it. I think it's more like we both had this rich neighbor named Xerox and I broke into his house to steal the TV set and found out that you had already stolen it."
I'm not so sure. Aren't we having a bit of negativity bias here, as we mostly hear about the negative events while there are probably countless successful integrations with cloud providers.
Look at all the banks shifting their infra to the cloud. Haven't heard anything bad happen from that. And their uptime and business requirements are as stringent as anyone else, even further scrutinized by regulators and auditors.
Yes, if you'd compare all horror stories of people having huge downtimes because their on-prem system collapsed vs. people having an issue with their cloud provider then we'd very quickly realise again why the cloud has taken us by storm.
If you extract this `Chain` class to a separate package, I would gladly reuse it in my applications. I've been thinking about creating a `Vavr`[0] clone in typescript, as I really like the syntax used in that library, especially the `Try` construct.
