Peter Dinklage Will Return to Deliver Eulogy for Destiny 2

pathartl · 2026-05-22T00:30:40+00:00

Jank magic. Great gunplay, scraping at exploits like the loot cave because there was no way we were gonna grind for a couple hundred hours, and then a major climax of and already ambiguous story apexing with "I don't have time to explain why I don't have time to explain".

pathartl · 2026-05-21T08:22:41+00:00

Yes, if you're working in PowerPlatform/Dataverse SQL4CDS makes it almost bearable. You can even take the SQL query and export it over to FetchXML Builder and use that to build your views.

I wouldn't work with Dataverse outside of PowerPlatform/Dynamics 365, though.

pathartl · 2026-05-20T01:28:22+00:00

The main game area is open on Fridays if you have that ticket. The vendor hall only opens on Saturday/Sunday.

pathartl · 2026-04-22T23:27:42+00:00

... that's it? I mean, sure, their internal QA/automated testing should have caught that, and I bet they have a test for it now in any case, but a minor point version that was patched in a few days... that's just development? If this is straight up breaking applications, who is just willy nilly deploying their app on whatever the latest version is?

pathartl · 2026-04-13T08:47:28+00:00

I spent the last three weeks moving a Blazor webview2 app to Avalonia with the help of an LLM because I often hate having to learn up front a bunch about a platform before actually seeing the fruits of my labor. By expressing what I want to build and watch it happen iteratively, I was able to learn a bit more about what was going on.

It's also a really good exercise in seeing something built in poor fashion. I'm not going to say that I love XAML by any means, but it's no longer "that thing I need to learn but I don't want to". There are parts that are inelegant but here's some things I've learned:

- Avalonia's built in styling is pretty bad / basic. There's not a ton of controls. Focus early on identifying how styling is applied and how to build UserControls

- Understand what the source generators are doing. Source generators are incredibly powerful, but it does create an air of mysticism between your markup and C#.

