Hacker Newsnew | past | comments | ask | show | jobs | submit | dnlzro's commentslogin

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 agree and I think it’s a nice explanation that fundamentality (characteristics upon which everything depends or would not be possible) is contextual.

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.


Accordions: just use `<details name="accordion-name">` and style it however you like. No need for JS or Web Components any more for an accordion.

Combo Boxes and Date Pickers: CSS Form Control Styling Level 1 [1] will be a massive game changer. `appearance: base` will make it easier to style every part of a browser's form input with just CSS as they start with fewer opinions on how it should be styled (less trying to be platform-specific, more web platform generic) and have more CSS selectors for their component parts. Yet they will still have all the accessibility of native form controls. Really hoping that draft moves forward this year.

[1] https://www.w3.org/TR/css-forms-1/


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.


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...


I had a Pixel 4a until I got a 10 a few months ago... they had a couple updates even after support officially ended.

I don't want to install random ROMs from a forum.

(also, I just noticed that out of all my comments, my OP was controversial enough to be downvoted <0. That's kind of funny, I thought there were better contenders.)


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?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: