Funny 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.
Without evaluating the merits of your statement, I find it funny you start out implying others are close-minded, but end up rather close-minded yourself.
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?
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.
It's way too slow and per-task overhead is much higher than in compiled alternatives (Rust and .NET - BEAM performance is much worse than these, sometimes by a factor of 10).
Surely you're not asserting that other platforms that provide concurrency and parallelism primitives are designed by people who don't know what they're doing?
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.
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.
It’s actually fascinating to watch this one. You can see scripters fighting for control. I just watched all the checkboxes get unchecked within a couple seconds, followed by an equally swift counterchecking from the opposing side.
Love the user count too. That was missing from the first one.
It would be nice if it had a fixed zoom level so that messages like "hi" would show up the same for everybody. But given the scripting, I guess it wouldn’t matter anyway.
Now you know what you have to do next: add 8-bit color selection support. Then we can prove once and for all what HN’s favorite color is.
Ha, nice. Any interesting notes on scaling and load testing? At what point does it fall over? We all found it out empirically with One Million Checkboxes, so I'm curious how this compares.
I'll let you know once we had actually hit some performance ceiling. Right now, there like 50 users. I don't even see that in my metrics. But I'll keep you posted.
Some numbers. When cursors.io (now dead, search images) had a huge influx from China for some time, it went into thousands daily. According to wiki, r/place attracted 90k, mostly bots, I guess. There isn’t much to retain a “player” in subj tbh, so…
Like do y'all leave carts out in the parking lots and Starbucks drinks on shelves? What went wrong in your life that you think it is fun to destroy other people's work.
EDIT: Feature request with that in mind: you should block someone's ability for 5 seconds to click if they are clicking subsequent boxes and someone reverses the check/uncheck within 2 seconds. Turn it into a real war.
eg: you are checking/unchecking in a line and someone clicks the box right as you click it, you get stunned.
It's a checkbox. It has one job in life. To be clicked. Your OCD isn't going to prevent me from clicking some checkboxes, either to check or uncheck them.
Awesome! Would it be possible to make checkbox number part of the url? This way, I could send someone a link straight to part of canvas, that I worked on :D
I just built my own version because I was curious how this would look like in a server-side rendered framework like LiveView. But I'm all for it that we build different versions in different stacks and compare notes :)
If there were to be an arms race like that, my first attempt would be infinite-checkboxes or similar. Would probably run absolutely horribly on anything but the beefiest machines, and cost thousands of dollars for bandwidth.
Would need to come up with a way to make (un)checking computationally expensive to stop the state immediately ballooning to gigabytes in size.
Elixir + Phoenix Liveview is such a mind blowing set of software. It really is something different that works so well for the majority of web applications.
Think about it. You walk into a video store, you see 8-Minute Abs sittin' there, there's 7-Minute Abs right beside it. Which one are you gonna pick, man?
[0] https://www.theonion.com/fuck-everything-were-doing-five-bla...