cirego

9 ms·

1.
by cirego 18d ago
I agree that attribution is professional. What I would worry about is people using the link to supply the reasoning behind the change without putting it into the commit message. Then you have the problem of needing to load the session to un
2.
by cirego 6mo ago
I've noticed that there's another problem with microservices as well. People tend to tie microservices and multi-repo into the same strategy. Multi-repo appears to make teams faster (builds are faster! fewer merge conflicts!) but,
3.
by cirego 6mo ago
First thing I noticed too.
4.
by cirego 1y ago
It sounds like this framework is susceptible to head of line blocking. In my experience, that significantly reduces the utility of any applications written choosing this framework. What’s the benefit being delivered?
5.
by cirego 1y ago
I noticed the same thing. I would have expected an Arc<Mutex<…>> or something similar for safe concurrency. Not sure what value is delivered by a single threaded, blocking web server.
6.
by cirego 1y ago
You bring up an interesting question -- I think Tilt works best for those that find themselves in an environment where product is delivered using a service-oriented architecture deployed to Kubernetes. It's also easy to get started wit
7.
by cirego 1y ago
I think Tilt Extensions highlights the combined power and composability that using Starlarks brings to Tilt: https://docs.tilt.dev/extensions.html . Want to create a Kubernetes secret? It's as simple as: load(&#x2
8.
by cirego 1y ago
Thank you for sharing this! I think your Tiltfile just showed me how to solve something that's been bugging me for a while! I see that you also have docker-compose files -- are those for different tasks or for developer preference? I&#
9.
by cirego 1y ago
I've always appreciated that Tilt chose Starlark instead of YAML. Makes things so much cleaner!
10.
by cirego 1y ago
I think that's a fair point -- you're making a tradeoff. And the best part is that you don't need to choose one or the other. In my case, I find that I prefer having higher fidelity and simpler service code by using Tilt to a
11.
by cirego 1y ago
My understanding is that dev containers are more about configuring your development environment with the right toolchains to build and run services. Tilt is a monitor process that builds and starts your services, with a hot-reload loop that
12.
by cirego 1y ago
Yes, Tilt really shines when you’re testing interactions with Kubernetes, such a APIs. But also things like your services’ ingress configuration and metrics scraping. By default, Tilt is actually intended for local development using kind, m
13.
by cirego 1y ago
Tilt can also help validate things like: - Service discovery - Volume mounts - Ingress and Certificates - Metrics scraping and configuration - Dashboards It’s really quite powerful and replaces the need to mock things out with docker compos
14.
by cirego 1y ago
Interesting to see this pop up here! I’ve been using Tilt for multiple years now but the pace of development seems to have slowed down after the Docker acquisition. I love how Tilt enables creating a local development environment that lets
15.
by cirego 1y ago
Sorry, I should have added my second thought. Your original comment about isolating MCP servers is also good! These are tools where the AI may tell you it’s doing one thing and then accidentally do another (I had an LLM tell me it would mak
16.
by cirego 1y ago
I believe echoangle’s concern is about the security and privacy of the LLM using the data, not the MCP server itself.
17.
by cirego 2y ago
I think you might be off by a factor of 10. Alphanumeric would be at least 36 characters, which would imply 2.8 trillion combininations (36 ^ 8).
18.
by cirego 5y ago
At the moment, we are focused on scaling up with a single instance. While there are a couple of strategies for scaling out, none of our current methods support scaling a single view beyond a single instance. This isn't really a technic
19.
by cirego 5y ago
You are correct! Updates are a expressed as a retraction and an insert that happen within the same timestamp. An example may not be necessary but it might also help clarify. Assuming you're using the psql client to run "TAIL WITH
20.
by cirego 5y ago
> In the simplest case, I'm talking about regular SQL non-materialized views which are essentially inlined. I see that now -- makes sense! > Wish we had some better database primitives to assemble rather than building everything
21.
by cirego 5y ago
> Yep. I meant it was easy to do it the inefficient way where you just refresh the entire query when any table mentioned in the query changes. You would just have to also check if something was a view and recursively parse the SQL that i
22.
by cirego 5y ago
Disclaimer: I work at Materialize. This is the exact problem that we are solving here at Materialize! I wrote an example blogpost that details to how to subscribe to a SQL query in practice: https://materialize.com/a-simple
23.
DOJ Drops Challenge to California Net Neutrality Law(law360.com)
3 points by cirego 6y ago|0 comments
24.
A Simple and Efficient Real Time Application Powered by Materialize(materialize.com)
20 points by cirego 6y ago|1 comments
25.
by cirego 6y ago
My understanding is that ksqlDB is a read-only interface on top of streams and only helps people write better consumers. The problems mentioned in the blog post relate to producers.
26.
by cirego 6y ago
Please do!