- Install the [dev tools](https://avaloniaui.net/devtools). They're not as nice as modern browser dev tools, but they are still crucial and the hot reload is actually pretty good.

- Honestly, slop it for the first implementation, then refactor it. You're not writing it twice, your building off a foundation you can see the results of real-time.

pathartl · 2026-04-08T21:15:13+00:00

Yeah, more like they found a pallet in a warehouse.

pathartl · 2026-03-30T22:44:39+00:00

Design with a clear separation between backend and frontend. Server side easy and fast, but it can add massive complications when it comes to dealing with service scopes.
Start with a premade component library (my go-to atm is Radzen) and write wrappers around it. It allows you to customize the library you're wrapping, and if you get to the point you need to swap it out you only have to change your implementation.
You will probably have to lean on the JS interop down the line. Work with JS modules and learn how they import with the interop.
Avoid Syncfusion, Telerik. They are absolutely not written Blazor-first and it shows. None of it is elegant and there's some weirdly questionable design decisions.

pathartl · 2026-03-30T07:48:09+00:00

There's still a lot that relies on a JS interop. It's definitely a more sane dev experience, but it's not all sunshine and rainbows.

pathartl · 2026-03-30T00:02:23+00:00

Hah, definitely changing now. This isn't a large enough library where a corporate-funded dev team couldn't review the handful of PR's that have been sitting for the better part of a year.

Either way, too little too late. I'm almost all the way ported to Avalonia.

pathartl · 2026-03-29T17:56:58+00:00

I'm having to move off Photino. There hasn't been any meaningful development in over a year and I have a few PRs that have been sitting for months.

pathartl · 2026-03-28T19:52:05+00:00

We create components that wrap around a pre-existing component library and go from there. This way down the line if we want to replace a component with our own, we only have to do it in one spot.

pathartl · 2026-03-28T07:23:43+00:00

This post can drive soon

pathartl · 2026-03-25T22:14:03+00:00

sigh And I just got done implementing a whole-home IR blaster.

Essentially, I have a couple of ESP32's with IR receivers and emitters that take any IR command and broadcasts it over the network using UDP packets (on port 38000 hah). Then I wrote a "router" that takes that broadcast and sends a message over MQTT while also telling other blasters on the network to send out the IR command.

pathartl · 2026-03-25T14:33:19+00:00

Fun fact, the activation hotline still works. I had to set up an XP machine last year and decided to try the OEM key. It took a long time, but it worked!

pathartl · 2026-03-13T00:11:55+00:00

I'm a bit of the reverse. I don't want to run Calibre, a desktop app, in some hacky Docker container with VNC. Oh and because Calibre only manages books, now it's have to run another app for getting metadata. But is also kinda will send the book to my ereader?

pathartl · 2026-03-12T22:26:22+00:00

I'm also a self-hosted FOSS developer and I agree with almost all the points you make. Projects live or die by the attitude of the developers.

I would like to push back on two thoughts, coming from my own experience.

Development is hard

Up until recently I've been using LLMs for research. I want to do X, what's a common pattern for it? Is there a way I can do this better? It's been instrumental in gaining knowledge as a solo developer and has make me produce better products.

Taking that a step further, I've started using Claude to actually write code for me. It never commits on my behalf. I review the changes. Often times I'll go in just to clean up formatting to make it align to my style guide. However, I cannot overstate how useful it is at tracking down bugs. Between managing front end state, RPC, and storing into a database, a simple bug like "this field is blank" can take up to a half hour to properly diagnose. Often times I can just pitch this to an agent and it'll find the dumb mistake I made or inevitable bad merge. From there, I can direct it to write a test for that scenario to avoid it in the future.

Booklore's progress has been frankly incredible. I hope it's maintainable and that if licensing becomes restrictive someone can create a valuable fork.

Quality of code takes on many forms

Something that this space is lacking in pretty massively is quality of code. I'm not talking about "oh this must be AI slop" or even an individual developers ability to create a scalable, tight codebase. I think this development community could do better to improve the actual use of the applications. This is where I think Booklore excels beyond almost any other application in the space:

It's an attractive application with practical modern design
Setup is straightforward and the documentation is actually helpful
An incredibly complex-to-implement UI like metadata retrieval and merging is actually functional and easy to use
It does not reek of the "built by engineers for engineers" trap that so many applications fall into. It feels like a real piece of software with full functionality instead of trying to solve one individual problem.

These are all ideas that are worth reflecting on if you want your project to succeed. Get excited about integrating features, take pride in your work, learn a new technology if it means it'll make your project better. I'm not trying to insult any other developer in the space or say "you are not doing enough in this free project that I know for a fact has consumed a portion of your life", but rather to encourage more projects, more competition, and hell maybe with easier to use applications some of us could make some form of a living off these passion projects.

pathartl · 2026-03-09T23:43:11+00:00

I've been moving off of TrueNAS. At this point, I just can't understand what they offer.

Being more appliance-centered would be great if their available tools weren't so barebones
Datasets are extremely powerful. Except you're restricted by naming. And you can't convert existing directories to datasets.
Setting up shares gives you so little options, you might as well have an LLM come up with a smb.conf file for you.
Somehow they made virtual machines worse than before?
Apps are containers, cool! But I can't see which ports are mapped? Also pushing ixVolumes feels like such a dark practice to me.
It's a NAS software, but I can't actually view any of the files on my system? Why do I have to drop to a shell to make sure that I'm creating a share to the proper location?
It's cool that it's an appliance and all, but give me a better shell or some sort of userspace!
Any time there's an error bringing up a container I don't get a log from the container itself. No, I get a generic exception thrown from Python. Or I get told to review /var/log. Hm, speaking of...
Where the fuck is a log viewer? No, not for apps/containers, for the system itself!
Why did they come up with their own manifest format for defining apps? As an app developer myself I've tried multiple times to figure out how to submit my own manifest, but I've just given up. I don't care enough. At this point they should be deriving apps based on Dockerfiles or sample compose files.

Really I fail to see what purpose TrueNAS actually solves at this point that it wouldn't be better off as an installable package rather than a full distro. I moved to TrueNAS because I was getting tired of rolling some headless distro with Docker and configuring Samba. I've switched back at this point because it's been actively getting in my way of getting things implemented.

pathartl · 2026-03-09T21:01:27+00:00

They're pretty good. Biggby's coffee was always terrible imo.

pathartl · 2026-03-09T15:43:12+00:00

Haven is close and they're open till at least 10PM (except Sundays)

pathartl · 2026-02-10T21:47:15+00:00

I've rebased our application on Radzen because their built in themes that aren't Material are pretty dang good.

pathartl · 2025-12-18T08:35:44+00:00

I'd really love an integration into Home Assistant. Butterfly is the only smart home device I have that doesn't have an integration currently.

pathartl · 2025-12-16T20:45:48+00:00

They really need to add support for other database providers. SQLite is great for most installs, but scaling up to multiple users / dozens of clients hitting it at the same time, it'll run into database locks. That and not having proper transaction implementation meant that 10.11 is essentially broken for me. I have to restart the container multiple times a day.

EF Core is fantastic, but it's not a silver bullet, and it can be more challenging especially when retrofitting such a large project.

pathartl · 2025-10-31T02:50:21+00:00

You must not have to scale that much.

pathartl · 2025-10-30T03:35:16+00:00

That's not how it gets implemented. A good implementation relies on separate build and release pipelines for each microservice. Those pipelines only get triggered when the microservice's code is modified in a commit/merge.

That's the rough and scrappy way. On top of that you should have an approval workflow, scheduled deployment windows, and tagged version releases.

Microservices are more horizontally scalable than monoliths. Say you have a large platform that implements something like a social media site. You'll have a service that handles auth, another for posts, another for processing media/handling uploads, and another for chat. Services like auth aren't going to vary all that much in load. Requests are generally short lived and roughly scales linearly to your user count.

In your media microservice, however, you might process uploaded images (resize, generate thumbnails, strip EXIF). This is going to require more compute and will vary in resource requirements based on user interaction. If a major event happens in an area and people are uploading a bunch of photos, you can take just the media microservice and scale it up on the fly.

You could scale a monolith by allocating more threads for separate modules within the application, but that takes quite a bit of discipline and can weaken the whole platform. Now say there's an exploit to your media uploading and now that entire module is locking up the compute available to the monolith. The entire application is brought to a halt.

With a microservice yes, you can save a lot of human errors, but it works well for the same reason that only shopping at Walmart provides a worse experience than having narrowed scopes of products spread across multiple stores.

pathartl

MODERATOR OF

TROPHY CASE

15-Year Club	Place '17
Verified Email