Recent submissions

Comment · 4 months ago
Wow, just wow. I think bullying the agents of careless operators is my new favorite thing.
Comment · 5 months ago
Considering it let them do an unauthorized wire transfer from a system account, 12k seems pretty reasonable.
Comment · 7 months ago
Hell yeah! After all these years it's finally here.

One thing I miss here (and admittedly I only skimmed through the post so if I missed this, please do correct me) is "ad hoc" unions.

It would be great to be able to do something like

  public Union<TypeA, TypeB> GetThing()...
Without having to declare the union first. Basically OneOf<...> but built-in and more integrated
Comment · 8 months ago
Comment · 8 months ago
No wonder they don't publish an availability percentage. If I was a business customer paying for GitHub I would be very upset with the availability lately.
Comment · 8 months ago
Actions are failing and starting new actions results in a 500 error... The status page is shockingly all green...

Edit: The status page is no longer green

Comment · 8 months ago
Comment · 8 months ago
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.

https://github.com/WispFramework/Wisp, https://wispframework.github.io/Wisp/

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.

[1] https://github.com/sebastienros/fluid

[2] https://github.com/chronoxor/NetCoreServer

(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)

Comment · 9 months ago
Comment · 9 months ago
For prototypes, almost certainly with a CNC lathe. For a large scale production, I would expect them to drop forge these...
Comment · 9 months ago
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.
Comment · 10 months ago
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...

Comment · 10 months ago
Comment · 10 months ago
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)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton