I wonder if you could make it multiplayer and then get the effects of time dilation?
In my imagined world I also wanted to explore speeds above the speed of light. You could just stick to galilean transformation, take a very low speed of light and go from there. The world you get should be pretty bizarre.
I suppose the problem in multiplayer is that everyone has the same wall clock time, so you couldn't easily have consistent time dilation and related effects such as the twin paradox.
“30 hours of unattended work” is totally vague and it doesn’t mean anything on its own. It - at the very least - highly depends on the amount of tokens you were able to process.
Just to illustrate, say you are running on a slow machine that outputs 1 token per hour. At that speed you would produce approximately one sentence.
(First of all: Why would anyone in their right mind want a Slack clone? Slack is a cancer. The only people who want it are non-technical people, who inflict it upon their employees.)
Is it just a chat with a group or 1on1 chat? Or does it have threads, emojis, voice chat calls, pinning of messages, all the CSS styling (which probably already is 11k lines or more for the real Slack), web hooks/apps?
Also, of course it is just a BS announcement, without honesty, if they don't publish a reproducible setup, that leads to the same outcome they had. It's the equivalent of "But it worked on my machine!" or "scientific" papers that prove anti gravity with superconductors and perpetuum mobile infinite energy, that only worked in a small shed where some supposed physics professor lives.
Their point still stands though? They said the 1 tok/hr example was illustrative only. 11,000 LoC could be generated line-by-line in one shot, taking not much more than 11,000 * avg_tokens_per_line tokens. Or the model could be embedded in an agent and spend a million tokens contemplating every line.
If anyone is struggling with keeping up with EU regulations, we built an AI powered platform that helps companies navigate this complex world. You can find it at: https://fx-lex.com
I do think that the amount of regulation is proportional to the complexity of the society. While you can over or under regulate, the general future trend will be more regulations.
In my mind, Gemini 2.0 changes everything because of the incredibly long context (2M tokens on some models), while having strong reasoning capabilities.
We are working on compliance solution (https://fx-lex.com) and RAG just doesn’t cut it for our use case. Legislation cannot be chunked if you want the model to reason well about it.
It’s magical to be able to just throw everything into the model. And the best thing is that we automatically benefit from future model improvements along all performance axes.
Gemini models run in the cloud, so there is no issue with hardware.
The EU regulations typically include delegated acts, technical standards, implementation standards and guidelines. With Gemini 2.0 we are able to just throw all of this into the model and have it figure out.
This approach gives way better results than anything we are able to achieve with RAG.
My personal bet is that this is how the future will look like. RAG will remain relevant, but only for extremely large document corpuses.
We haven't tried that, we might do that in the future.
My intuition - not based on any research - is that recall should be a lot better from in context data vs. weights in the model. For our use case, precise recall is paramount.
Thank you!
The main website (https://www.myphotos.site) was built my co-founder Or using Webflow. He's a real pro when it comes to websites - see more of his work here https://gambit.design/
The user galleries and the editor dashboard are built using Next.js, Typescript, Tailwind, and Vercel. For the masonry, we first tried a few libraries (such as https://www.npmjs.com/package/react-masonry-css) but ended up writing our own because all the libraries we tried didn't handle proper column-height distribution.
I kinda see the point though. State management is bundled with frontend development in such a way that even for simple projects it almost seems like necessity for most people.
Don't use things that you are not hundred percent sure you need. Blockchain is a robust solution for high complex state management issues but most people will never end up using it for its full potential. Even if you did there often are alternatives that performs much better for your need.
People will try to bend their projects to meet the blockchain need rather than just use it when you need to use it.
I think it attempts to paint them as overhyped. If the target would be to put down blockchains, the page would simply be a "No". But it's true that we throw blockchains at things that don't need a blockchain.
Any kind of atmospheric studies (or studies of currents) would indeed be an archetypal example of a chaotic system -- although much simpler dynamical systems would exhibit chaotic behaviors.
https://requestfx.com