NoNameProvided
In my opinion, the pg repo and packages are an example of how OSS stuff should be maintained. Clean repo, clean code, well-maintained readme, and clearly focus on keeping things simple instead of overcomplicating.
I cannot pass judgment on whether this is good or bad, but I can easily see how this familiarity can be beneficial for the average programmer.
As a maintainer of class-validator, I'd like to clarify that this is not accurate. Legitimate security issues, when reported, are promptly addressed. The multi-year security alert listed in NIST NVD is akin to the bogus report that the curl maintainer discussed a few months ago.
In a nutshell, the report suggests that specific settings can potentially lead to validation bypass, which is indeed the case because these settings determine whether unknown objects should fail or pass the validation. This is analogous to my creating a CVE for Windows simply because anyone can access my computer when I haven't set a password.
However, the other part about the scare support is sadly true though.
Parent comment said:
> But the problems they solve are also unintuitive.
Do you consider calling a JSON API unintuitive or complex? If not, then you may be using the wrong tool. If you need nothing else, you are perfectly fine using a promise.
If you need to await extra requests, transform them, and react to other events then you need RxJS. For a simple call, you do not.
> I would imagine most people’s use case (mine certainly is) for RxJS boils down to “call a JSON API and receive a response”. That shouldn’t be a hard problem
Do you consider the following code hard to understand or are you are making requests in a more complex way?
``` this.network.get('<url>').subscribe(response => <do whatever you want here>) ```
Even if we agree to disagree that the above code snippet is hard to understand, you can just convert it to a promise:
``` const response = await lastValueFrom(this.network.get('<url>')) ```
A big part of maintainability comes from the quality of code and/or existing experience with the two frameworks, not the frameworks itself.
I work at an Angular only shop, if we would write some React it would be probably harder to maintain for us than the Angular ones.
I just have finished playing A Plague Tale: Requiem[1] a few days ago, and I spent the last two days with this strange feeling of sadness, almost grieving. It is such a masterpiece of emotions, the story of the bond of a sister and brother who went through hell to save the boy.
I remember the first game had the same effect when I played it the first time. For days I felt the with a mix of sadness and happiness. The developers have been successful creating such a strong bond to the characters that I felt I am practically there next to them, experiencing the pain and happy moments alike.
I really suggest everyone who has the smallest intention to play games to experience these two masterpieces[2][3]. (You definitely need to play the first game to be able to experience the second to its fullest.)
Since we are on HN, one technical detail that impress me so much the number of unique animations they created to give life to the word around us and to show the bond between the two of them. Like how Amicia waits for Hugo to get down from the ladder every time or how Amicia picks Hugo up multiple times during the storyline to carry him.
Thanks for letting me share this, I hope all of you have a nice day!
[1]: https://www.youtube.com/watch?v=zoEwC2TxiMA [2]: https://store.steampowered.com/app/752590/A_Plague_Tale_Inno... [3]: https://store.steampowered.com/app/1182900/A_Plague_Tale_Req...
> ...team is great and lot of interesting challenges...
A great team and exciting challenges are a strong retaining factor, and I dare to say, it's way harder to find a job that excites you than one which pays well.
You just summed up, why he said Angular is better in this regard. Yes any developer with experience CAN lean how to write good structured React apps. In Angular it is basically enforced.
There are problems with puclic healthcare that needs solving, but I would much rather focus on thoose problems than pumping insurace companies with money so private hospitals can charge 10x-100x the price of a treatmant (compared to Europe for example).
> With regard to nuclear weapons specifically, Russia reserves the right to use nuclear weapons: > - in response to the use of nuclear and other types of weapons of mass destruction against it or its allies, and also > - in case of aggression against Russia with the use of conventional weapons when the very existence of the state is threatened.
As long as NATO doesn't nuke something first or the very existence of Russia is not threatened, they should not use nukes.
From this part on I am speculating only, but I believe if Putin would press the red button the officers would have the right to refuse to execute the order.
[1]: https://www.politico.eu/article/russia-propaganda-disinforma...
What place would you suggest? We had bad experience with Azure support we could never fight through on the first support line.
> However, I believe you could have set up "public IP prefix" using azure cli. I do not think you needs a azure managed firewall.
I don't have deep experience in networking stuff on Azure so my understanding can be wrong, but I think "public ip prefix" is just a group of continuous IP addresses what you can reserve. You still need to assign those to something eg a NAT Gateway. As far as I know you cannot assign them directly to an Container Instance.
In our case, all we wanted was a static IP in front of an Azure Container Instance. Easy right? Let's put the container in a vNET, place a NAT Gateway in front of it and we are done. However, for some reason NAT Gateway is not supported for Container instances, instead, the official documentation suggests setting up an Azure managed firewall in front of your container that starts at a whopping 600EUR/month. That is a steep price increase from your ~30ish EUR/month for a basic container instance and it doesn't seem to be any other official alternative.
I have opened an issue with the docs team [1] about it and I hope there is another way of doing this that doesn't incur a doubling of our Azure monthly spending.
[1]: https://github.com/MicrosoftDocs/azure-docs/issues/81274
When you login into the NPM CLI it printed in all caps that the given email address will be public.
I don't like this either about NPM, but it's not like they are leaking in, they are upfront about it and warn you that the registered email address will be accessible to anyone in the package metadata.
This sounds interesting, do you have any sources about this?
> His generals really screwed up the Eastern theatre in the late 1940s.
My limited understanding of the eastern front is that: a, Hitler ordered the initial attack despite the warning of his generals b, forbid any (even tactical) retreat when the tides turned which eventually led to the destruction of multiple army groups.