I have used k6 in our CI/CD pipeline to do integration testing and then ran nightly actions to do smoke and load testing. It was easy to setup and it worked great.
The framework provides a clean way to define expectations and to produce data that can then be visualized in grafana.
OT but I’ve been working with WASM and TinyGo and hit an unexpected roadblock: TinyGo lacks JSON support (because the native go implementation uses reflection).
That meant that I couldn’t find a way to serialize structs between host and WASM compiled functions/modules.
The initial implementation of what I wanted to do took me half an hour. Trying and testing serialization libraries (JSON, protobuf, msgpack) took me four days and couldn’t find one that worked (working on a apple M1 made things more complicated). The one left to try is karmem but I just had to move on and be productive.
I used goja instead to get unstuck but now I want to find a working solution :)
I would call that a megalith, and not to be cute but to give a sense of scale which is useful. I think there is a point in which a monolith grows so big that is painfully obvious that size became an obstacle greater than the benefits.
Pain tolerance differs so the label gets applied at different sized monoliths.
(My brain was turning up Chicago, which I knew wasn't right. I note that Chicago and Memphis are both names for fonts... but I bet any large city has a font named for it, so perhaps that's just rubbish.)
I often interpreted this as a conservative interpersonal communicative approach. It is safer to talk about yourself than to ask questions from people because there risk of inadvertently saying something offensive.
Sure, you will find people that are a bit more self absorbed and would just pong about themselves.
But there are so many conversational constraints- asking “why” is aggressive, direct feedback is discouraged, slipping pronouns or other identity traits is a minefield, etc. You should not follow up when others say something because they were being polite and you’re putting them in evidence…
If you get to engaged in a conversation people can feel weirded out, like you’re supposed to go through the motions but that’s it.
Not talking also can get you in trouble.
Talking about yourself is probably the safest thing to do.
I actually find it easier to converse by asking polite general questions about what the other person just said about themselves. (Probably not something like "why?", more like "oh cool, how was it?") Because so many people's most comfortable topic is themselves, it can put them at ease. Can't go overboard with it though.
I think if you find that engaging with people is such a minefield that's probably on you. It's not hard at all to have an engaging conversation with someone without accidentally offending them...
People talk about themselves because conversations can be intimate - they're a two way street where both parties are sharing and relating.
I believe the OP. There's always a minefield when cultures collide. This is evident when someone from the US Midwest/Mountain West moves to SF for work. Just very different norms for how interactions are structured, and how good faith is communicated.
Because all involved parties basically look and sound the same, they judge one another according to their own local standards, instead of recognizing that they are actually interacting with a different culture.
I only used the VScode extension and is great. Except that it modifies the whole interface so I have two IDE instances one for with platformio and one without. It even encouraged me to write test for my arduino projects
I wonder if anyone can comment if they have experience running minio at scale. It would be a pleasant surprise if a “simple” minio cluster could handle such workload
It means that Prisma will provide a data access layer (we call it "application data platform" [1]) similar to the custom data access layers built by big companies [2] (e.g. TAO by Facebook or Strato by Twitter) that enables application developers to better access their databases.
We've explained that in the blog post here in the "Open-source, and beyond"-section [3].
I think we all appreciate the links but unless I'm missing something, no, it doesn't help -- what's the plan to make money? That blog post doesn't mention anything along those lines at all.
The framework provides a clean way to define expectations and to produce data that can then be visualized in grafana.
https://k6.io/