Pretty cool! It would be great if there was a way to set coordinates manually, since Nominatim can sometimes produce mediocre results. Also, would be nice to have a way to render the same map in all themes, not just one.
The initial version were coordinates actually but then realised people mostly love their cities more than anything and it's easy that way. Will add this feature back as optional parameters.
Well also get to the point eventually where people are writing like AI because they’re exposed to it so much. I’ve caught myself rephrasing certain posts after I realized it sounded like AI
The prices for the only region in Germany are very similar to the prices in eu-west-1 (Frankfurt), except in € instead of $, so that’s basically a 16% markup by today's exchange rate. Also, AMD CPUs appear to be completely missing.
Apart from the payment part, this could be used entirely from a machine without a GUI. You can do the same with others using Terraform or aws-cli but it requires setup first.
Some commenters mentioned that the GraphQL API exposes the database IDs and a URL to the object directly in the schema. But the author did not know that and instead reverse-engineered the ID generation logic.
This is one of many reasons why GraphQL sucks. Developers will do anything to avoid reading docs. In the REST API, the developerId and url fields would be easily discoverable by looking at the API response. But in GraphQL, there is no way to get all fields. You need to get a list of fields from the docs and request them explicitly.
The author may well have been aware of this. However, since the author didn't retrieve those database IDs or URLs in the first place, they would have had to make further requests to retrieve them, which they wanted to avoid doing.
"I was looking at either backfilling millions of records or migrating our entire database, and neither sounded fun."
It also ties you to a desk. If you're working in one location, a desktop PC would be more cost-effective and more performant. If you need mobility between desks, a small form factor PC would be easier to carry. And if you are an employer and expect employees to work from home on this keyboard, you need to buy monitors for their homes.
> a desktop PC would be more cost-effective and more performant.
But ugly and taking up space, which is why the iMac exists and has been pretty successful for decades at this point.
> If you need mobility between desks, a small form factor PC would be easier
Maybe, but performant AR glasses are changing that equation. The cyberdeck, as an ideal, still exists for a reason.
> if you are an employer and expect employees to work from home on this keyboard, you need to buy monitors for their homes.
Do you? Is that law where you live? Because it's definitely not here in UK. I'd rather work on my trusty 4k than some shitty cheapo Dell only provided to tick a box.
The first thing I thought of when I saw this was using a phone as the display. Not as good as an actual monitor, but a far more interesting setup than what you're imagining.
You’re unlikely to find a 1998-era Web page still running a 1998-era SSL stack. SSL was expensive (computationally and CA-cartel-ically), so basically banks and online shopping would have used SSL back then.
The linked post contains three cases of Markdown syntax (underscores) leaking into the text, where actual italics were likely intended. This is the most basic Markdown syntax element failing to work. The problem CommonMark is trying to solve is not adding new features (the only one they added to Gruber Markdown is fenced code blocks), but rather specifying how to interpret edge cases to ensure the same Markdown code produces the same HTML everywhere.
I understand the goal of the spec. In my experience once some spec document gets adapted widely enough, there's a strong incentive to add new features to it, which renderers would then be compelled to implement. Before you know it, MD is a complicated spec that doesn't serve its original purpose.
In this case a few minor edge cases is really not a big deal compared to that (in my opinion).
reply