indexerror

Its for purchasing AI summaries. By default each user gets 1000 article summaries to begin with, which should suffice for several months for most users.

Initially I didn't want to put any in-app purchases but decided to add it to prevent abuse.

Glad that you are liking the app! Import/Export feature for bookmarks is on my roadmap.

OpenAI just released Codex, which is basically the same as Claude Code.

These datasets would definitely have a lot of Text => Sketch pairs as well. I wonder if its possible to extrapolate from Text => Sketch and Text => Image pairs to improve Sketch => Image capabilities. The models must be doing some notion of it already.

I have used it for quite sometime. The v2 works fairly well now but still not _great_.

Can this be used to clean podcast audio? I don't see a reason why it can't be...

That is an interesting observation. I wonder what percentage of the training text data for LLMs contains proper dashes, since a large part of it is user-generated content.

People are coming to ChatGPT with an intent to type. Its much harder to introduce text-based interface to otherwise click-based interfaces because of the friction. Thats why chatbots often fail to gain adoption, because they are a byproduct of the product team being lazy and not thinking through the UX.

Thats why I go for the nuclear option (the one that requires higest attention, like account cancellation) when presented with a list of options by a bot. More likely to get a person that way.

I have always assumed that I could just kick the window to break it open in a situation like this.

This is what we need.

Q4 comes out to be ~26GB but Apple doesn't let you load it on a 32GB Mac machine because they put a limit on the max usable unified memory at ~21GB (`device. recommendedMaxWorkingSetSize`) [1]. So for Q4 Mixtral MoE you'd need a 64GB Mac machine unfortunately.

Unless you use this hack [2].

[1] https://developer.apple.com/forums/thread/732035

[2] https://github.com/ggerganov/llama.cpp/discussions/2182#disc...

Pretty Cool!

Well it was an 'Open Secret' outside of Meta as well, wasn't it?

Jetbrains IDEs have a local history feature that provides snapshots with diffs and allows partial rollbacks.

I only use it when experimenting with different approaches.

Mostly I only use the "Local Changes" tab in the Git panel that shows the diff compared to the last commit, or "Compare with branch" to see the overall changes relative to the base branch.

A professor of mine who used to work at ISRO says that the place is choke full of bureaucracy.

You can do this with Axios too:

  interface IResponse {
    foo: string
  }
  
  async function doSomething() {
    const reponse: AxiosResponse<IResponse> = await Api.call()
    ...
    // or you can use AxiosPromise<IResponse> without the await
  }

Very cool product.

From the /product page:

> ...It profiles applications using the Linux perf_events subsystem and interfaces with a target application's machine code through the Linux ptrace system call. When optimizing a program, it loads a code cache into the target program's address space...

That paper is for school exams. Here is one of the two papers for IIT-JEE: https://drive.google.com/file/d/0B14M4ID1Z9cQdWZSaWhSejd1Qlk...

This is the approach that Kotlin takes (albeit with boxed primitive types). Float, Integer, Long - all are subtypes of Number.

> It's been a year and a half since I took a course on this

Can you please recommend a MOOC/resource for learning more about this?

> Elm exists solely to excel at front-end web development.

Except that it unfortunately falls short of that.

From page 10-11 of [1]:

> A shared resource provides a way to build a real counting thread with a negligible overhead compared to a message passing approach. This already raised concerns with respect to the creation of a high-resolution clock [19]. In this method, one worker continuously increments the value of the buffer without checking for any events on the event queue. The main thread simply reads the current value from the shared buffer and uses it as a high-resolution timestamp.

[1] https://gruss.cc/files/fantastictimers.pdf