I was expecting it to keep 2million checkboxes updated in my browser.
But looking at the websocket messages, it seems to only send updates about the slice I am looking at which consists of 1441 checkboxes at a time.
Two million checkboxes (written in Elixir)
51–60 of 61 posts
Re: Two million checkboxes (written in Elixir)
#52Earlier quoted context omitted.
Considering how many other solutions that are all trying to solve distributed systems issues but avoiding just using Erlang or Elixir I think the statement has merit.
Exactly, I've commented many times on here that at least half the show hn posts (like Hatchet from yesterday) are just overlycomplex implementations of features that have existed on the beam for decades. Or at least already in the Erlang/Elixir ecosystem (Oban, for example).
Proof that the only thing that matters about any software is whether it's easy for beginners to get into. What's wrong with Erlang that in ten years it's seen so little adoption?
Re: Two million checkboxes (written in Elixir)
#53I was expecting it to keep 2million checkboxes updated in my browser. But looking at the websocket messages, it seems to only send updates about the slice I am looking at which consists of 1441 checkboxes at a time. https://i.imgur.com/uKH4wee.png
Darn, I was gonna do that optimization
Re: Two million checkboxes (written in Elixir)
#54Funny how these things are fairly simple on BEAM. Funny how majority of industry won’t ever learn anything about BEAM and will keep hitting walls for the rest of their careers.
I find the pedagogy of Erlang and Elixir to be sparse. Maybe those programmers just start out strong and don’t need soft on-ramps. I know they’re working on it but not having types is also a big deal for project scalability and not just performance scalability.
Re: Two million checkboxes (written in Elixir)
#55I upgraded the server to 2 performance CPUs and 8gb of ram, running on Fly.io Should be fiiiiiiine, right?
Definitely needs more edge functions to scale horizontally across a global CDN.
Sincerely, Your friends at the triangle company
Re: Two million checkboxes (written in Elixir)
#56Funny how these things are fairly simple on BEAM. Funny how majority of industry won’t ever learn anything about BEAM and will keep hitting walls for the rest of their careers.
What can BEAM do that other languages can't? Do you have a favorite learning resource for it?
Here's the meme https://www.reddit.com/r/elixir/comments/gpdlp4/the_more_i_l...
It's not so much that it does things others can't, it's that it does all the things, running in the same application space, and things like background jobs, or a caching layer, or cron are all things that most stacks these days need to sort via another library, and Erlang/Elixir apps just do it all on BEAM.
Re: Two million checkboxes (written in Elixir)
#57Funny how these things are fairly simple on BEAM. Funny how majority of industry won’t ever learn anything about BEAM and will keep hitting walls for the rest of their careers.
tbh, the 2m app is more clunky than the OG 1m. Virtual scroll is very poor. Jump doesn't seem to work (it works just sometimes).
Re: Two million checkboxes (written in Elixir)
#58Earlier quoted context omitted.
Exactly, I've commented many times on here that at least half the show hn posts (like Hatchet from yesterday) are just overlycomplex implementations of features that have existed on the beam for decades. Or at least already in the Erlang/Elixir ecosystem (Oban, for example).
Proof that the only thing that matters about any software is whether it's easy for beginners to get into. What's wrong with Erlang that in ten years it's seen so little adoption?
10 years? You mean 38 years. And Elixir (a language on top of Erlang) has had solid adoption and is very easy for beginners.
Re: Two million checkboxes (written in Elixir)
#59Funny how these things are fairly simple on BEAM. Funny how majority of industry won’t ever learn anything about BEAM and will keep hitting walls for the rest of their careers.
The majority of the industry is made of people who care mostly about their own careers. If solving nasty distributed system problems is simple, you can't justify having a huge bloated expensive team. If your team doesn't spend a lot of money, you aren't seen as very important within the company. Since people want to be important, it's hard to get more productive languages to be adopted.
Re: Two million checkboxes (written in Elixir)
#60Funny how these things are fairly simple on BEAM. Funny how majority of industry won’t ever learn anything about BEAM and will keep hitting walls for the rest of their careers.
Unfortunately the Elixir app seems more flaky and keeps disconnecting with even a small number of users compared to the 1m checkboxes guy.