dnlzro

Psst, the GitHub link in your post is broken (it should be https://github.com/chenxin-yan/crust).

It’s built with SwiftUI, which is not really cross-platform.

The only reason why you regard JavaScript as “fundamental” is that it’s built into the browser. Sure, you can draw that line, but at least acknowledge that there’s many places to draw the line.

I’d rather make comparative statements, like “JavaScript is more fundamental than React,” which is obviously true. And then we can all just find the level of abstraction that works for us, instead of fighting over what technology is “fundamental.”

I didn’t know about the `name` attribute on `<details>`, thanks for pointing that out!

Stylable form controls are definitely a step in the right direction. It really should not be taking this long though. In the meantime, developers have been building broken, half-assed, inaccessible inputs just to satisfy aesthetic requirements.

Web Components are a great way to implement things that the browser should have already implemented, like accordions, combo boxes, and date pickers that don’t suck. It’s been a pleasure to use them in a mostly static, content-heavy Astro site.

But beyond that, they’re not really usable without a framework that can deal with state and reactivity across a whole application. And that’s fine! They fill a good niche. But just because the browser provides an API doesn’t mean it should be used whenever possible.

That’s not true. There’s an API to read from and write to Apple Health: https://developer.apple.com/documentation/healthkit

I’m not sure if that’s something the Pebble app uses right now, but it’s certainly possible, and a third-party app could make it happen as well.

> Upgrading today should save more money vs. upgrading down the road.

Ehh, I’m not sure about that. It depends what trend the resale value follows. Generally, if you’re upgrading every 3 years instead of every 6 years, you’re going to be spending twice as much on new phones, but it’s not always the case that you’re getting twice as much resale value.

I think you can take Google at their word for software support though. They promised 3 years for their phones at the time, and they delivered no less.

Also, Pixel devices are very well supported by third-party ROMs after EOL: https://xdaforums.com/f/google-pixel-3a-roms-kernels-recover...

Even acknowledging this flaw, there's a valid reason (simplicity) to design it this way.

"Be kind. Don't be snarky."

To add to jeroenhd's comment, if you're only sending mail from a single server (e.g., you are using a custom domain with Proton Mail, Zoho, etc.), then you probably don't need DMARC reports at all.

To avoid them, you can remove the `rua` or `ruf` tags from your DMARC DNS record.

> that don't implement both SPF and DKIM

I don't see how that's related at all to specifying report addresses in the DMARC record.

What makes you draw that connection between climate policy and a lack of new hospital/healthcare construction projects?

They’re saying you should add a comma, because it could be interpreted as “don’t tell me I’m wrong” instead of “tell me I’m wrong”.

> Maybe you’re at a restaurant and they need you to open a website for example. You may end up having to bug some people around you for their phone. It can be annoying but I haven’t found this to be too troublesome.

I have been using a profile-based restricted iPhone setup for about 6 months now, and this has been the biggest holdup for me. I've pretty successfully blocked almost everything distracting, but I'm pretty good at finding ways to bypass my restrictions. e.g., I'll find an alternative Reddit client (like Redlib) to bypass my Reddit blocks.

The obvious solution is to use a whitelist instead of a blacklist, but then you completely lose the ability to scan QR codes in the wild.

I'm thinking of building a browser designed for this purpose. Your browsing can begin at certain pre-defined entrypoints, like a news aggregator or a QR code, but you can't manually enter arbitrary URLs or use search engines.

There is no visible plumbing because it kinda is magic! Astro provides adapters for different server runtimes (e.g., Vercel, Cloudflare, Netlify), and it's basically just plug and play. The Cloudflare adapter exposes a bunch of bindings [1] through `Astro.locals.runtime`, which can be accessed during each request. The `cf` binding contains incoming request properties [2], including latitude and longitude.

These bindings (or at least some of them) are also mocked when developing locally, in a non-Cloudflare-Workers environment.

[1] https://developers.cloudflare.com/workers/wrangler/api/#supp...

[2] https://developers.cloudflare.com/workers/runtime-apis/reque...

I'm sure that's your totally unbiased opinion ;)

It's always facing the sun (although it doesn't include the sun itself).

Maybe someone smarter than me could add stars to the night sky, so it's not just black.

A server is needed to calculate the sun's position from latitude + longitude + time, and then render the gradient. I could use HTML templating in some other language/framework, but I used Astro because that's what I'm familiar with and it's very easy to deploy to Cloudflare Pages.

I actually included that so the tab and status bars are themed on iOS/Safari. Here's someone else's writeup on that: https://medium.com/@evkirkiles/coloring-the-webkit-browser-b...

Thank you! And umm, not to make you feel ancient, but I think I wasn't even alive yet when `setTimeout(() => location.reload(), ...)` first became widely available.

Unless you're holding only cash, why would that matter? Your real wealth can grow as long as you are holding assets that appreciate faster than the dollar depreciates.

Source code: https://github.com/dnlzro/tintin

I chose it because it’s what I'm used to and because it makes it really easy to do SSR (I wanted no JS to be sent to the client).

I did that intentionally because the only thing I wanted on the page was the comic panel. I may reconsider and add a small info button in the corner of the page with links to other timescales and the source code.

But I'm also trying not to overthink this too much... It's just a silly little website I made in an evening.

Great suggestion, and thank you!

Ah, that’s too bad. I do plan to update it so that the speech bubbles are SVG objects instead of embedded in the image, which should make it dark mode-friendly.

Happy to hear that — it’s what I was going for :)

Valid, not nitpicking!

Thanks for the suggestion, will do! (I’ll also be open-sourcing it, as I probably should’ve done before posting)