There were no "big" rivers, ever. More like springs. We have lots of subterranean water, so out of the 18 rivers we have in the city, 16 have their sources here [0]. They were used to power mills in the 19-20th century during the industrialization. Many of the rivers that used to go through the city center flow underground.
I live close to the river Olechówka [1], which flows into a regulated reservoir that used to feed a mill - so the area is called Młynek, "Little Mill" :)
I made a similar map but with tiles that only load of you zoom in far enough: tomthe.github.io/hackmap/
(Sorry for posting my link so often)
That way it has to load only a few megabyte for the first view.
Nice introduction, but I think that ranking the models purely by their input token limits is not a useful exercise. Looking at the MTEB leaderboard is better (although a lot of the models are probably overfitting to their test set).
This is a good time to chill for my visualization of 5 Millionembeddings of HN posts, users and comments: https://tomthe.github.io/hackmap/
Thanks, a couple other people gave me this same feedback in another comment thread and it definitely makes sense not to overindex on input token size. Will update that section in a bit.
Depending on the data, maybe? SDFs aren't great at rendering large numbers of enumerated objects -- something like a point cloud would be prohibitively expensive, so I wouldn't think to use them for like traditional graphing.
This one might be interesting for you: https://daylightcomputer.com/
it has a fast e-ink-type of display. Unfortunately it is expensive and not available.
I'm not saying they're necessarily wrong... there are certain things where a website should just be dead simple. I built a site for my mechanic, in trade for work on my car. It's like three static pages. Just something to backstop a link on Yelp and Google Maps.
I said simple websites are a dead letter, because it's no longer the 1990s. There's no cachet in them. The web is littered with simple sites that don't rank and no one ever visits. Then the owners think 'maybe I should hire SEO' or 'add a blog' and the question is "wait you built me this site, why can't you just do that for $500"? And that's why I just refer clients like that to someone who does Wordpress now. I have no interest in learning the giant pile of PHP sludge that is WP for projects that barely pay. I hardly build websites at all anymore unless they're SPAs, and only if it's functionality that can't be done with off the shelf frameworks.
To the sibling who said I'm doing this to justify being a freelancer - quite the opposite. I'm telling potential clients of a cheaper way to get what they want, and turning away work that I know is a pointless headache.
Because most non-technical people greatly underestimate all the moving parts in a website, even a simple one.
And yes some websites truly are simple and can be managed with a few Markdown pages and a static site generator (even that can be a barrier to non-technical folk), but any kind of advertising or small business website - even if it's a single page - needs the ability to be updated or managed by a non-technical person and those parts are unknown/invisible at first.
Wordpress, for all it's problems, is one possible solution that can help those people have the website they imagine or want without the sticker shock that comes with the eventual realization that their website (as a whole) is not "simple".
It’s like a lightbulb. Of course, the manufacturing of lightbulbs is a highly technical topic. However, to the user, they present a simple interface (screw it in and flip the switch).
I feel like this is a point that devs often miss. Simplicity from the POV of a user and the POV of a dev are completely different things.
The dev finds a static site generator simple, and WordPress unnecessarily complex. The user finds WordPress simple, and an SSG unusable.
reply