If the framework is used, eventually there will be 3rd party lib adding new features (from the top of my mind, maps), and someone will need to write the bridging with the native SDK. It means the bridge will most likely need to be written in objective-C instead of Swift
I actually hope to find better answers here than on cursor forum where people seems to be basically saying "it's you fault" instead of answering the actual question which is about trust, process, and real world use of agents..
So far it's just reinforcing my feeling that none of this is actually used at scale.. We use AI as relatively dumb companions, let them go wilder on side projects which have loser constraints, and Agent are pure hype (or for very niche use cases)
Luc Julia (one of the main Siri's creators) describe a very similar exercice in this interview [0](It's in french, although the au translation isn't too bad)
The gist of it, is that he describes this exercice he does with his students, where they ask chatgpt about Victor Hugo's biography, and then proceed to spot the errors made by Chatgtp.
This setup is simple, but there are very interesting mechanisms in place. The student get to learn about challenging facts, do fact checking, cross reference, etc. While also asserting the reference figure of the teacher, with the knowledge to take down chat gpt.
Reminded me of this job offer from the city [0], 2 years ago! Seems it paid off then!
Searching for this post, I ended up scrolling through the HN result of "new York rats" [1]. It paints quite a story! Couldn't imagine it was such an intense topic (running for more than a decade!)
A pro could have been an extra narrative about carbon footprint savings.
I'm surprised it hasn't been raised when talking about saving 2Tb/year only for React. It represents costs, which doesn't seem to be an issue, but also computing power and storage. (Event with a higher/longer computing power due to slower compression, it's done once per version, which isn't really comprable to the amount of downloads anyway)
Hard to calculate the exact saving, but it would represent a smaller CO2 footprint..
There're few benefits that comes with packaging it into an electron wrapper, including:
- making sure it works on all platforms independently of the browser you use (because it comes packages with chromium)
- having access to more API from the platform. Although the UI is rendered through a WebView, there's still native code running, that you can hook back into your app. That can be useful to either offload some logic to native, or access native API that you pilot from the WebApps
- having a shortcut icon to open you app in the system (although this is getting obsolete now that Chrome and Safari offer "Add to Desktop" functionally)
Many people in the PR mentioned the complexity that Typescript brings. But wasn't it an over simplification from the language from the beginning?
I mean, in the context of JS 10 years ago, Typescript in indeed overly complex, but in the context of today's JS running servers and very complex apps at scale, it just seems sane to back up the code with types, just as most other languages would do..
In my opinion it's now a required complexity to build up a lib with some stability and a safe DX for contributors
3DImka, who is being most of hidden-3d.com, is constantly pushing the boundaries of stereograms!
I highly recommend having a look at some of his best creations on deviant art [0], particularly his technic of matching outlines with the final 3d result [1], or his experiments with transparency [2].
Most of autostereograms are meant to be seen wall-eyed, instead of cross-eyed [0].
With wall-eye, you shift the convergent point being what you're seeing, while with cross-eye you shift it before.
So it creates the exact opposite 3d. Watching a stereogram meant to be seeing wall-eyed, cross-eyeing you'll see an upside down 3d. Some stereogram are mean to be seen cross-eyed though, which is considered easier to see.
This is definitely an issue which is well underestimated!
Portugal (e.g in Covas de Barroso) [1] and Spain (e.g. in Cáceres) [2] are facing huge pressure to settle for lithium mines, without much consideration for the social and ecological impacts on those regions...
It is still considered as a green energy, simply because we decide to forget about part of the process.
Just as we did for gas, and plastic.
Energy price should take in account all the impacts (recycling included), the avoid being considered as a magical solution, and rush blindly toward the next crisis..
They didn't pay for the processing.. We ignore a lot of cost when selling a product, and particularly the cost of recycling, which start to be a huge issue taking in account the amount of waste produced..
Wow I feel I just came out of a cave, to discover only now about Worldcoin..
Apart from the arguable concept itself, I'm genuinely wondering why betting on yet another scanning device, instead of using fingerprint scan, which is now available on most smartphones ?
Is it that much more reliable that it's worth going through the pain of engineering a new hardware ?
Finally, how they could expect any other reactions than doubt, fear, and reject, out of this solution, while fingerprint and face detection already go through so much ethical issues ?
Good ol' days spirit