Everyone talks about Websockets for pushing real time data to the browser. This article highlights some of its drawbacks. I use Server Sent Events (SSE) instead. A lot of the problems the author of the article faced are solved with SSE. Also, SSE scales way better than polling all the time.
I didn't see anything in the article about battery capacity or the density. This (with the other info in the article) would tell us if this is groundbreaking or not.
It is not true that Ollama doesn't use llama.cpp anymore. They built their own library, which is the default, but also really far from being feature complete. If a model is not supported by their library, they fall back to llama.cpp. For example, there is a group of people trying to get the new IBM models working with Ollama [1]. Their quick/short term solution is to bump the version of llama.cpp included with Ollama to a newer version that has support. And then at a later time, add support in Ollama's library.
Not always true! Your statement is only true when the running clock's speed is the same as time. Thus, regular time and the clock's time will never meet.
If the clock is running faster than regular time, it will at point catch up to regular time and thus be correct for a split second. If the clock is slower than regular time, regular time will catch up to the clock and the clock will be right for a split second.
Just last week I was looking into OptaPlanner [1] and MiniZinc [2]. OptaPlanner even has a real-time/continuous optimization mode. There are a whole bunch of other solutions, but these were the most interesting to me.
I wonder why Google didn't just go with an off the shelf solution and integrate it instead of building their own solution?
I hate articles that talk negatively about GPS when they really mean navigation software. GPS allows you to determine where you are. Navigation software tells you where to go.
Two examples: GPS does not spy on you and tracks your every movement. But the navigation software might. GPS doesn’t tell you to go down the wrong road. But the navigation software might. Etc.
A few years ago, I worked on an app where some of the state was kept in the session and some was on the url as GET params. We ran into an issue where some browsers would only accept urls that were less than 1024 chars long. Is that still an issue today?
I've been watching his videos too for the last 6mo or so. If you like them, you should watch his friend's videos on SerenityOS as well, Linus Groh [1]. He does a lot of stuff on LibJS and LibWeb libraries. I think he is the lead developer for those because every month when Andreas does the monthly summary video of changes in the OS, he defers to Linus to talk about the browser changes.
> the biggest challenge would be the right of way and litigation
I totally agree. I live in SoCal and there are some infrastructure projects that took forever (ie creating the I105 and finish connecting the I210), or will probably never get completed (ie. finish connecting the I710 and California High Speed Rail) all because of right of way issues and lots of law suits.
I think developers using the Arduino platform on the ESP32 are mostly just using one core. Developers using the Espressif's SDK are more likely to use both cores.