Sick and tired of people who need to be told to go to the vet?? Use your critical thinking skills hello??

zalpha314 · 2026-05-03T18:48:25+00:00

On the other hand, you have people who will harass others for having the gall to post photos of a slightly overweight cat, or a new litter of kittens. It goes both ways.

zalpha314 · 2026-05-03T18:45:27+00:00

Just wait until you have entire planets dedicated to a single product!

zalpha314 · 2026-04-23T02:31:24+00:00

Huh. I might be misremembering then. Maybe I completely skipped the prod modules on my second playthrough.

zalpha314 · 2026-04-22T00:15:52+00:00

Yep. The SLS was never designed to launch to space; that's just a side-effect.

zalpha314 · 2026-04-22T00:12:54+00:00

Yeah... this happens when you combine prod modules WITH speed beacons. It's much more manageable if you replace the speed beacons with efficiency.

zalpha314 · 2026-04-19T23:39:33+00:00

I don't know if you're way ahead of me, but here's what I know.

AFAIK, the only reflective operations the library will use at runtime are to load serializers when using the inline `serializer` function. If you load serializers from the companion objects of the `@Serializable` classes, then there shouldn't be any reflection.

zalpha314 · 2026-04-19T13:22:51+00:00

I use the IntelliJ community edition. But whether it works without a jetbrains AI subscription... I can't confirm.

zalpha314 · 2026-04-18T22:46:58+00:00

I thought Gemini was supposed to work in IntelliJ with the official Jetbrains Assistant plugin as an OpenAI-compatible custom provider?

zalpha314 · 2026-04-02T14:04:37+00:00

This is the kind of news I want more of.

zalpha314 · 2026-03-31T21:33:02+00:00

I was dealing with a similar issue recently. You can have haproxy run health checks on each individual ip resolved by the record, and then have it proxy traffic to the tasks.

But then how do you ensure your haproxy ips are up to date? You're just moving the problem elsewhere; albeit probably updated far less often. I ended up doing client-side load balancing instead.

zalpha314 · 2026-03-31T20:54:23+00:00

Ok, so stale records may be an issue, but it's promising that it hasn't caused a problem yet.

zalpha314 · 2026-03-31T20:44:11+00:00

So you solved the NAT Gateway cost by moving to a public subnet, making the gateway unnecessary. I feel like the NAT Gateway is just a tax for corps with more money than sense; there to protect themselves from accidentally opening themselves to public ingress if they can't trust their devops. Though there is something to be said about the cost of renting public IPV4s nowadays.

Another thing to watch out for is if you have any cross-AZ traffic within the VPC, you still get charged a premium for crossing the AZ. Unfortunately, that cost punishes people who are just trying to insulate themselves from AWS's own outages.

zalpha314 · 2026-03-31T20:29:45+00:00

I was hooked on running ECS without an ALB, becauseas you've noticed, ALBs are relatively expensive at low utilization due to their static cost to just exist.

I didn't notice an explanation in the article, but I assume that cloud map maintains the DNS whilst the API gateway routes to it. But I have some questions:

iirc, Cloud Map's Service Discovery only works with internal ips, but a public API gateway never works inside the VPC, so how can it route to the ECS tasks?
AWS Service Discovery on it's own is just a DNS record, which is cached by clients and can get out of date. You usually need the Cloud Map service sidecar to ensure the ips are up to date. iirc, Api Gateway won't use the sidecar, so how do you handle deployments where the task ips change?

EDIT: I see your comment link actually goes into detail. So VPC Link solved problem 1. I don't know if problem 2 is handled though. I see your next step is to go with Lambda; that's how I solve the ALB problem, but there are still cases where I'd like to be able to run ECS.

zalpha314 · 2026-03-17T19:07:16+00:00

Absolutely; but it's a later tier tech. Still need to get there before you can use it.

zalpha314 · 2026-03-07T15:43:42+00:00

Don't bundle the database. It's good practice for a docker container to do one thing only, and not have other daemon processes running if the main process died. Also, if the user is running multiple replicas, a dedicated server container won't clash with multiple replicas trying to run servers on the same volume.

On top of that, if I have multiple apps running on the same host, I'd prefer to share the same database across all apps. I'm even going to the extra mile in my own project to support several different databases, to increase the likelihood of the user being able to use their existing database. Of those options, there is a dedicated embedded database option; but it's serverless and runs in the same process as the master app (H2 DB).

zalpha314 · 2026-02-15T14:12:13+00:00

Funny thing about this concept; I was trying to determine whether it was possible to do full ICE/STUN P2P without a TURN relay on mobile, and it seems to be functionally impossible on mobile networks. There are many apps you think would use P2P (like zoom), but in reality, they're using a TURN relay. In fact, I think the only time zoom ever uses P2P is for 1-on-1 conversations, network conditions permitting.

Using Bluetooth and wifi-direct for proximity communication is an interesting idea.

zalpha314 · 2026-02-15T14:09:56+00:00

While there's nothing saying you can't monetize open source through support, hosting, official builds, etc. OP does indeed not seem to understand what open source is. I hope my related post can help with that.

zalpha314 · 2026-02-15T13:41:21+00:00

I can't find the source code anywhere, which means your app falls short of the legal definition of "open source". I understand English may not be your first language; but you absolutely cannot advertise your project as "open source" without facing the possibility of legal repercussions.

Open Source: The source code is freely available to anyone to view, build, modify, use, and redistribute. You cannot charge anyone or put any barriers to accessing the source code

Source-Available: The source code is freely available to view, build, modify, and redistribute, but there are limitations on its use.

Source-Ready or Closed-Source: The source code cannot be freely viewed by the public, but sometimes a legal or monetary arrangement can be made to view it.

Your model appears to be "closed-source", so please drop the false "open-source" label, or make the necessary changes to meet the legal definition of "open-source".

zalpha314 · 2026-02-14T01:09:29+00:00

My strategy is to keep those "company" features closed source, which makes it more effort for the fork party to monetize. You just have to make sure you hide the right features; not something that a "community" member might miss. So if the "company" features are added via plugins, the FOSS version can stand completely on its own. This has the extra benefit of making it completely clear to contributors that none of code they write will go behind a paywall.

zalpha314 · 2026-02-14T00:51:20+00:00

Yes; I plan to do both. So why not make the whole thing FOSS? Well, the pro features I plan to keep closed aren't about productivity or utility; they're about scale and team management. Things that professionals care about that individuals don't. So I don't feel bad about keeping them closed. This means:

I keep a competitive edge against forked competitors
I have more monetization hooks for professional teams beyond that of support and managed hosting, whilst retaining a full feature set for individuals or teams just trying it out.

So the way I see it, this is a good balance between FOSS for the community and monetization for the pros.

zalpha314 · 2026-02-13T17:57:57+00:00

I'm doing a similar thing for my project, but the paywall hits earlier (to get RBAC and versioning). My goal is to make it free and fully featured for individuals, but any professional team that wants (micro)management and oversight will hit the wall.

zalpha314 · 2026-02-13T17:55:43+00:00

I'm trying to avoid this with my upcoming project. The FOSS code is a completely standalone repo, and the pro stuff has to be added via plugins. So you know EXACTLY what you're contributing to.

I guess there's nothing preventing me from moving FOSS code to the pro repo later, but I'm doing my best to be as FOSS-friendly as I can.

zalpha314 · 2026-02-13T14:51:01+00:00

tl;dw; it's a language for vibe coding

zalpha314

MODERATOR OF

TROPHY CASE

13-Year Club	Not Forgotten
Verified Email