I do this. Ollama makes it very easy - just pull the model you want. The great thing is the ability to test them in the same tasks, there's a huge difference in comparable models.
You can set it up in your editor of choice - I use Zed, and it's just listed as one of the providers you can choose.
Yes indeed! I'm not surprised there's some difference. One thing I learned doing this is that there's a lot of choices to make when selecting the best icon.
For example, some sites have SVG icons, which are usually superior in both file size and in scalability (compared to raster formats), but if using them in a mobile app in React Native, it would require an additional step to integrate SVG images.
Whoa, I hadn't thought of a sprite sheet, but that's a great idea actually. It shouldn't be too hard to generate one of these. How many favicons in one sheet are you thinking?
I was working on an app, and in it, we wanted to render an icon for links from meeting invites. This turned out to be quite a pain!
I found other things that could return icon data, but alas they were all JSON APIs. I didn't relish the idea of fetching an endpoint for each and every website icon I needed to load (and write glue code to render the best icon out of the bunch).
You'd think favicons are as simple as loading "example.com/favicon.ico" but there's a lot of subtleties to it.
First, favicon.ico's are often really low res – there's often higher res icons available via tags in the HTML or through the manifest file.
Second, what if the hostname is unreachable or if there is no favicon at all?
And third, no one wants to parse a whole HTML page just to get one little icon!
So that's why I made Icon Horse – it automatically parses the site's HTML to determine the best possible resolution icon. And if no icon is available, it serves a decent fallback, so you never end up with a broken image. And finally, it's dead-simple to use. You simply use the hostname like so:
They're kind of different things. Graal is an attempt to create a polyglot environment. For example, using Python and Javascript in the same environment. For example you might be working on an application where the web server managed by the web team is written in Node and your data scientist team uses Python scripts to deal with the data, but they need to run in the same environment. Graal lets you re-use that environment for both.
Node and Deno are dedicated runtimes to run Javascript using the V8 engine. Both provide a standard library of additional functionality to make them worthwhile beyond just browser code.
> Tech companies (Google, Apple) don't custom-tailor their maps because they want to. They do it because the states use leverage to force them into it. And the states do it to promote the idea that the disputed territory is theirs.
So what? Google wants people to use their map software. By showing variations of the map depending on what the official stance of the regional government is, they are ensuring that their map software is available in that region and fits the context of that country.
There is a Russian narrative for Crimea being theirs. There is a Ukrainian narrative for Crimea being theirs. It's not Google's place to decide between them, it's their place to create a map people can find things on.
It does not matter what you, I or Sundar Pichai believe is the truth of whom Crimea should belong to. Their product is a map and it's available in Russia, Ukraine and Crimea. In fact, by presenting all the credible alternatives in this case (for Russia's side, they currently administrate the region and for Ukraine's, it was very recently their territory), they are being apolitical about it.
You can set it up in your editor of choice - I use Zed, and it's just listed as one of the providers you can choose.
In terms of performance - it works decently well.