codebeaker

Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue.

Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

I live in northern europe, in Germany, so our bar is high, quality of life is good, but i'm no snowflake prude, around Market Street in San Francisco is simply disgraceful.

I witnessed on every trip passers by being harassed sexually by mentally unstable, or drug abusing people. I was offered to buy a stolen gun in broad daylight a block over from the Twitter building. I saw a gang of people storm a hair salon on Market St. and attack the occupants, spilling out into a 10 person brawl on the street. I've seen people jumping turnstyles and being assaulted by police/security personnel.

It's a really desperate situation.

A rudimentary look in the source code showed a <traffic-simulation/> element but I'm not up to date enough with web standards to guess where to look for that in your JS bundle to guess at the framework!

Glad to see competition in the space, but I doubt that Kreya can claim to be a "postman alternative" unless it has 75% feature parity with Postman, simply because the range of ways people use Postman is so broad, that it's an unverifiable claim.

Unless Kreya can do teams, testing, scripting, sharing, reviews, forking, publishing secret-link API docs, generating example API code out of the docs in Ruby/Python/etc, it certainly isn't an _alternative_ to Postman for my team's use-cases.

> Parcel CSS has significantly better performance than existing tools, while also improving minification quality. In addition to minification, Parcel CSS handles compiling CSS modules, tree shaking, automatically adding and removing vendor prefixes for your browser targets, and transpiling modern CSS features like nesting, logical properties, level 4 color syntax, and much more.

What literature, or framework or ecosystem holds this to be a hard-and-fast requirement of CQRS?

Personally I've solved this problem similar to Git, modelling CQRS on top of Merkle trees so your system at least knows if your incoming edit (command|commit) is being applied on HEAD (no changes to the model since the command started) or to HEAD+n (needing to re-run some command validations, and "rebase" the incoming command).

Of course what the author wrote, and what I understood needn't align, we're different, with different cultural references, but this stood out to me enough that I stopped reading to revisit HN to find out if anyone else observed the same casual use of what seems like inappropriately dismissive language.