902 karma · joined March 1, 2019
Sad that you are a party pooper tho! I was being nice and warned you and here you are, removing the fun.
In my experience stuff like this is often vastly overestimated but if it really can do what it says it's great but I would like to see some examples.
They are a horrible, horrible party that desires power over all else.
Even though, it's far easier to change peoples opinion in one country than in 28.
Compared to Shein H&M is a luxury brand.
I guess what I am really asking is how would it say so? Because even if it is free software I assume this plugin would block it anyway since it don't know.
You could write an html comment just above it but how will I as a website owner know that this plugin:
1. Exists.
2. How to respect it.
There are plenty of plugins but this seems just like a plugin if you like to suffer when you really don't have to. I can kind of understand the goal of the FSF and I do hate some modern software today and companies trying to remove ownership but I have never thought the way FSF is doing stuff is a good way to reach their goal.
I don't get the hate against javascript tbh. With this, web components won't work I assume unless the license is known before hand? Or is that considered trivial?
What about wasm? Does it block that? Javascript is at least better than wasm since you can inspect javascript. So people that hate javascript should really hate wasm.
Sure, there were a lot of farmers having some animals but not in the large scale industry that we have today. That is a very modern phenomenon.
I read somewhere that scientists mutated it and that it's only 2 mutations away from spreading human to human and that the mutations are such that they could happen in nature.
I am a bit worried of the bird flu and I am very confused over the fact that we care so little about it and keep trading with countries that have horrible animal care which probably is the root cause of these diseases.
What exactly with VS is so great? Maybe I didn't use that feature..
If you sell a picture to me you can't come back 40 years later demanding me to stop using it just because it was successful, even if the picture is of you.
People accuse me of not reading, while seemingly not reading the entire thing themselves.
Not really cool or useful to me.
I really tried to learn RxJS, I used a lot of different methods like filter and what not but I still got into a huge amount of issues but honestly a lot of that was because angular was not really fit for the type of application we were trying to build. Especially as we relied heavily on query params for state. There were many strange behaviors of Angular Router that I ran into several times. It has some kind of own internal state and fires updates in an unexpected way. I remember sitting hours just to try to get the query params to update correctly and I was not the only one having these kinds of issues.
Even if I agree useEffect is unnecessary complex, it's still far far away from being as complex as RxJS and Angular. I remember I was trying to add some pipe service or whatever it was called and it was near to impossible to achieve what I wanted to do which would be trivial in any other framework/vanilla JS (unfortunately I don't remember what it was).
Then using third party stuff in Angular is a nightmare as well. You have to deep dive into how it's being built to make sure all the stuff is brought into the build step etc. The configuration is a nightmare if you want to do something special like making use of Angular Elements that's barely documented at all.
I never got to use the Signals feature, because I left the company before it got introduced into Angular.
The problem with Angular, especially as the app grows is that you will have many different subscribers that all listen on the same state changes, then fire them again so you will have code that just runs again and again and it's extremely hard to have a mental model on how the system work and what code runs when.
The code also easily gets super slow because you run something, it affect state, then it triggers something else that triggers something else that just happen to affect the first state, whoops now you have a loop. Even if the loop resolves, it's pretty much inevitable to get a loop sometimes if the app is complex enough, at least in my experience working with several other devs.
My last job forced Angular on me, I quit after a while (not because of solely that reason) but I told them Angular was a bad choice and they chose to overrule me. Pretty funny now, they will have to endure the pain of migrating a large app which makes me feel good.
Make stupid choices, win stupid prizes.
But yes I do believe in some processes, you can host an event on the campus as well to tell everyone how he is wrong.
I won't read any book recommended by people like you, sorry.
They are as much of zombies as the apple fanboys are. It doesn't matter what the company do, they will buy it and lick it up like they were a cat licking cream from a platter.