I'm working on a "toy" .NET web framework that has no dependencies on the ASP.NET Core Web SDK, runs fully on the "base" .NET Core SDK and can easily be embedded in existing applications.
It tries to be reasonably lightweight but batteries-included, with extra features in separate "extensions" packages. It's also designed to be modular. All functionality has a default implementation but can easily be replaced if desired. It uses the Fluid template engine[1] (a .NET implementation of the Liquid language).
It's been a great way to dig into more advanced concepts like reflection and HTTP internals and while it's probably not safe to use in production, I have used it to build small private apps with great success.
The current major pain points are the lack of websocket support, which I'm planning to add soon, and the general fragility of the NetCoreServer[2] based HTTP backend, which I'm planning to replace with EmbedIO. (Ideally, I would love to use Kestrel here, but it's so deeply baked into ASP.NET Core that you can't use it without pulling in the whole Web SDK)
The documentation is also pretty incomplete but I hate writing docs so I find it hard to force myself to do it.
(LLM Disclaimer: This project is not vibe-coded. Most of the code is written by hand, with some input from ChatGPT being used as a fancy search engine. The docs are written by hand and then fed through ChatGPT to make them more readable)
If you're looking for an alternative to Discord, check out Stoat (formerly Revolt). [1] Especially if you're an iOS dev with some free time as the iOS client could really use some love... [2]
(not affiliated with the project, just really want to see it succeed)
If this doesn't work for you on a reasonably recent version of Firefox, you can enable experimental (but in my experience quite stable) WebGPU support in `about:config` by setting `dom.webgpu.enabled` to true.
Bose continues to be an extremely consumer-friendly company (especially by today's standards). I remember back when the QC35s were THE noise cancelling headphones, the bridge* snapped on mine, I contacted Bose support asking if it could be fixed and they offered me a free replacement, no questions asked, a year after my warranty ended.
* Is that what it's called? The top part that goes over your head...
It would appear that they pay their employees fairly well, as seen in this old job posting [1] (not all levels will make this much of course but it gives you a general idea, almost 300k a year is a lot even for a staff engineer).
$275,000 is almost $23,000 a month. Take that times N amount of employees, and other business overhead, and suddenly $80k a month is literally peanuts.
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();
reply