2,079 karma · joined May 23, 2016
We do not have any good research backing "bugs found later in the process cost more to fix".
If anything, the few empirical and solid dataset we have show no correlation, to at best really light one.
This principle may sound solid in theory, but the evidence is not here to support it and if anything seems to point to its invalidity.
See in particular https://shape-of-code.com/2021/06/27/increase-in-defect-fixi...
There are thousands of cases that are hidden in the bowels of the post office court system
Oh and the compensation are uh... let say hard to get the money for.
Numerous people that rabbithole into this case end up running to a nearby bucket. It is... not pretty.
I did not talk of reading documentation because i am literally one of the person you should come to if you need something in the doc. I learned how to write elixir and erlang by reading their doc.
I also do not use an IDE and am really relucant of them because i don't find them useful.
And I am a big defender of prolog. And i am not denying the strong architecture and infrastructure of erlang. I literally contribute to it.
But what you have not addressed is ... all I mentioned. The broken testing libraries. The inability to do the right thing nicely because the parse transform are a pita. The fact that modules names cannot be aliased, generating painful to navigate file structure and names. Etc etc.
And look. It can be made better. We have worked on documentation and there is more coming. We are getting multiline strings. Rebar3 mostly work. Hex can be used for erlang projects.
But in order to do things better we need to acknowledge the problems. Not just say that the kids don't understand. Especially when the person you say that to is actually understanding it pretty well thank you.
Typescript had ms behind it and it still took a decade. At some point the engineering, experiments and learning take time and you can hardly speed it up with more ressources.
I cannot agree. Erlang is a pita to with. From the lackluster test libraries, the lack of module aliasing, the atrocious UX of parse transform, and so much more.
Erlang bring nearly nothing that Elixir cannot do and the UX of elixir is by far better.
And I am not talking of syntax here.
You are close to realising the problem. Financialization is a consequence not a cause.
The cause is demographic. Why and how did pension funds grew so much need to own everything and get money?
Spoiler: this happened in steps with Boomers investing in their retirement. Because they were so numerous it flooded everything.
Second Spoiler: they also had (and still have) the political power by sheer number, which warped the regulatory environment.
Long story short, they are running in debug mode, badly written, not optimised, with bad OS level settings. And every time the community have tried to contribute fixes, the experience has been... Really bad.
So we stopped trying. If things have changed we could try again but ... We just wrote them off
In particular, it is preemptive. This... Makes a lot of stuff easier.
You can choose to cut yourself from this part of your humanity. That is your choice. But don't scowl at others as childish because they have real emotions to express.
It happens that words have meaning and using "vulgarities" have its place and meaning too.
You may not agree, language is a dynamic thing, but even in a technical or professional settings, these words have their use.
Enum.sum([1, 2, 3, 4])
Exist ;)That none of the participants lie and that you can infer niche effectively from the data. And that the ad can deliver the behaviour change
The ads are only cheaper if they actually find the niche people and change the behaviour. Otherwise you spent money for nothing.
The problem is that we have pretty good hunch from a bundle of clues that the data and org that validate these assumptions are lying.
We also have pretty good bundle of clues from the consumers that the ads are not hitting their niche pretty well.
So... We have an industry that breach privacy and lie, for a purported benefit based on seemingly false assumptions.
Maybe the results are not achieved.
I recommend a watch of this for a recent take on trying to change how we think of these. It is an open research field
Effekt or Ocaml 5.0 new events handler system may help get ideas that help you achieve your goal here.
It is that the historical developer of nix, who was also behind flakes, moved to create a company called Determinate Systems. And this company keep pushing out products that are "ways to fix all kind of problems with nix and flakes".
Except they are done in secret then announced, while the rest of the community is trying to actually make the underlying stuff just work.
It is a bit like the guy built a half finished stuff, good enough for him, leave it in this state, then keep coming back with "solutions" that are not in nix themselves. And let everyone else clean his stuff.
Ofc the other way to look at it is that they are the only one having results and really fixing things. But I am on the side of all the other maintainers that keep having to clean up the mess.