songqin

Cards.fun | Software Engineers (Fullstack) | Remote only

We're digitizing pokemon cards and creating unprecedented financialization of card assets. We're a small bootstrapped team. Interested in those able to wield Claude Code effectively, and take a test-driven approach. Bonus points if you have any interest in tokenization of RWAs. Our stack is written in Rust, with a vanilla JS and templated HTML frontend.

this isn't true, tariffs are assessed within the US by the receiving firm, not on the sender's side. We run a business with a foreign supply chain and our suppliers have changed nothing, we just get an extra bill to pay to the government when our inventory arrives.

I can fill in the blanks in my head, but I doubt they are what you're thinking. Would you mind elaborating on the cause/effect you have in mind? It is difficult for me to imagine this in and of itself being successful. We would also need to solve the allocation of those collected funds, as in many countries it would likely go to welfare, defense, corruption, etc.

What do you specifically find deceptive about Trilogy? Just curious, as I see them around me a lot.

This is really cool. It is so snappy, and the tweakability and sound really does feel like a real synth.

The problem I see is the current async story is opt-out.

Surely this is only the case if you have picked asynchronous libraries to use?

I had understood your concern as wanting to avoid the complexity of asynchronous code execution in your codebase, I did not realize your concern is about writing very low level systems code. In that case, you are doing the right thing: libraries like ureq, minreq, Isahc, curl, and more all offer what you want.

It is unclear to me what you mean by keeping the community "in check". There are a lot of people who rely on and enjoy the async story, and they will continue to produce code that improves that story. Simultaneously, there are people who do not need that, and they are not hindered by this. People will build what they want and need. You've just picked some libraries from some of the biggest async contributors in the community and requested that they be kept in check so that you don't have to switch to a synchronous alternative, of which there are plenty.

Your comment touches on a few misconceptions I see a lot.

Firstly, `reqwest` exposes both an async and a synchronous API, allowing the developer to choose which one to use. They are largely interchangeable code-wise. [1]

Secondarily, and more broadly, async is possible to opt out of. You must understand that most web and network related libraries will be async by default for performance, because people who write in Rust and people who write web servers typically care greatly about performance. This is the intersection of those two groups. That being said, there are options outside of that ecosystem. [2]

If you truly want to use an asynchronous library without migrating your application to run entirely on an async runtime like tokio, you can run it inside of a synchronous function without much trouble. I've put together a playground link for you. [3]

1. https://docs.rs/reqwest/0.11.2/reqwest/blocking/index.html

2. Iron: https://github.com/iron/iron Rouille: https://github.com/tomaka/rouille

3. https://play.rust-lang.org/?version=stable&mode=debug&editio...

Anecdata: as a Texan from a rural town currently working in software in Seattle, I've had multiple experiences with this. People assume my political views or agenda far before they know me. Luckily I don't believe it has impacted my actual job search thus far.

what's wrong with the name?

This is my first "Show HN" submission here. This is an ANSI X12 EDI parser and generator for Rust. It has been already used commercially for multiple EDI pipelines and is able to handle any X12 document which is specification-compliant. It can both parse and output valid EDI documents while maintaining versatility to cover the entire spec. There is also a `loose_parse` mode which is less strict on the spec, in case the incoming data is slightly malformed.

I hope this crate helps some companies stuck with antiquated EDI pipelines eliminate some old tech cruft.