pythonaut_16

Have you seen Elixir list comprehensions?

  iex> for n <- 1..4, do: n*n
  [1, 4, 9, 16]

Or for your example:

  iex> l = 1..3 # equivalent to [1,2,3]
  iex> Enum.reduce(l, fn item, acc -> acc + item end)
  # or
  iex> Enum.reduce(l, &(&1+&2)
  # or the built in
  iex> Enum.sum(l)
  # all return:
  6

https://elixir-lang.org/getting-started/comprehensions.html https://hexdocs.pm/elixir/1.12/Enum.html#reduce/2 https://hexdocs.pm/elixir/1.12/Enum.html#sum/1

None of which take away from your point though: it's definitely a different mental model than you use for Python/Go/Javascript.

Also a risk of polyglot environments. You can easily end up with teams that lack deep knowledge of the languages and libraries you're using.

Thanks for sharing!

We could certainly debate the objective merits of Elixir vs other languages (which seems to be the primary discourse in this thread and elsewhere) but hearing subjective developer experiences is also critical.

It doesn't matter if Elixir is objectively better or not, if lots of devs who are exposed to it are having a hard time it's worth asking why.

In addition to developers not wanting to expend additional effort to learn a new language or paradigm, I believe there are gaps in the ecosystem especially around medium-advanced topics.

Could you expand on what you mean by this?

Module design doesn't seem any harder than class design in JS or Python.

Do you mean the language is generally harder for non-developers? Or that Elixir is harder for JS/Python developers to pick up and write good code? Or something else?

Writing well designed Elixir code does seem to require a fairly different approach from most common OO languages, at least at a surface level. (Although IMO that's more because you can copy OO patterns you've seen before without thinking much about why they're good patterns than because good design in Elixir is much different from OO)

Do blue collar workers require healthcare from college educated people? Do they benefit when American industry is competitive on in the international marketplace?

We shouldn’t be leaving people behind but the idea is that we all benefit from an educated workforce.

There’s plenty of arguments to be made over the details but let’s not miss the big picture here.

My recollection of the details is fuzzy, but I think a common solution to this is connection draining. You set up your deploy to bring up the new instance and direct all new traffic to that one and then hold the old one open until all sessions/connections end.

Can't remember if/how that routing was accomplished in the BEAM (Erlang/Elixir VM). It's definitely possible but you might have to implement it yourself.

Wonder the Apollo dev or one of the other Reddit 3rd party apps would be willing to migrate or create one.

Do you have any recommendations for more resources like this?

I've had a hard time searching for patterns and tips for modeling common data/features for web applications.

However, be aware of potentially leaking your company's private or sensitive information when doing this.

Nothing you said negates the potential for leaking your company's private or sensitive information by submitting it to a third party.

Were the unhelpful docs written by ChatGPT? Otherwise your story doesn't support your conclusion.

It's more likely LLMs will result in better docs for some projects and worse docs for others.

I really hate how the wealthy benefit from my washer, dryer, dishwasher, Internet, air conditioning, access to a huge variety of food... When will the wealthy start passing the benefits of progress on to the rest of us?

We've got big problems in our economy and income inequality is certainly one of them, but it's asinine to pretend that most individuals in society have not benefitted from technological progress.

Unequivocally yes. Not every usage of a screen in education is beneficial.

But there are absolutely numerous use cases where being able to display graphics on a screen (or even better interactively) is a massive benefit. Think of any sort of science that's better shown with animation than just a static image on a page for example.

And yet the proliferation of screens capable of displaying information and graphics has been an absolute boon to education.

This is sort of what HTTP codes get at though.

The server doesn't know what you want to do with a 400 but it knows that the problem is with the request for example.

I don't disagree, but I don't think it's fair to lump AWS in with the rest of Amazon's side projects.

If we're comparing Amazon and Google you almost have to compare AWS to Google search since AWS is driving a huge part of their profits.

"Having engineering problems to solve is proof that you shouldn't try to do anything."

Why can't we just appreciate a creative solution to a problem?

What about a system where only some fraction of the ticket sale has to present matching ID?

Example 1: Limit of 6 tickets per purchase. I buy 6 tickets, I invite 5 friends. I show ID at the door and it doesn't matter which 5 friends I bring with me.

Example 2: Same deal, but instead we're allowed 1 "flex" ticket in case someone backs out. Or some proportion allowed as flex.

Obviously this still allows scalping, but it seems less attractive for a scalper to have to attend with the people they're scalping to. Especially if you make 50% of the group show ID.

Imagine saying this 80 years ago about any number of technologies that are cheap and commonplace today.

> the power of numbers

Maybe I'm misunderstanding you, but isn't that the point of democracy? If enough people agree with your view then that's what gets implemented. The point of the parent is that you can't let people with the loudest voices and most free time abuse the system.

That's more of a NIMY - Not in My Yard kind of thing.

I think the parent post is referring to the library example. At a certain point you don't get to keep the land around you from being used in any way other than it was exactly when you moved in.

Eminent domain is a different issue that should have a much higher barrier to use, and has likely been abused historically.

Google Takeout will let you export all of your data, mostly as JSON. There are some parsers for it on the web.

I thought it was fair given their oversimplification of what delivering messages at scale requires.

The point isn't that the Earthquake Detection isn't impressive. Why do we have to deny Google any credit here? Is it just because they're a big tech company?

IMO it feels like another "I could build Dropbox in a weekend" comment.

Be my guest to go build one then.

Oh but if you're truly committed you'll need to avoid Cloud computing resources, avoid Twillio, don't use any Google services, no Firebase Cloud messaging... You probably shouldn't use Android phones either...

And remember any delayed or failed messages put people's lives in danger...

Or we can just admit that Google as a whole had some impressive achievements here alongside the Earthquake team.

That's a narrow take.

Detecting an earthquake early and alerting millions of people quickly are both hard problems, and both had to be solved for this to work.

Much of the hard work on Google's side just happens to overlap with other use cases that they've already scaled.

Consider that no amendments are currently being held up by a small minority. Congress simply isn't proposing amendments. And most likely amendments on current issues would fail to get even a simple majority of states to ratify.

The hard truth is that most amendments that get discussed today are around issues with no level of national consensus.

This is either absurd or sorely uninformed. That the Bill of Rights was added later is essentially a procedural technicality.

The (lack of a) Bill of Rights was a major concern when the Constitution was drafted. It was passed with the promise that amending it with a Bill of Rights would be the first priority.

The Constitution was only passed without it so the convention wouldn't keep dragging on.

Ah, so still fully static vs. a SPA that uses REST or GraphQL. So then clients interact with it as static HTML/JS rather than hydrating it via Javascript.

Can you explain how Cloudflare Workers factor into hosting static pages on Cloudflare Pages vs hosting a React SPA on pages that talks to any other API?

Like are the workers just serving as your backend at that point? Or are they doing something more or different as well?

> But Not Strictly Open Source doesn't appeal much to HN crowd

I don't think this is true. "Open Source" But Not Really is what gets criticized here, such as Elasticsearch's new license.

Things that want to benefit from calling themselves open source while restricting user freedoms.

Source available on the other hand is exactly what it claims to be. It's more open than strictly closed source and less free than fully open source.

Could you elaborate on this pain point? How do you think serialization should work?