pmarino90

ahah sorry about that! I merely wanted to add that to the conversation but I should've replied to the previous message.

Here a good blog post on this exact topic

https://dashbit.co/blog/a-new-authentication-solution-for-ph...

> Tooling is just terrible. The VSCode plugin is crap, kills the CPU unless you disable features. There is no IDE from jetbrains. There is a plugin but last time I tried it, it was even worse than the VSCode plugin.

I am using VSCode too and the experience is not as good as with Typescript/Javascript but is not that terrible either. I would compare it with Rust's experience, so far.

> Also, I've read some comments where people mention "we don't need redis", "we don't need workers" everything is so much easier. That was our thinking at first. But then you realize on deployments you will lose your cache, or your background jobs, etc. So you have to persist them either in mnesia or in the database. At that point you're just reinventing your crappy undocumented and untested version of delayed_job.

Of course you need _other_ libraries to achieve some of those things. You do not have a queue built it but there are some very good tools like Oban https://github.com/sorentwo/oban that are basically doing what Sidekiq does, just relying on the main database you are already using. There are also very good libraries for caching that rely on ETS and that simply replaces what you could do with Redis.

> Most of what you get from elixir in terms of redundancy, high availability, etc you can have that anyway from kubernetes, heroku or any PaaS.... you will need more than 1 server anyway, so...

This is partially true. The ability of BEAM to cluster and execute processes inside the cluster, internal communication between actors and so on are not _just_ achievable with k8s, not without a good added complexity.

Nice points indeed!

I would also say that the "library" one is basically valid for every language. In general is always a good thing to spend some time analyzing the possibilities before importing an external lib into your application.

This could have been more interesting to read without the hundreds pop-up coming out!

Interesting point. I feel that dismissing the whole thing as a "lack of transparency" issue is a bit too simple though.

It might not be "illegal" but it is not farfetched that they are abusing they power position. Sure is their platform but we sometimes forget that it represents some 1.5B devices. As also other cases point out the 30% tax, which for a small firm is money, is not the only unfair practice. Different set of APIs for their apps and everyone else's is another important thing.

It is indeed true that arguing about complexity, while estimating, is useful to spark conversations about the item at hand. I feel that _estimations_ per se are not a good way to achieve those interesting conversations. You can, for example, analyze those items using the cynefin framework.

The tricky thing about estimations is that, for some people, they end up being a promise that then is used to plan the future leading, in some cases, to an unpleasant reality check.

"Simple & Safe – Synchronous programming keeps apps simpler and safer. In Objective-C, Swift and Java, asynchronous programming is very error-prone and requires callbacks. Synchronous nature of PHP makes bug-free developing a breeze." Seriously??