> Having said all this: nobody should be using crypto/fips140 unless they know specifically why they're doing that. Even in its 140-3 incarnation, FIPS 140 is mostly a genuflection to FedGov idiosyncrasies.

What should folks use then?

crypto/, not crypto/fips140.

To nitpick, there is no special crypto/fips140 package. (Ok, there is, but it just has an Enabled() bool function.)

FIPS 140-3 mode is enabled by building with GOFIPS140=v1.0.0 (or similar, see https://go.dev/doc/security/fips140), but it shares 99% of the code with non-FIPS mode.

Still, your message is right, just GOFIPS140=off (the default!), not GOFIPS140=v1.0.0.

Not a nitpick! I was just wrong!

That's a nice solution when managing a platform. You can "upgrade" all your teams, and/or easily detect they have upgraded.

If you have this kind of revenue, you don't approach anyone, they approach you.

I tried downloading this for MacOS Silicon and was told the dmg was damaged :/ Guess I'll wait a little bit for things to iron out.

It's not damaged, read some other comments about the workaround for this.

Given that your Remix version has been ~2 years in development by X number of developers, what are the other expected outcomes? It sounds like potential SEO performance is unknown? Is the development team happy with the choice? I can't recall working somewhere that allowed us to work on a project for two years and not release to production, how did you get business buy in?

You don't need buy-in when they tell you to do it!

Not OP but I've definitely seen a "leadership has decided on a rewrite into a new technology" project not ship for a couple years. I doubt it ever shipped, I didn't stay around to find out.

The other outcomes are a redesign and more configurability plus a bunch of new features. It wasn't really an apples to apples comparison. The non-iFrame version was more of a 1.1, where the new thing we are building is a 2.0. Based on some other projects, I do suspect it would have gone faster if we built it on the old stack.

The development team made the choice to go with Remix (well, the tech lead and VP of engineering). No one had used this tech before. We have subsequently talked about whether it would have been better to do the whole thing with Rails + Hotwire. We have been using this approach elsewhere in our stack, and it seems to be a lot conceptually simpler than rendering JS server side and then hydrating it.

WebAI | Software Engineers, Systems Engineers, ML/AI Engineers | Austin, TX (US), Grand Rapids, MI (US), or Remote (Anywhere) | REMOTE or ONSITE | Full-time or Contract | $150k-$250k base + equity | https://www.webai.com/

WebAI is building the future of Human-AI interaction and we’re a community committed to building the future of decentralized artificial intelligence. We believe that democratizing AI is key to unlocking its full potential and creating a better world for all. Our new product Navigator enables users to create custom AI models to meet their needs, while our WebAI Intelligence Network is critical infrastructure required for a decentralized AI future.

Senior and Staff roles available.

Desirable experience for our various roles:

  - Full-stack Python, Go or Rust

  - iOS (Swift)

  - P2P, encryption, or cryptography

  - Managing multi-cloud and/or on-prem infrastructure

  - Distributed training

  - Custom DNN architectures (pytorch/tensorflow/mxnet/burn)

  - Optimization via quantization/compression techniques

Apply here: https://boards.greenhouse.io/webai (company name change in progress from Iris to WebAI)

WebAI | Software Engineers, Systems Engineers, ML/AI Engineers | Austin, TX (US), Grand Rapids, MI (US), or Remote (Anywhere) | REMOTE or ONSITE | Full-time or Contract | $150k-$225k base + equity | https://www.webai.com/

WebAI is building the future of Human-AI interaction and we’re a community committed to building the future of decentralized artificial intelligence. We believe that democratizing AI is key to unlocking its full potential and creating a better world for all. Our new product Navigator enables users to create custom AI models to meet their needs, while our WebAI Intelligence Network is critical infrastructure required for a decentralized AI future.

Senior and Staff roles available.

Desirable experience for our various roles:

  - P2P, encryption, or cryptography

  - Managing multi-cloud and/or on-prem infrastructure

  - Distributed training

  - Custom DNN architectures (pytorch/tensorflow/mxnet/burn)

  - Optimization via quantization/compression techniques

  - Rust

Apply here: https://boards.greenhouse.io/webai (company name change in progress from Iris to WebAI)

It's possible that candidates are getting shuffled around, as some of the Meta recruiters themselves have been laid off. I know multiple people that were/are in the Meta process that this happened to. Takes a few weeks for the new recruiter to go through their double/triple work load of candidates and schedule.

What would happen if you paid for unpaid leave and didn’t use it?

Paid back to you at the end of each year like it never happened. I don’t think it happened much at all.

I could also work and bank comp time up to 80 hours (no overtime, 99% of the time). Use comp time like vacation time but no pay.

Thank you for this example; it wasn't clear to me reading the article, but this is the main problem I was hope being solved. Will make writing tests much smoother.

I have a small Deno powered bot that generates Shopify listings from some inputs. It’s been running for a few months with no crashes or restarts.

I think it really comes down to what APIs or packages you need. I have had trouble with projects such as Prisma and wouldn’t do that in production as the generated output is slightly different for some reason (haven’t had time to inspect).