Considering the relatively limited context window even on the latest models, the output would likely be incoherent mess. Sure, you could make the LLM go through the code in easily digestible chunks (file by file) but to get any groundbreaking optimization, it would need to have the context of the entire project to properly understand the architecture. (IMO that is, I'm not an expert)
If you want a more... ergonomic language, you can also use the new "run file directly" functionality in .NET 10. It supports shebangs directly and it will even install packages referenced in the script!
#!/usr/bin/env dotnet run
#:package Newtonsoft.Json@13.0.3
using Newtonsoft.Json;
Console.WriteLine(
JsonConvert.SerializeObject(new { Hello = "world" })
);
Even better, with the #:sdk directive, you can even serve a tiny web app directly from your "fancy shell script"...
#!/usr/bin/env dotnet run
#:sdk Microsoft.NET.Sdk.Web
WebApplication
.Create()
.MapGet("/", () => "Hello from a shell script!")
.Run();
Almost definitely not this FTC. And I'm not sure the FTC would in general considering there is a plethora of mainstream streaming providers outside of just Netflix and HBO Max.
Apple, Amazon, Google, Disney all have their hands in that bag. Not to mention all the old cable providers are practically streaming services now too. I don't even use my spectrum cable box, I use the Roku app to watch live TV and access all their on demand library
I've been working on a factory sim game for some time now and I'm finally getting to a stage where I might be comfortable enough showing it off soon and maybe even try my luck with some sort of crowdfunding.
I duct-taped together a quick website[1], you can sign up for the mailing list or the discord if you're interested... Or just check up on the website in couple of weeks.
My country's national postal system still uses an IBM mainframe based system from the 80s. The clients these days are desktops with Linux Mint and a terminal emulator but it's still very much TUI based.
