qw

WSDL is in some ways more user-friendly than openapi schemas. They have a rich set of types that mostly just work as expected. When I try to generate models from an OpenAPI JSON file, I often find myself either overriding the models or making scripts/plugins to rewrite the json to fix types. An example of this is using proper decimals instead of doubles, which is crucial in my line of work.

I think this library maps the different representations into a single representation. The business logic, metrics, logging etc. will use the single representation instead of being tightly coupled to the transport medium

Example from the docs where the "PAYMENT_DECLINED" state is mapped from protocol specific responses:

  PAYMENT_DECLINED
  |
  +-- HTTP 422
  +-- gRPC FAILED_PRECONDITION
  |
  --> logs/metrics keep PAYMENT_DECLINED

It's been a couple of years since I used it, but I think the Ionic framework has this feature.

https://ionicframework.com/

Yes, but mostly because of a lost opportunity.

I was working on my own web based reader when Google made a significant upgrade to their reader. It was similar to what I had made, so I thought it would be foolish to compete with Google and stopped working on it.

I wonder where RSS would be now if Google had not discouraged potential competitors.

It's how we used to make websites before SPA, and it's refreshing to see that it still makes a noticeable difference even on today's powerful CPUs and high speed networks.

In sci-fi we see warp drives, worm hole travel, phasers, photon torpedos and energy shields around ships. But what if none of that is possible? In that case, we might even have the technology to defend ourselves today or at least by the time they reach our solar system.

It's a huge risk for a civilization to attack us. Even if they have capabilities that are beyond our technology, there might still be limitations based on the laws of physics. And if they attack us, they risk a response.

Some names today still use the double a, like the Norwegian football player Martin Ødegaard. In that case it is pronounced the same as the "å" sound. (not too far from how an American might pronounce the "o" sound in "for")

> The Ship of Theseus, also known as Theseus's Paradox, is a paradox and a common thought experiment about whether an object is the same object after having all of its original components replaced over time, typically one after the other.

https://www.onceuponasaga.dk/journey

The initial prefix check would probably reduce the amount of lookups necessary, as it would only be necessary to do a deeper search if the prefix matches.

This:

    isRegistered: true

    accountStatus: "UNREGISTRED"

From what I have heard, it's still an issue with Excel, although I assume that Windows may handle plain text better these days (I haven't used it in a while)

You need to write an UTF-8 BOM at the beginning (0xEF, 0xBB, 0xBF), if you want to make sure it's recognized as UTF-8.

As others have explained, the news here is a rocket reaching orbit

It is probably easier to just close it down to avoid handling all the angry phone calls if it would happen to have an issue during the break.

https://idiot.vitebsk.net/i43/sun_english.htm

https://www.norsar.no/about-us/history/arpanet

Norway was the first country outside of USA to be connected to Arpanet in 1973 to share seismic data, but the universities did not gain general access until 1983.

I posted submitted a link to a story here: https://news.ycombinator.com/item?id=42655568

Some "10x" developers are extremely productive because they know the software stack inside and out.

There are also "10x" teams where they share an institutional knowledge of the software stack and are constantly improving and finding more efficient ways of solving a problem. When someone finds a better library, more efficient CI/CD or establish new code practices it is easy to apply it when they have a single stack to focus on.

It's hard to replicate this in teams where they are responsible for 10 micro services, each written in their own language and using different software stacks that are more "optimal" for some use case.