4 47 80

Irene Solaiman

irenesolaiman

AI & ML interests

None yet

Recent Activity

liked a dataset about 10 hours ago

nbroad/hf-inference-providers-data

liked a Space 26 days ago

hugging-science/science-release-map

liked a Space about 1 month ago

Molbap/transformers-modular-refactor

View all activity

Organizations

liked a dataset about 10 hours ago

nbroad/hf-inference-providers-data

Viewer • Updated about 10 hours ago • 1.53k • 5.1k • 1

liked a Space 26 days ago

Science Release Heatmap

🔥

Browse AI models and datasets for scientific research

liked 2 Spaces about 1 month ago

Transformers Modular Refactor

😻

Interactive analyzer for modular models in Transformers lib

Transformers Timeline

🤗

Interactive timeline to explore the 🤗Transformers models

upvoted an article about 1 month ago

Article

Tricks from OpenAI gpt-oss YOU 🫵 can use with transformers

Sep 11

• 157

liked a Space about 1 month ago

220

Inference Playground

🔋

Set theme for Hugging Face Playground

reacted to abidlabs's post with ❤️ about 1 month ago

Post

3714

Open Models vs. Closed APIs for Software Engineers
-----------------------------------------------------------------------

If you're an ML researcher / scientist, you probably don't need much convincing to use open models instead of closed APIs -- open models give you reproducibility and let you deeply investigate the model's behavior.

But what if you are a software engineer building products on top of LLMs? I'd argue that open models are a much better option even if you are using them as APIs. For at least 3 reasons:

1) The most obvious reason is reliability of your product. Relying on a closed API means that your product has a single point-of-failure. On the other hand, there are at least 7 different API providers that offer Llama3 70B already. As well as libraries that abstract on top of these API providers so that you can make a single request that goes to different API providers depending on availability / latency.

2) Another benefit is eventual consistency going local. If your product takes off, it will be more economical and lower latency to have a dedicated inference endpoint running on your VPC than to call external APIs. If you've started with an open-source model, you can always deploy the same model locally. You don't need to modify prompts or change any surrounding logic to get consistent behavior. Minimize your technical debt from the beginning.

3) Finally, open models give you much more flexibility. Even if you keep using APIs, you might want to tradeoff latency vs. cost, or use APIs that support batches of inputs, etc. Because different API providers have different infrastructure, you can use the API provider that makes the most sense for your product -- or you can even use multiple API providers for different users (free vs. paid) or different parts of your product (priority features vs. nice-to-haves)