Higher volume legal actions can only be successful as "peer-to-peer". If it goes through a courtroom, there is no way they can handle this kind of volume(even with AI tools). Imagine that the CEO is informed there are 20 new legal actions and the first court hearing will start 10-20 years from now when the CEO will not be part of the company anymore.
> But file syncing is a “dumb” protocol. You can’t “hook” into sync events, or update notifications, or conflict resolution. There isn’t much API; you just save files and they get synced. In case of conflict, best case, you get two files. Worst — you get only one :)
Sync services haven't evolved much. I guess, a service that would provide lower APIs and different data structures (CRDTs, etc.) would be a hacker's dream. Also, E2EE would be nice.
And if they closed the shop, I would have all the files on my devices.
This looks cool for v1! The only problem I see is most devices don't have much RAM, so local models are small and most requests will go to the servers.
Apple could use it to sell more devices - every new generation can have more RAM = more privacy. People will have real reason to buy a new phone more often.
I don't see any explanation for why they trained 8B instead of 7B.
I thought that If you have a 16GB GPU, you can put 14GB(7B*16bits) model into it, but how does it fit If the model is exactly 16GB?
The progress is insane. A few days ago I started being very impressed with LLM coding skills. I wanted Golang code, instead of Python, which you can see in many demos. The prompt was:
Write a Golang func, which accepts the path into a .gpx file and outputs a JSON string with points(x=tolal distance in km, y=elevation). Don't use any library.
You can run Gemma and hundreds of other models(many fine-tuned) in llama.cpp. It's easy to swap to a different model.
It's important there are companies publishing models(running locally). If some stop and others are born, it's ok. The worst thing that could happen is having AI only in the cloud.
Agree. Spinning out the FSD and Optimus teams wouldn't accelerate progress on the new models. Also, they will make more money from humanoids than car robots.
The main problem with HTML/CSS/JS is programmers want more than these languages offer. With WASM you can pick up language(must compile to .wasm) that fits your use case best. This is the freedom most programmers want.
There will always be programmers who will draw their custom buttons(instead of modifying DOM from WASM) and ignore accessibility. They can do this with JS as well, but most of them don't.
Nice project! I love WASM. It's designed to be sandboxed and portable from day one. I wish WASM was invented instead of Javascript in the 90s. WASM will eat the world.
What I hope most is endurance. There are many programs that we are not able to run anymore. The best examples are probably older games. I hope WASM will change that, although I'm a little bit nervous about adding new features, because simple specs have a higher chance of surviving, but the future of binaries looks exciting.
One of the biggest risks right now is viruses created by transformers trained on known viruses and anti-virus binaries and databases.
Humans created relatively simple viruses which took down hospitals, etc.. Transformer can make new "super" viruses and keep fighting the anti-viruses/firewalls in real-time with high-quality custom attacks.
"we were pretty impressed with the overall performance on offer, despite being limited to a 65 TDP limit. Although power consumption on the CPU package was around 90 W at full load, this is still considerably lower than other processors the trio of 65 W Ryzen 7000 chips was pitted against."
This is from the Conclusion page. Still pretty impressive.
Sure developers have a hard time handling all that HTML, CSS, Javascript and connections(DOM, etc.) between them, but I see a much bigger problem in browsers. There are actually only a few browsers and most of them are based on chromium(or Webkit). Why? Because web standards are huge!
Their complexity is so big, that even great programmers have a hard time creating browsers from scratch. The latest example of this is probably Ladybird[0].
Andreas Kling and others have worked on it for years("Just under 1000 days for a bunch of hackers to build a new JavaScript engine"[1]) and they know it will require way more time to just catch up the Chrome[2].
A year ago I started to build SkyAlt[3], which doesn't have anything to do with the web. It's not just a browser, but also an IDE where you can create apps with few lines of code or just drag and drop stuff on canvas.
It's written in C and it's only 25K LOC. Compiling takes a few seconds and binary is under 1MB.
There are tons of features that need to be built, but I like its simplicity(relative to the web).
Yep, this is what I meant, thanks for the sources.
Although, I'm not sure about that "then sinking into the water" part. There are big LO2 and methane tanks and If they are empty enough and closed, both Starship and Booster shouldn't sink. I guest, we'll see it soon.
In 2019, Elon tweeted[0] that the price of one Raptor engine is under $1M with the goal going under 250K for the next version. Any recent info where there are now?
I'm still surprised they moved to this orbital fly so quickly without doing more tests. Going from 3 engines to almost 30 is crazy. Also, If I understand it right, both booster and starship will end up in the ocean. I hope they will be able to reuse at least a few engines.
[0] https://github.com/ggerganov/llama.cpp#web-server