All-in, I wanted something on the order of 1MB for client app, server, all dependencies, everything.
Okay that's gotta be radically different!
I was thinking along the same lines but then I thought about other neighbouring countries like Lebanon. Being recognized states didn't stop Israel from doing whay they did to them. Not saying there's no difference, I'm just not sure what the practical difference is. I'm probably ignorant.
Some hopium here.
Actively dismantling international law, I see.
Well, you gotta start it somehow. You could rely on compose'es built-in service management which will restart containers upon system reboot if they were started with -d, and have the right restart policy. But you still have to start those at least once. How'd you do that? Unless you plan to start it manually, you have to use some service startup mechanism. That leads us to systemd unit. I have to write a systemd unit to do docker compose up -d. But then I'm splitting the service lifecycle management to two systems. If I want to stop it, I no longer can do that via systemd. I have to go find where the compose file is and issue docker compose down. Not great. Instead I'd write a stop line in my systemd unit so I can start/stop from a single place. But wait 🫷 that's kinda what I'm doing isn't it? Except if I start it with docker compose up without -d, I don't need a separate stop line and systemd can directly monitor the process. As a result I get logs in journald too, and I can use systemd's restart policies. Having the service managed by systemd also means I can use aystemd dependencies such as fs mounts, network availability, you name it. It's way more powerful than compose's restart policy. Finally, I like to clean up any data I haven't explicitly intended to persist across service restarts so that I don't end up in a situation where I'm debugging an issue that manifests itself because of some persisted piece of data I'm completely unaware of.
Sorry, why do the bags have to be wet? Does the wetness affect the intelligence of a bag?
This has been a pretty educational moment ngl..
You said Trump bus originally. We were on the American bus, not the Trump bus. Once there was a change of driver to Trump, we got off at the next stop, as you pointed out.
Also most Canadians didn't love PP either. Instead we were united in hating Trudeau, which is why the libs started climbing in the polls as soon as Trudeau left the room. Before there was a new leader.
These can't shoot down F35, can they?
Let me know how the search performs once it's done. Speed of search, subjective quality, etc.
Why start anew instead of forking or contributing to Jellyfin?
I think I lost neurons reading this. Other commenters in this thread had the resilience to explain what the problems with it are.
This sounds plausible. Has anyone caught him in the act?
The problem is that Grok has been put in a position of authority on information. It's expected to produce accurate information, not spit out what you ask it for, regardless of the factuality of information. So the expectation created for it by its owners is not the same as that for Google. You can't expect most people to understand what LLM does because it doesn't scale. The general public uses uses Twitter and most people get the information about the products they're being sold and use by their manufacturer. So the issue here is with the manufacturer and their marketing.
GlobalFoundries to acquire MIPS, bringing together RISC-V chip design and manufacturing - Liliputing
GlobalFoundries trying to become AMD again. 😁
I use a fixed tag. 😂 It's more a simple way to update. Change the tag in SaltStack, apply config, service is restarted, new tag is pulled. If the tag doesn't change, the pull is a noop.
Let me know how inference goes. I might recommend that to a friend with a similar CPU.
F-35 exit strategy: Canada could pay about $313M to pull out of jet program, defence documents show
Ontario Election 2025: Pre-Debate, PC lead drops as Ford’s negatives rise. Ontario Liberals clearly in second. - Abacus Data
