I agree with you. In B2B SaaS you don't sell the software, you sell your expertise in a specific domain and the responsability you take for owning that expertise. The fact that the development costs are nearly zero will make them more valuable and more protifable

Development has always been a small fraction of B2B SaaS expenses after the first couple of years anyways

I had a C64 and learned programming on it. I guess it's a question of destiny at this point :)

great idea! just ordered one, I will give it a try

First of all, great job! I think the inference will become more and more important.

That being said, I have a question regarding the ease of use. How difficult it is for someone with python/c++ background to get used to zig and (re)write a model to use with zml?

Hi co-author here. Zig is way simpler than C++. Simple like in an afternoon I was able to onboard in the language and rewrote the core meat of a C++ algorithm and see speed gains (fastBPE for reference).

Coming from Python, the hardest part is learning memory management. What helps with ZML is that the model code is mostly meta programming, so we can be a bit flexible there.

We have a high level API, that should feel familiar to Pytorch user (as myself), but improves in a few ways

pretty easy, usually the hardest part is figuring out what the python code is doing

> It started by accident, with the original llama weights being leaked by two separate employees.

This is not true. Meta Fair has been built on openness from day 1. We published many papers and open-source d many repositories to reproduce the work

On a side note, if you are running something for days or weeks you should implement checkpointing anyways. I have no idea if matlab allows that for internal operations

This is the real answer

The actual problem OP has is that their simulation can't be restarted if something goes wrong

These CRUD apps need complex business rules, requiring expertise in the domain and making them configurable on the application level for customer while trying to keep the app not bloated.

Scaling is not the only challenge engineers face, but somehow it's the one that is mostly praised.

They also need to respond to customer requirements, which IG never needed to do while they had no actual customers. And as soon as fun was up and IG had actual customers (spoiler alert, advertisers) what a surprise 3 devs was not enough.

They also need to quickly respond to downtime, because unlike IG if some of those CRUD apps go down in B2B world you are often losing customers actual money not just ad views

Ad views translate to actual money??

Sure. If you are full on marketer you can say "not see an ad for service" is as bad as "service does not work".

But anyway there was never a period where Instagram had a tiny 3 dev team and handled ads at the same time. 3 devs only worked back when there were no customers, no ads, no profits and no real responsibilities.

same. I have these exact urls bookmarked for years

For popups I blame the website developer, I read these as "let me give you a small annoyance to push a personal opinion" => ctrl+w

To be accurate, IE was not hated by "end-users". It was hated by web developers (understandably) reluctant to support non-standard apis and by informed people.

It was also hated by many end users.

If the API was used by 90%+ of the internet, then it was the standard.