jcusch

16 ms·

1.
by jcusch 1y ago
Fair enough, I thought what I'd originally written for that section was too wordy, so I asked Claude to rewrite it. I'll go a bit lighter on the AI editing next time. Here's most of the original with the code examples omitted
2.
by jcusch 1y ago
It looks like I was missing a www subdomain CNAME for the underlying github pages site. I think it's fixed now.
3.
by jcusch 1y ago
An ad for what? I'm not associated with any of the projects mentioned.
4.
Linear sent me down a local-first rabbit hole(bytemash.net)
467 points by jcusch 1y ago|218 comments
5.
by jcusch 1y ago
Thanks for the feedback, I like the idea of the multiplayer mode
6.
by jcusch 1y ago
Thanks, I'm glad you enjoyed it, I hope your friends have a good time too
7.
Show HN: Quotatious – A Wordle and hangman inspired game(quotatious.com)
7 points by jcusch 1y ago|5 comments
8.
The Servers Behind Serverless(nitric.io)
5 points by jcusch 2y ago|0 comments
9.
by jcusch 2y ago
This is great, I've been wanting to do something like this after finding an old series about making games in the terminal ( https://www.youtube.com/watch?v=xW8skO7MFYw ). I'll need to checkout bevy now.
10.
Let's Build a Game Using Only TypeScript Types [video](youtube.com)
1 points by jcusch 2y ago|0 comments
11.
by jcusch 2y ago
Thanks! That's not harsh at all, it's exactly what Tim and I are looking for. It's honest detailed feedback with great reasoning. I appreciate you taking the time to provide so much detail.
12.
by jcusch 2y ago
The reason for the abstractions is that the behavior of equivalent services from different clouds is functionally the same, but offered through subtly different APIs. If you think the value of each cloud is how unique their object storage (
13.
by jcusch 2y ago
Common denominator implies you're restricted to some subset of the cloud's features. I'm curious what restriction you see, since nothing about nitric limits combining nitric code with existing cloud libraries or extending pro
14.
by jcusch 2y ago
How you're describing iOS is similar to how nitric works. Developers indicate in code "I'm reading from this bucket", it's a request not an order, they're not actually configuring the permissions system. That r
15.
by jcusch 2y ago
Nitric is a layer on top of Pulumi/Terraform. It also supports Python, Go and Dart. Other language support is also possible. The Ops side of nitric (the providers) can be written in any language, but the out of the box providers are al
16.
by jcusch 2y ago
I'm curious what designs you use to avoid the issues. For example, if your code needs to access a resource (e.g. making a call to send an event to a cloudwatch event bus or SNS topic on AWS), how do you deal with things like: - Consumi
17.
by jcusch 2y ago
The application is agnostic to that with nitric, more so than usual. It could be worth reading the docs on how it works, I don't think you got it.
18.
by jcusch 2y ago
I'm curious what you think wouldn't work. Nitric doesn't cover every use case, but in those cases you just continue to do what you would have already.
19.
by jcusch 2y ago
We really like CDKTF and Pulumi, they're two options nitric uses for deployments, but it's also a layer on top that helps decouple application code from the target cloud(s).
20.
by jcusch 2y ago
Software built with nitric ends up with considerably less cloud related code in the application. The bulk of it is split into the provider, enabling separation of concerns. For example, instead of AWS client libraries, environment variables
21.
by jcusch 2y ago
That's essentially the idea with nitric, you ask for cloud resources in an abstracted request. How that request is fulfilled is determined by the provider used. What "read" access in nitric means can be up to the platform eng
22.
by jcusch 2y ago
That's actually something nitric helps with, it provides an API for deployments, separating it from application code. Those other teams like devops/sre/etc. are free to customize that process how they see fit. They can enforc
23.
by jcusch 2y ago
I can definitely see your point, but we don't think cloud development has hit up agaist the limits of inherent complexity. It's still needlessly complex in many cases. Projects using Nitric typically write the bulk of the applica
24.
by jcusch 2y ago
Thanks Junto, for function deployment we use matched files as the entrypoint for containers rather than exported functions or something similar. This lets you group many message consumers, route handlers, etc. together in a single container
25.
by jcusch 2y ago
Thanks, that's the way we see it too. We think people mistake "separate files" for "separation of concerns", but many applications have inherent coupling to their infrastructure.
26.
by jcusch 2y ago
It's a valid point, Nitric isn't a good fit in some cases. We've been working on improvements to the underlying provider implementation to allow for easier extension for non-standard cases. Nitric is a gRPC API under the hood
27.
by jcusch 3y ago
There is a collection of new tools trying to address this exact problem such as Nitric, Winglang and Ampt for example. (disclaimer, I work on Nitric)
28.
Is IaC Being Replaced?(nitric.io)
2 points by jcusch 4y ago|0 comments
29.
by jcusch 4y ago
There are probably a few reasons it might seem like web apps are faster. A few that come to mind are perceived performance https://developer.mozilla.org/en-US/docs/Learn/Performance/P... and optimization
30.
Contributors to AWS Lambda container cold starts(nitric.io)
6 points by jcusch 4y ago|0 comments

More ›