There was one in a previous AoC that I think stumped a lot of AI at the time because it involved something that was similar to poker with the same terminology but different rules. The AI couldn't help but fall into a "this is poker" trap and make a solution that follows the standard rules.
We all have our writing quirks, like how some people use shorthand for words where there is only a marginal difference (like "people" => "ppl"), or even people who capitalize the start of sentences, but not the start of their whole text.
There's plenty of prior work to go on. I mean, you could use a font ligature or one of the browser extensions (although I don't know if Chrome still lets you have a browser extension touch all text).
Change ChatGPT to 'my drunk uncle' while you're at it.
It affects a certain disposition for the writer; the information it contains isn't in the actual data they are expressing, but rather the state of mind that they express it from, which can be important context. Oftentimes it can indicate exasperation, which is an important social queue to be able to pick up on.
A little excerpt from Arlo Guthrie
"I mean, I mean, I mean that just, I'm sittin' here on the bench,
I mean I'm sittin here on the Group W bench, because you want to know if I'm moral enough to join the army, burn women, kids, houses and villages after being a litterbug."
Imagine that without the "I mean"s in it, and the importance of how they convey his stance on the situation.
Twitch puts the ads directly in the HLS stream, but as seperate segments from the content (a HLS stream is made of many small video files, on twitch they're about 2s long). They're trivial to recognize and filter out (they're actually explicitly tagged as ad segments) but it still won't serve you the actual stream you were trying to watch - the ad segments override it. The best you can do is just block until the first non-ad segment arrives.
Twitch is HLS, but they've tightened the buffers and shortened the segments (2s is standard) so that latencies of down to a couple of seconds is common. It's quite impressive, tbh.
In a weird way it kinda reminds me of `exec` in sh (which replaces the current process instead of creating a child process). Practically, there's little difference between these two scripts:
#!/bin/sh
foo
bar
vs
#!/bin/sh
foo
exec bar
And you could perhaps imagine a shell that does "tail process elimination" to automatically perform the latter when you write the former.
But the distinction can be important due to a variety of side effects and if you could only achieve it through carefully following a pattern that the shell might or might not recognize, that would be very limiting.
this is pretty much exactly how my "forth" handles tail call elimination, and it's the main thing that's added the quotes so far since it shifts the mental burden to being aware of this when writing code to manipulate the return stack.
as you imply towards the end, i'm not confident this is a trick you can get away with as easily without the constraints of concatenative programming to railroad you into it being an easily recognizable pattern for both the human and the interpreter.
I'm surprised they don't see more activity for polar orbits. You want to launch north-west or south-west and into ocean, northern scandanavia seems perfect for that.
Polar orbits have to go west, because they have to counter the earth's rotation if they aim to cross over the pole. Further north means less rotation to counter.
When I'm in charge of an on-call rotation I always try to make it very clear that this is not the expectation.
In my preferred model of on-call, you have a primary, then after 5min an escalation to secondary, then after 5min an escalation to something drastic (sometimes "everyone", sometimes a manager).
The expectation is that most of the time you should be able to respond within 5 minutes, but if you can't then that's what the secondary role is for - to catch you. This means it's perfectly acceptable to go for a run, go to a movie, etc.
You relax the responsibility on the individual and let a sensible amount of redundancy solve the problem instead. Everyone is less stressed, and sure you get the occasional 5min delay in response but I'm willing to bet that the overall MTTR is lower since people are well rested and happier to be on call to begin with.
We have a primary/backup setup and I would be pretty pissed if my primary just started going out for movies or a date night during their shift tbh. My job as a backup is to be there for unexpected events, ie they did not wake up or had an accident. Not be on call effectively 2 weeks in a row just because the primary doesn't take it seriously.
Yeah, going for a run or a dinner where you might be able to ack but not actually at keys for 10-20 minutes is one thing. Going to a movie or date where you might not even ack and won't be at keys for hours? Not cool at all.
I don’t see how this changes the problem where there is an expected guarantee of a rapid response except that now two people are expected to be available and would now need to directly coordinate in order to ensure one person’s going for a swim doesn’t interfere with the other’s WoW raid.
I guess to me that seems worse because that’d effectively double the number of off-hours accountability per teammate. Not only do you need to be first on call for your primary hours, therefore severely restricting the quality of your “free time” but now you ALSO have to be secondary on call for that irresponsible coworker that goes afk without properly communicating for 2 hours, dipping twice into your actual free time.
Out of 168 hours in a week, there are maybe up to 8 where I want to do something that interferes with being oncall. There's no downside real downside to being oncall for the other 160 hours. But I would get a lot of disutility from losing my freedom during those 8.
This is pretty much how it should be done. If the business demands more, they should have a properly manned 24x7 NOC.
You also need *ownership*. There is nothing worse than having to support somebody else's work and not being allowed (either via time or other restrictions) to do things "right" so that you're not always paged for fixable problems. Everywhere I worked where the techs had ownership (which varied from OPS people being allowed to override the backlog to fix issues or developers being given enough free reign to fix technical debt) has usually meant that oncall is barely an issue. My current gig I often forget I'm even on call at all and the main issues that do crop up are usually external.
Almost all the reliability issues I encounter is usually due to constraints ordered by people who don't have to deal with on-call.
Things like, running in AWS but you have to use a custom K8S install so they aren't dependent on AWS.
Using self managed Kafka so that you aren't dependent on proprietary tech.
It all sucks because they are always less reliable and generate their own errors and noise for on-calls.
If they had to deal with phone calls every time there's a firewall issue that had absolutely nothing to do with the application, they would soon change their tune.
So it takes 10 min until you've gone to the drastic solution? With this time-frame it would be risky to go the bathroom, not go to a movie. Also even the backup sounds like a primary in this scenario.
Sure, but the assumption here is that primary and backup (edit: probably, ie. they're not coordinating this) aren't going to the bathroom at the same time. It's also based on the idea that alerts are extremely rare to begin with. If you're expecting at least one page every rotation, that's way, way too often. Step one is to get alerts under control, step two is a sane on-call rotation.
We want to ack within five minutes, and be at a laptop within 30. So long as I'm within mobile signal when the page goes off, it doesn't really matter what I'm doing — an ack is a button press on a push notification. And I can stay within 30 minutes of my laptop and an Internet connection by carrying said laptop and my phone (with "unlimited" data).
If the primary (paid) on-call doesn't catch the notification, the secondary (unpaid) will be paged. And so on, down a couple more steps, to a senior manager. There's no expectation that anyone other than the primary would actually be available to ack the alert.
Having the primary/secondary rotation is arguably worse. In that model, from the perspective of any one participant, now they're on-call for two weeks each time around instead of one.
> I wonder why that C file which maps a more abstract Rust-friendly C-API on top of the existing API can't live inside the Rust directory and build structure
This is more or less what the RfL folks are asking for - they have a Rust API to be used by other Rust code, which uses the existing C API, and are promising to maintain that API themselves. It lives in the Rust "directory".
The C maintainer is rejecting this, seemingly because his goal isn't to find a compromise that works but to completely block the project.
This isn't all that different to how I use my gaming PC - it's off in another room, with a monitor that is plugged in but almost always off (I don't think Windows will boot without at least something plugged in?), Steam set to start on boot, and then I entirely use it via Steam Remote Play from my main PC.
I do use it occasionally - mostly when Windows has thrown up some issue stopping Steam from working properly.
eg. I need to dismiss a dialog that is invisible over remote play, or it won't finish logging in until I close a "finish setting up your windows install" screen.
Go to the gaming machine and upgrade it to > home or edu version if needed. Enable remote desktop with auth on your network for that machine. As long as Windows is booted and able to be logged in to on the gaming machine you can go on your other machine:
Win+R mstsc.exe and put in the gaming machine's name or IP and follow the instructions, checking all "remember this" boxes (there's 2, three if you count the certificate).
RDP won't let you play games but it is functionally identical to sitting at the machine itself.
I meant to come back and fix this but missed the window. I am unsure if the home/edu/N/P whatever versions of windows 7, 8, 10, and 11 support actually remote controlling the desktop as opposed to merely getting a "video feed" as it were. There's ways to upgrade to pro that are beyond my pay grade to discuss, but i think you can get a clean copy of windows that supports RDP for $130. If your alternative is "having a monitor plugged in 24/7" or "dummy cables but still have to plug a monitor in if something goes wrong with steam link {and it will. -ed.}" or other hacks/hardware, and you're already running windows at least the GPU/gaming side, RDP practically pays for itself even though it's $130 for that feature.
Someone else probably has alternatives (moonlight? bazzite? gopro and a soviet-era robotic arm (it only leaks a bit when it's hot outside.))
Can confirm, Sunshine + Moonlight are a killer combination.
I run a Windows VM on one of my servers for some gaming because I don't run Window's otherwise, and with Sunshine on the VM, I can play with moonlight from my TV, laptop, desktop, phone, ROG Ally (Bazzite), tablet, basically anything that can support Moonlight.
I still don't understand why operating systems can't properly work without a screen.
I have a Linux "home server" and I haven't found a way to boot up a graphical session with everything working (there were bugs in some applications, like menus not showing up, you couldn't change resolution, etc.).
A dummy HDMI plug fixed it, but still. It's 2025, come on.
You can run Windows server headless too, and run individual applications over the RDP protocol, exactly like using an X server on a machine with a screen to run Xeyes on a headless machine.
Anyone have a good tutorial or reference for doing that on a modern windows system? It would be very useful alternative to VM seamless style and allow Linux X11 system as the hypervisor with windows VM.
Well, i buried the lede. you need windows server to do it easily; once you have windows server set up, you need terminal services to be enabled and installed for that server. Then you can set up "single application mode" application. https://learn.microsoft.com/en-us/troubleshoot/windows-serve...
I didn't really need a guide, it's pretty straightforward; we ran firefox on a windows server VM in AWS and watched youtube videos, in 2009, just to prove it could be done. We offered thin client conversions to companies. never had any clients, too early, i guess, and everything went to cellphones instead. When i say we watched youtube videos, i mean on our test computer in front of us there was a firefox icon on the windows desktop local, and double clicking it, after a few seconds, would launch a firefox window, but instead of the firefox icon it would be the mstsc.exe icon, and you were not looking at an executable's output on your screen, you were looking at the output of the executable in the cloud.
anyhow the windows server software takes care of bundling/packaging/deploying of the the little "scripts" that let you have a desktop icon and everything else. I think there's a wizard.
edit: i buried another lede. The video quality of youtube over terminal services in 2009 with our crappy dsl was... "talking head" - or as i like to call it "peak apple quicktime video circa 1996" - approx. 15fps
When I looked into doing it once on a modern system and stopped when window server entered the story. I’ve been hoping there might be a simple solution but that had me stumble upon Parallels RAS which I’ve been considering doing an evaluation of.
My primary battlestation system (not gaming but for business) is 8X4k monitors on a custom Linux system driven by 2 high end GPUs. What I’d ideally like to have is many Win11 pro application windows managed by my X11 windows manager.
so it looks like, in addition to the method i mentioned, you can also virtualize the applications within "App-V" which is like hyper-v for apps (is anyone catching all of this? is this thing on?).
Microsoft made a firecracker or whatever for windows apps and no one told me?
edit: i'm shocked there's not a kitsch-y name for this like "Windowless Office Suite" for on-prem office that's virtualized for app-v... Someone at microsoft should pay me if they use this.
Quick skim seems to suggest the client to that system is Windows only.
I’m hoping for a Linux client which apparently the commercial Parallels RAS provides.
I think MacOS is even more hopeless than Windows for a per window or seamless remote GUI application solution. For Linux I use Xpra which honestly with GPU server and client acceleration can feel like magic. The dream for me would be a Linux based system for display using an X11 window manager to manage remote GUI application windows from all 3 platforms from multiple systems, all GPU accelerated on both ends.
Apple seems to have a particular hatred for the idea of anyone using their OS remotely for whatever reason, though Parsec works quite well for me, though I’ve heard there is a sunshine+moonlight approach that does even better than Parsec …
rdesktop has a "-A" flag for seamless mode which looks like it does what you want. I'm telling you we had that working 16 years ago via AWS - the AWS side was running windows but there wasn't any reason we had to be [running windows] on the client side. I merely mentioned that microsoft apparently didn't rest on their laurels with msts, they now support even more thin client mechanisms.
Windows will boot without a monitor, or at least, it used to, not sure about Windows 11. But Steam Link mirrors your display, and so doesn’t work without one.
I built a NUC running Windows 11 into a tiny portable server for a project I was building and can confirm it boots and functions just fine without being plugged into a monitor.
I just plug it into a power source and it does what I need it to do, but I can plug a monitor and keyboard (and sometimes a mouse because keyboard-only navigation seems to be getting less and less supported/intuitive...) if I need to perform troubleshooting.
The issue is usually with the graphics card itself in my experience.
This is easily "fixed" on a DVI port by plugging a resistor of the correct value into two of the tiny pin sockets. The diagram is very easy to find online and you don't have to open the computer. That's become a thing of the past as far as I know.
This always seemed to be a very deliberate design choice by them to avoid you being able to use their consumer cards headless versus paying them a large amount on the Quadro or DG cards, since the big problem we saw at $OLDJOB was always that you couldn't use CUDA on them headless.
At said $OLDJOB, we ended up soldering dummy VGA plugs that had resistors across the right pins when we wanted to experiment with building a low-power cluster of NVIDIA Ion boards and seeing how it competed with big cards. Ah, memories.
Would bet that this is exactly why. I run Tesla GPUs in my server rack which don't even have display ports, but they run any OS just fine with the vGPU drivers, which Nvidia make an absolute pain to obtain.
The _very_ first gen of Tesla cards did have those headers on them, IIRC, and then successive ones had the headers on the board but not connected for another generation or so, IIRC.
You also used to be able to edit the PCI IDs for the drivers to get the Tesla ones to attach to consumer GPUs, but that stopped working at some point.
Can confirm that. Using both to connect to the same windows box and sunshine+moonlight is better latency wise for fast paced games. And for games bought from GoG unless you want to configure Steam to launch them :)
Steam streaming is more convenient if the game is on steam and it's turn based or something like that. Also if the (mac) box you're streaming to has multiple monitors, Steam will continue to show the game if you cmd-tab out of it, while moonlight will minimize from the start.
Okay this all sounds great, what specs do I need on the machine connected to the TV? Will a Raspberry Pi 3 work? Pine64? Atomic Pi? (That's x86_64, intel Celeron)
Anything more than that and the value proposition goes way down. For every 50 grams lighter I am willing to lose 1fps. For every fan removed I will drop an entire resolution (4k -> 2k -> FHD...) Change "lighter" to heavier if it makes sense. My comfort and aesthetic matters more than competition quality, pixel perfect yadda
I keep starring these remote display projects but none have convinced me to provision a client machine for the purpose yet.
It doesn't take too much compute, the networking is the key.
I've run Moonlight on a bunch of things from my TV, crappy old Android TV box, phone, tablet, laptop, desktop, ROG Ally; don't recall if I ever tried a Pi, but I might give it a go.
My advice is, whatever you use, make sure it has wired ethernet for a consistent experience. That said, a more powerful device on the receiving end (Moonlight) with good high-speed wifi should also work fine, but almost always try to keep the PC end (Sunshine) hard-wired.
thanks, i have fiber and copper at the TVs. not in a pretty, or impressive way, i just have a switch next to the sets is all. fiber is impervious to most lightning strikes.
I got some hardware, someone else mentioned h264/265 hard requirements, but there were codecs before that for FHD that even a pi model B could handle (among them x264 i imagine). My main viewscreen is 720p60, DLP, it's real sensitive to artifacts in the visual output being literally glaring. doesn't take much horsepower to move 720p60 relative to fhd or 4k, imo; but here i am, hands out, begging for solutions!
I imagine it's related to what Sunshine/Moonlight is compatible with.
In terms of codecs, Pi4 is the best option (out of the Pi family) for hardware video decoders, Pi5 removed some hardware decoders which is unfortunate.
the gaming machine can handle all that, as i currently use it with a steam link (mentioned elsewhere) which means it's scaled from 4k/2k to 1080p or 720p depending on what TV i'm on. I'm sure i can run 4k (with a dummy hdmi dongle as i don't have a 4k plugged in to this pc anymore) with moonlight/sunlight/etc because i can do it with remote desktop!
At a minimum anything with h264 hardware decoding. H265, and VC1 hardware decoding supported but optional. It depends on what your output is.
Networking wise, cabled is the best latency and bandwidth wise but wireless also works but can be unpredictable depending on usage and environment.
This is one of many reasons why I just don't let Windows touch bare metal. My old gaming rig was a Linux machine that would boot a Windows VM with GPU passthrough, and the control I had over the virtual hardware that Windows thought it was attached to was really helpful for working around a lot of Windows bullshit. Won't boot without a screen? Virtually attach a fake one. Recognizes a device and tries to auto-install the garbage manufacturer-provided driver? Run the better Linux driver (if one exists) and have qemu present Windows with a generic version of the device. Want to debug some issue that requires disconnecting a piece of hardware? Just take it out of the qemu command instead of needing to go physically disconnect it. Want some remote peripheral attached that Windows has no idea how to talk to? Proxy it over the network in Linux and just present it to the Windows VM as a USB device. Having full control over the world that Windows lives in makes it much more manageable.
Same. I only stopped because managing storage became a problem - three huge games came out that I wanted to play.
Were I to do this again I wouldn't do ryzen I'd do at minimum a threadripper, so that the guest can get a USB pcie card and a GPU, so literally every device windows sees and talks to is virtualized. Usb keyboard, mouse, soundcard, etc.
I think LTT did an epyc build where 1 epyc ran 3 full "Desktops" with GPUs, nvme, for each virtual machine dedicated. I just need the one!
Ditto I grabbed a few clearance steamlinks and have all the TVs remote play to my single high power desktop and use a normal browser for media.
I had it running on ASTER at one point, a multiseat windows software so I can be on main computer and others can use steamlink on alternate windows profile and few issues.
Performance was rarely issue, especially even on wireless, and it's nice to have everything happening in 1 box.
