>abstracts your network
>handles your requests
>makes oop babbies cry
why aren't you using elixir?
>abstracts your network. >handles your requests. >makes oop babbies cry
>abstracts your network
>handles your requests
>makes oop babbies cry
why aren't you using elixir?
it's kinda ugly tbh
What is beautiful for you then?
common lisp
scheme
haskell
idiomatic haskell is sooo sexy.
Link github or liar
I like the language, but I don't like that it's confined to a VM, it's pretty slow and heavy, its niche is very limited and its platform/ecosystem is completely dead outside of it.
If you're not a big company that needs some big dick concurrent, distributed, possibly embedded, stuff, Phoenix for webdev, as nice as it is, is all there is.
I want to get into it, but I don't have a use for it's unique strengths
A bit the same for me. There is a lot to learn, but it would be strictly limited to personal projects until I would be proficient enough with Elixir and Phoenix to start looking for gigs with this stack. The whole part about processes, supervisors and genservers is a bit daunting.
I am though. It's nothing special.
because me not using irrelevant languages makes OP seethe
I am using it
Because I’m using the other meme LLVM scripting language Julia
It looks interesting, but it's too slow and memory intensive and doesn't actually offer any advantages over like golang or even python for my use cases (microservices).
Bruh, you have no clue, the BEAM is amazing for microservices
>type checks at runtime
Consider this cis gendered alternative https://gleam.run/
because clojure is simpler.
What about Clojerl?
Because Elixir is a BEAM language, and if you need BEAM for some reason there are better languages like Gleam.
Elixir was made for moronic ruby gays.
do you really WANT oop people moving in to it? It's doing good enough with the people who actually uderstand what it's good at.
let it be, it's use cases will not disappear for the foreseable future.
> do you really WANT oop people moving in to it?
kek, Who do you think created Elixir? It's the OOP/Ruby gay version of erlang.
>It's the OOP version of erlang
Considering it's not object oriented and doesn't have classes or objects, no it's not.
Imagine coming online and posting about something you have no clue of just to pretend you fit in with the schizo contrarians on IQfy
Cause I couldn't get a job in it.
Erlang and elixir is what message-passing OOP is, anyway. Genservers are concurrent objects. The more I code in Go, the more I realize how good it would be to have supervisors, genservers, genstage in Go.
I am.
t. cto of startup built with liveview
tell us your story, anon.
How is it? I'm currently working on learning Live View, and it seems pretty neat so far.
Been getting sick of React, not that I actually write the code or anything though.
Are you on track to profitability yet?
No the aws bills ran wild and the company went bankrupt
Another successful startup for the resume
Because it's a poor man's Erlang.
Erlang is actually a poor man's Elixir. Elixir has access to every feature and every library that Erlang does, plus many of its own that Erlang doesn't have. It's strictly superior in every way.
Erlang can exist just fine without Erlang, but the reverse is not true.
>Erlang can exist just fine without Erlang
Incorrect
Now this is fault tolerance
I plan to. I've played around with erlang a bit so far. Want to learn both. But currently don't have the drive to actually write much outside of work.
BEAM is VM done right, imo. The JVM doesn't really bring anything new to the table in the way we program on it, in my experience. BEAM does. So even though I usually dislike VMs, I'm actually very interested in programming on BEAM.
No static typing is the biggest drawback for me personally.
Because every time I try to get into it some insane impossible shit happens that breaks everything. Like the dependencies don't compile on a fresh Phoenix install in a new directory and the fix I figure out on my own is that it magically works after you run the mix clean get compile cycle three times, not one, not two, three. That's bullshit. That's moron-mode bullshit. The Tailwind package produces a configuration file that FAILS BY DEFAULT because it omits a single line defining `plugin` at the top of the file. That's FRICKING bullshit. This ALWAYS happens - last time I tried to get into it, mix phx.new produced unworkable fricking garbage by default as well. Just following the instructions on their Getting Started guide would result in a broken project. I had to report it myself. For RELEASED, STABLE SOFTWARE. And everyone acts like it's totally normal.
I'm actually still using it I just want to kill myself. Back on the grind
I don't have any of these problems. Are you sure you're not just moronic?
>Are you sure you're not just moronic
No, frankly, but every issue I've reported has been fixed after I reported it. They just don't care to make things work up front. If you're using Elixir you're beta testing it for them.
>I don't have any of these problems.
Then you didn't start any new projects when Phoenix 1.6 launched
I came from erlang and elixir was butter smooth with 0 problems. Obviously your case is a skill issue.
Yes, clearly my insufficient skill level is what caused their getting started tutorial and default generators to produce broken code, documented and fixed in git. That's definitely what's happening here. It couldn't possibly be that the pleroma trannies are neuroatypical in any way
>clearly my insufficient skill level is what caused their getting started tutorial and default generators to produce broken code
Yep
I am. Built an intermediary service to handle bursty loads. It's fun to write. Supervisors and GenServers are extremely powerful. I prefer the functional approach over oop. I wish it were statically typed.
What do you use supervisors and genservers for?
supervising and generic serving mostly
For this service, synchronizing data access. The (dynamic) supervisor ensures only one genserver for a given entity exists at a time.
>BTFOs your shitty potion
best I can do
I am.
Elixir is just Erlang for rubygays, and I'm a hardcore rubygay.
>YES I NEED ELIXIR FOR MY 8 req/s SERVICE
Shit like this is hilarious to me. I moved from one company using Elixir for a 400req/s bulk data service to a much smaller company using Elixir for a 4req/s crud app and it's crazy how all architecture design completely stops mattering but it's not like we're going to stop trying to design it well.
>YES I NEED ELIXIR FOR MY 8 req/s SERVICE