5

I can't get over the fact that my company downgraded the project from Elixir Phoenix to nodejs express.

I asked them why, they told me, the elixir is difficult and blablabla. In my resume, I did mention I have the experience for 2 and a half years (phoenix one year) , I can do that. and previously the senior here used elixir for scalibility , etc. Personally, the system he built weren't bad at all.

now in nodejs , with the async await promise shit.

but 'we prefer old tech' they say . old is gold they say .

Wait nodejs isn't old. To me elixir is like Ruby and Erlang had sex and gave birth to it and named it elixir.

Comments
  • 1
    I wrote a backend in nodejs recently and it was a shitty experience
  • 2
    There’s talk of ditching c# in favour of nodejs where I am now.
    The argument is it’s better supported in AWS. Well yes it is, but with the massive c# estate this place has (enterprise sized company) shouldn’t you have decided on using tools that avoid that?

    Just thought of a possible upside as I write this though. If we go nodejs then they are forced to throw away all the existing code that’s in .net 4.5.
    Sounds a bit better now
  • 1
    @TeachMeCode let's create deerJs.
  • 2
    It's easier to find devs for node, or so they think. In reality the market is saturated with amateurs.
  • 0
    @lbfalvy #fact
Add Comment