Leads to really fun statements like "there exists a proof that all reals are equal to themselves" and "there does not exist a proof for every real number that it is equal to itself" (because `x=x`, for most real numbers, can't even be written down, there are more numbers than proofs).
> The hardware supplier that we use no longer has the battery. Therefore, we cannot sell you the battery. What we can do is provide you with the part numbers so you can source it elsewhere. If you're considering sourcing the battery for the Darter Pro 5 from another supplier, please note that the model number for the battery is N150BAT-4, and the original part number is 6-87-N15ZS-51E01. Third-party battery sellers may display one or both of these numbers and might also list other compatible part numbers that are suitable for the same model.
It's actually a Darter Pro 6, but the battery part number is correct in that text.
You can not purchase this battery, it no longer exists. There are a few sketchy websites which say that they sell it, but they will cancel your order a few days after placing it and tell you that there is "lack of material".
AMD Strix Halo (a consumer mobile processor) has theoretical support for 256GB/s of memory bandwidth (quad-channel, 8000 MT/s LPDDR5X, must be soldered, supports 128GB at most).
Each planet has its own gimmick which throws a spanner into standard builds in its own unique way - one planet is essentially a farm where your factory is growing and processing fruits, which will rot and spoil if they aren't processed immediately -- so you need to design a factory which processes small packets at high speed without any buffering.
A well done PWA will absolutely beat SSR on a shitty connection if it's actually an app.
Cache-control immutable the code and assets of the app and it will only be reloaded on changes. Offline-first and/or stale-while-revalidate approaches (as in the React swr library) can hugely help with interactivity while (as quickly as possible) updating in the background things that have changed and can be synced. (A service worker can even update the app in the background so it's usable while being updated.) HTTP3/QUIC solves the "many small requests" and especially the "head of line blocking" problems of earlier protocols (though only good app/API design can prevent waterfalls). The client can automatically redo bad connections/requests as needed. Once the app is loaded (you can still use code splitting), the API requests will be much smaller than redownloading the page over and over again
Of course this requires a lot of effort in non-trivial cases, and most don't even know how to do it/that it is possible to do.
> HTTP3/QUIC solves the "many small requests" and especially the "head of line blocking" problems of earlier protocols (though only good app/API design can prevent waterfalls).
I love the autocomplete, honestly use it more than any other AI feature.
But I'm forced to write in Go which has a lot of boilerplate (and no, some kind of code library or whatever would not help... it's just easier to type at that point).
It's great because it helps with stuff that's too much of a hassle to talk to the AI for (just quicker to type).
I also read very fast so one line suggestions are just instant anyway (like non AI autocomplete), and longer ones I can see if it's close enough to what I was going to type anyway. And eventually it gets to the point where you just kinda know what it's going to do.
Not an amazing boost, but it does let me be lazy writing log messages and for loops and such. I think you do need to read it much faster than you can write it to be helpful though.
reply