mainguy

Ironically, people keep saying this, but then gloss over the core problem of coordinated between these agents... For completely independent codebases with no dependencies, sure thing right on...go for it. But the vast majority of F500 companies I work with have wild and undocumented dependencies between almost every system that will take years to "agentify" (assuming they ever figure out that it's an organization and governance problem.... which they might not ever realize)

IDK, at many large orgs...there are developers that essentially communicate through "tickets" and "their lead"... and Def never talk to "business" people or customers. It's not very rare if you get a large enough org.

I think the problem with C (well my problem) was the *& characters all over the place. I think because I spent too much time with pascal where (in my opinion) the pointer syntax is more symmetric.

I don't think that's an exact analogy....maybe if you're using react in some oddball/low skill way. Flash (and ...javafx/applets/whatever the id equivalent was...I can't remember) were 1000x more bumpy than react.

I was going to say the same, I have a webxr (virtual reality) site that has a few react components on it, plus a few vanilla javascript libraries in the main page template.

Umm, how is it a one way street? Just add a <script> tag and implement what you need... I'm not 100% convinced that using react from jump street "Just in case we need something in the future" is a great idea. That having been said, I'm not sure I've built a completely static html page in the last decade.... So I often start with react/angular.

User of Couchdb for similar use case...been keeping up to date on a parallel branch of my solution using fireproof instead of couch. Still early, but great potential...stumbled onto fireproof because I was about to write an adapter for couch (well Pouch actually, but same same) to replicate in a similar manner to fireproof.

I noticed planned maintenance in Duesseldorf, wonder if someone accidentally "flipped the wrong switch"?

Hmmm, suspicious that right after this cloudflare dashboard goes down. Sorta feels a bit like when AWS east cost took a hit and random other things stopped working (because they or things they depend on were running on same infrastructure)

We beat their status page by 10 minutes and downdetector by 5 minutes.

Well I was in middle of DNS change and the "remove" was completed when it went down....I guess I need to start to get a little more diligent about "what will happen if second part of operation can't be completed :o ?"

Hmmm, now my DNS is horked and I can't fix it :o

Note, just saw big traffic spike and realized there's no way to give feedback in the tool (sad trombone).

Yeah, docs say last write wins (at the field level though, not the document level).

I don't 100% know in the case of triplit, but pouchdb does what you describe for "free" (i.e. you don't need to code it). firebase uses a websocket, pouch uses (I believe) long polling.

Interesting take, I just switched from firebase realtime to pouchdb. I was getting concerned about firebase "local first" not really working how I expected and pouch fit the bill nicely. I like the idea of field level sync and wonder if triplit would be faster than pouch.

I wonder about this myself (sorry don't have a strong opinion)...but today we're so connected and I constantly wonder "if a tree falls in the woods and nobody tweets about it, did it actually happen?"

ROTFL...

For the non technical-ish... Have a drink every time I say "uh"...

Or as I like to say "Oh, you have a big ball of mud in your monolith because of poor design and want to move to micro-services?"..."now you have n^n big balls of mud" Poor design is poor design, adding more complexity just makes it a more complicated poor design.

8 minute overview of deployment compared to release and why you need to treat them differently.

Yeah, I mean at the end of the day if you really need extreme performance and/or offline capabilities (beyond what PWA can give) mobile is really the only way to go IMHO.

I maybe sidestepped the issue (because I use esm imports in my project)...I'm not sure if it's because i'm using webpack or if I'm misunderstanding the issue you're talking about.

A-frame has been around a while, but I see the future of immersive experiences diverging much like mobile/mobile web. Native will always have a place, but web is the future.

I think OP is coming from a different perspective than I (corporate bespoke solution builder) do. When I say "reproducible build" I mean a build that is the same on any machine (i.e. no special magic necessary to build a "official" version of the code). Too often in corporate environments, getting a local build or setting up a new build pipeline involves arcane black magic and/or copy/pasting weird libraries that can't be pulled from any sort of "official" repository. curl/bash libraries that "automatically change versions" based on when upstream decides to change them can wreak havok when setting up a new build environment. My $0.02, it's not (in the corporate world) so much about validating binaries, but more about "how many steps beyond check out the code" exist and how easily can I validate my binary uses the same versions of libraries/dependencies as the one that a local developer tested?

Well, looks like it's been resolved.