ronanyeah

- The SAT solver is implemented using the Rust crate `varisat` - The Rust program is provided to the webapp as WASM

If the low hanging bugs can't even be triaged, what hope is there for any future innovation? ie, the countless unsupported browser APIs

It is clear that Elm is understaffed, to say the least.

Honestly, even just a tweet from the BDFL twice a year saying 'I still care about this' would be something.

It's impossible to evangelise something when the creator has seemingly taken his ball and gone home.

The idea that enterprise should use Elm is laughable.

People are constantly asking for a pulse:

https://discourse.elm-lang.org/t/is-elm-browser-still-mainta...

https://discourse.elm-lang.org/t/request-elm-0-19-2-any-upda...

It's pretty sad. I personally believe the ecosystem would be in a much more vibrant state today, if the creator had formally abandoned the language at any point in the past, as there are many who would pick up the torch.

It is telling that several people who could once have been considered 'core team' are now building their own languages:

https://gren-lang.org/

https://www.roc-lang.org/

https://www.derw-lang.com/

Interesting, got any repos written in this style?

> Please don't post shallow dismissals, especially of other people's work.

I think you are violating this guideline.

'actually the murder rate isn't that bad'

It is possible to tolerate wealth inequality, while not tolerating mentally ill drug addicts terrorising the public.

Americans clearly have very low expectations for their standard of living.

As demonstrated by the amount of insane 'actually the murder rate isn't that bad' comments in this thread.

I've been using render.com to host Rust+sqlite stacks recently, and I'd like to leverage this.

Should my Rust server be running sqld, and I would add a passthrough endpoint through its existing http api to the sqlite?

Or alternatively, should I be using sqld locally to access my sqlite instance through SSH or something?

I think personal experience with multiple paradigms is essential for a developer to decide which one they prefer.

The opinions of programmers who have only used one paradigm are less than worthless, since they are demonstrating a basic lack of curiosity and lack of willingness to invest in their craft.

You can always find excuses not to learn.

> They make a significant portion of all US voting machines.

> Just quadrupled their staff to make a voting machine then fired them all.

Fascinating.

This person has clearly never had a job outside.

I like this perspective: https://twitter.com/cdixon/status/1440026949838069763

For example, predicting Airbnb or Patreon in the early days of HTML/CSS/JS would have taken a lot of foresight and vision.

There were plenty of people in 1995 who did not understand the utility of HTML. That is the nature of revolutionary technology.

Web3 is like knowing HTML in 1995. Act accordingly.

Yeah Solidity has many resources and is worth learning. Solana is another smart contract platform which uses Rust, and Rust is a fantastic language, though it is tough.

Both ecosystems use Node.js for scripting/tests/frontend so that is going to be advantage to learn.

A good progression might be:

  - Modern JS / Node.js
  - Solidity / Ethers (https://docs.ethers.io/)
  - Rust
  - Solana / Anchor (https://project-serum.github.io/anchor/getting-started/introduction.html)

Look into web3/blockchain/NFT technology, most of it has been around less than 2 years so experience is less of a hard requirement than in other fields of software engineering.

I would like to hear some chaos stories.

I would personally recommend Elm for production use after 3 years of development with it.

I regularly engage in refactoring efforts that would be prohibitively time consuming in React, which I also have production experience with.

Huawei has already made some 'careless mistakes': https://www.zdnet.com/article/huawei-denies-involvement-in-b...

Check out elm-ui.

https://korban.net/posts/elm/2019-11-17-elm-ui-introduction/

I come from a Node.js background and picked up Rust about a year ago, after dabbling with Haskell, Elixir and Purescript.

---

Things I like:

- Modern type system. Sum types, Option type etc

- Strict compiler. If it compiles, it works.

- Great error messages.

- Mature package tooling. Cargo is at least as good as npm.

- Mature GraphQL packages.

- Decent cloud support. Github actions, Container guides.

---

I've been running it in production for a while, usually as a remote schema for Hasura: https://github.com/ronanyeah/rust-hasura

Deploy pipeline:

- Push to github

- Github action builds binary

- Github action pushes binary to AWS ECS in a container

- This triggers a rebuild of the AWS Fargate service which restarts with new Rust code