Back fired because of opus 5.5.
So now we get the real sol-6 as sol-6.1, and OpenAI will eat the cost to stay competitive.
This could be invalidated if sol-6.1 is the same speed as sol-6.
1,412 karma · joined November 10, 2014
Back fired because of opus 5.5.
So now we get the real sol-6 as sol-6.1, and OpenAI will eat the cost to stay competitive.
This could be invalidated if sol-6.1 is the same speed as sol-6.
Maybe you just write like an LLM.
RDF, OWL are existing formats for defining a schema
How will non-tech founders develop their product on this stack? That's a stack for developers to build the product.
This is a very hard problem, when you see a fragmented ecosystem its because players in the ecosystem have wide ranging and demanding requirements.
You will have to acquire your target customer when they are ready to setup this stack but before they have done so themselves. This would require very high brand awareness. Like "Oh I was going to setup on AWS but XYZ makes it so easy". Only a few companies have achieved this type of awareness in the devops space. Heroku comes to mind. None of them are indie-hacker projects.
Need to verify if it even knows what you mean by nothing.
Retrospective https://www.youtube.com/watch?v=suv76aL0NrA
https://www.remote.org/frederik/projects/railserver/history....
I think it got relatively lucky with the query, since tried a few variations, you.com and Perplexity and they all failed to find it.
How about a browser extension that scrapss Google results and asks GPT to summarise?
There are many prompts beyond summarisation that would be interesting, for example ask GPT to present conflicting point of views in the results.
They are answering why education is "so abstract and uninspiring", talking about the educational system specifically. Not peoples abilities. They are actually implying that people could understand if given the chance.
> The main difference between ARC and Nim GCs is that ARC is fully deterministic - the compiler automatically injects destructors when it deems that some variable (a string, sequence, reference, or something else) is no longer needed. In this sense, it’s similar to C++ with its destructors (RAII). To illustrate, we can use Nim’s expandArc introspection (will be available in Nim 1.4).
> This shows one of the main ARC features: scope-based memory management. A scope is a separate region of code in the program. Scope-based MM means that the compiler will automatically insert destructor calls for any variables which need a destructor after the scope ends. Many Nim constructs introduce new scopes: procs, funcs, converters, methods, block statements and expressions, for and while loops, etc.
> ARC also has so-called hooks - special procedures that can be defined for types to override the default compiler behaviour when destroying/moving/copying the variable. These are particularly useful when you want to make custom semantics for your types, deal with low-level operations involving pointers, or do FFI.
> The main difference between Rust and other languages is that it does some more (but not all [2]) safety checks at compile time rather than at runtime. It also allows you to avoid GC, but does not provide you any memory safety over GC. Rust's borrow checker allows you to statically prove that references are live [3]; a GC simply avoids deallocating any memory that has a live reference to it (on the other hand, a GC can ensure that references remain live even where this is hard or impossible to prove statically). The end result is the same with respect to memory safety (the reason some people want to avoid GC is for performance reasons, not memory safety).