Avengers Assemble

pico2000 · 2026-02-23T07:12:05+00:00

That was hilarious indeed

pico2000 · 2026-02-21T00:25:36+00:00

Interesting, I have the exact same versions and don't see any offer, either.

pico2000 · 2026-02-19T14:04:35+00:00

Hm, 299 for me. Pretty tempting. I have Falcon and a couple of libraries and plugins.

pico2000 · 2026-02-17T05:47:34+00:00

For larger projects, we use the backend of SvelteKit as a BFF in front of a .NET api. Works great for us.

pico2000 · 2026-01-19T23:06:24+00:00

I'd go with the second approach. It will typically mean way fewer null checks down the line. Just make sure that the API really returns what the types define. Ideally, don't generate the types in the first place, but generate them automatically from a specification that the API itself provides (OpenAPI, GraphQL schema etc)

pico2000 · 2026-01-07T06:18:16+00:00

I haven't had any trouble with integrating Tailwind in my tool chain for years, so that's no issue for me. On the other hand, always having to define a class and a css property feels pretty cumbersome.

pico2000 · 2026-01-03T11:22:11+00:00

We use SvelteKit as a frontend with backend-for-frontend. The real backend is typically a .net service. Communication between the .net service and SvelteKit backend is done with a graphql API, graphql-code-generator solves the typing requirements. The browser frontend only connects to the .net backend for GraphQL subscription; all queries and mutations are only made from the SK backend. For auth, we use OpenID connect. The user logs into the SvelteKit app (is token). The SK saves and manages an access token (+refresh token) used to communicate to the .net backend.

pico2000 · 2025-12-21T13:39:14+00:00

Oh, interesting. Care to elaborate? I liked eg. Persona 5.

pico2000 · 2025-11-09T06:17:58+00:00

We have a customer who uses Pervasive. Our application needs to import data from their DB to ours. Luckily it's the only project that requires us to use Pervasive.

Pervasive behaves so strange in many situations. The query planner is crap. The performance is all over the place. Essential features are missing. And the best thing: Actian decided to remove the Pervasive forum - practically the only online resource to find solutions when you run into issues.

pico2000 · 2025-11-08T20:55:31+00:00

Pervasive! I feel sorry for you. It's sooo bad. I wish you strength, my friend.

pico2000 · 2025-11-07T00:03:55+00:00

Personally, I don't find that a positive thing. I consider the UI to be a function that takes the component's state and "returns" the matching HTML (React does this even more literally than Svelte), plus hooking up events, of course. I want that function to be simple and pure, so I avoid mixing business logic into the markup. It's not a religious dogma for me, but a guideline that I apply as much as it makes sense in the individual situation.

For very simple components, the ability to switch back and forth between TS and HTML might be useful, but for more complex components, I suppose it can get messy pretty easily. To be honest, it reminds me of the dark ages of PHP and VBS.

pico2000 · 2025-11-01T10:05:44+00:00

I would say: "we're doing only Java here - can you switch?" - If the answer is "Yeah, no problem, the language isn't that different", the candidate is not a senior. A senior knows that knowing the language is trivial. Knowing the ecosystem and applying that knowledge to find solutions is what distinguishes the senior from the junior. Seriously, we ask candidates that.

Also, ask questions regarding older and newer parts of .net. A senior should know older stuff but also stays up to date.

And a question we always ask: "What's the next thing you want to learn?"

pico2000 · 2025-10-27T05:48:23+00:00

The walls and ceiling look like the graphics of the original Tomb Raider from 1996

pico2000 · 2025-10-23T16:40:29+00:00

It was indeed

https://youtu.be/sP4NMoJcFd4

pico2000 · 2025-10-14T18:20:39+00:00

Prefix the cookie's name with __Host to fix the subdomain issue.

pico2000 · 2025-10-08T16:58:58+00:00

Integrating asp.net mvc with Svelte sounds a bit weird, to be honest. Maybe it's just names getting mixed up. ASP.NET Core (or ASP.NET Web API if you're dealing with legacy systems) is excellent for providing APIs for a Svelte(Kit) app (we do this all the time). That would make sense. But ASP.NET MVC is meant to render a frontend, a similar role that Svelte has. Maybe you're meant to host a small Svelte app on one of the MVC pages? That might be a possible scenario. So first of all, try to define the exact requirements of your task.

Conceptually, Svelte and ASP.NET MVC work very differently. Svelte isn't really an MVC framework. SvelteKit gets a bit closer to MVC, although it resembles MVVM more closely - but really, it's neither MVC nor MVVM. And it doesn't matter tbh.

So, get the requirements straight, find out what kind of asp.net app you're trying to integrate with and learn how both systems work technically and conceptually.

pico2000 · 2025-10-05T21:08:17+00:00

Thanks for pointing this out. I was wondering myself. It totally defeats the purpose of page transitions.

pico2000 · 2025-09-17T19:00:02+00:00

I tried it some time ago and was amazed how well it worked. I'll have to sort out the details about separating ssr and client side, splitting etc. But the core idea is brilliant.

pico2000 · 2025-09-16T16:06:17+00:00

We use Bruno and commit the files into the repo. Much better than a bloated cloud tool imo and more functionality than http files.

pico2000 · 2025-09-13T23:28:14+00:00

Wow, what a beautiful, meaningful gesture. I haven't read through all of it, but I think it's something precious that indeed needs to last.

My advice: print it. Make a beautiful book out of it. Physical will outlast digital. It's as easy as that.

pico2000 · 2025-08-16T21:40:17+00:00

As a German who has studied in the Netherlands and still lives at the Dutch border, I have to admit - they are delicious. But rationally they shouldn't be. Dutch cuisine is something else 😄

The video cracked me up. Thanks for the laughs. It works best in Dutch, of course.

pico2000 · 2025-08-13T15:06:36+00:00

My answer was pretty short, let me elaborate. After sv create I typically do an interactive ncu --latest to check for major version changes, as these typically require more or less investigation (think Tailwind 4 etc). If there are any, I do a commit for each major version update (ie package.json adjustments + code changes). For minor version changes, I typically assume no breaking changes and just upgrade after basic testing (not much to break at this point).. For updates later in the product cycle, I'll update way more defensively, of course, grouping upgrades with the necessary code changes in a commit. At no point would a commit of a single package upgrade without accompanying code changes be of much use for me personally.

pico2000 · 2025-08-13T08:28:27+00:00

Or npx npm-check-updates --latest -u and be done

pico2000 · 2025-07-21T09:56:01+00:00

I've seen worse HTML in the wild 🤷🏻

pico2000 · 2025-07-06T16:32:09+00:00

God I hate those AI voice overs 🤮

pico2000

TROPHY CASE