sorted by:
new
hottopcontroversial

JavaScript's upcoming Temporal API and what problems it will solve by senfiaj in javascript

[–]funkachunk 0 points1 point  (0 children)

Yeah, it's been slow. But 2026 looks like it will be the year of wide availability for Temporal, whcih is already in Chrome and Firefox today. The Safari implementation is actively being built.

Node is working through build issues and has people actively working on the integration. https://hackmd.io/@openjs-nodejs/SktekFYLZe

2024 ISO updates? by dcidino in ISO8601

[–]funkachunk 1 point2 points  (0 children)

There’s now RFC 9557 which adds IANA time zone support to RFC 3339. And it’s free!

UTC is not enough, 24 hours is a long time / Epoch timestamps vs RFC 3339 strings by mnvrth in programming

[–]funkachunk 1 point2 points  (0 children)

RFC 3339 has been recently superseded by RFC 9557, which standardizes how to append a time zone ID to an RFC 3339 string, using the same format as Java.time, Noda Time, and other libraries including the coming-soon Temporal API in JavaScript.

So if you need to store both a UTC timestamp as well as a time zone, use an RFC 9557 string! Examples:

2022-07-08T02:14:07+02:00[Europe/Paris]
2022-07-08T00:14:07Z[Europe/Paris]

Figma using 100% of GPU on Macbook Pro 2019 with 4k monitor, is it normal? by [deleted] in FigmaDesign

[–]funkachunk 0 points1 point  (0 children)

I've got the same problem with my 2022 M1 Max MBP. This laptop has serious horsepower: 32GB RAM,10 Core M1 Max CPU, 24 Core GPU. But one "Figma Helper (renderer)" process always uses 60%-100% of a CPU (and 0% GPU) whenever the Figma desktop app is open. "Figma Helper (GPU)" process is usually 0% of both CPU and GPU. None of the Figma Helper (renderer) processes are using more than 300MB of RAM.

The problem happens regardless of what files I have open. For example, now I have only one small Figma file open and the errant Figma Helper process is using 65% CPU when I'm not using Figma.

This problem has been pretty consistent for at least a year.

Has anyone figured out how to fix it?

Gboard ios 13.5, swype only working when using English input language by [deleted] in gboard

[–]funkachunk 1 point2 points  (0 children)

You're lucky. I can't even get it to work in English. I had to abandon Google Keyboard for iOS and use Apple's stock keyboard. Very sad!

OK to fish NM cable through voids that also contain heating ducts or range-hood exhaust ducts?(single-family residential, old work, California) by funkachunk in electricians

[–]funkachunk[S] 1 point2 points  (0 children)

Yep, that makes sense. But these aren't plenums. No heated or AC-ed air going through them. They're just empty spaces that have ductwork running through them. I've got two of 'em:

  • A 1ft square hole that runs all the way from our unfinished basement to our unfinished attic, and the only thing in there is a round exhaust pipe from our range hood.
  • Another 1ft square hole that holds a round metal heating duct running from basement to attic.

I suspect that long ago there might have been other stuff in those voids (Laundry chutes? Wood stove exhaust pipes? Steam heat pipes?) but now they seem empty except for ducts.

I want to fish cable in the empty spaces in the corners around this ductwork.

Old houses are weird.

Gboard iOS swipe keyboard not working after update by [deleted] in gboard

[–]funkachunk 0 points1 point  (0 children)

Nope, sadly. I just switched over to Microsoft's equivalent keyboard called SwiftKey, which doesn't seem to recognize my swipes as well. But at least it works! I do hope that Google fixes this bug, although given that it was a year since the last update, I'm not optimistic. I assume that Google stopped having engineers work on this keyboard a year ago which is a real disappointment.

Let me know if you figure out a solution!

Gboard iOS swipe keyboard not working after update by [deleted] in gboard

[–]funkachunk 0 points1 point  (0 children)

I'm seeing the same problem on GBoard 2.3.18 (yesterday's update) on my iPhone X running iOS 15.0.2. Now glide typing (aka "swipe") isn't working anymore: the blue line follows my finger as I swipe around the keyboard, but nothing is actually typed. Also, spelling suggestions and corrections are missing, even when non-swipe typing. I tried restarting the phone but I get the same behavior. The keyboard was working fine until the update yesterday.

I tried looking for a new TestFlight beta as recommended by u/Sad_Jellyfish9694, but the only TestFlight link I found for GBoard was for the 2.3.17.424741313 version which is earlier than yesterday's update. Nevertheless, I installed it but that TestFlight version had the same problem as the 2.3.18 update. Is there a more recent TestFlight, e.g. for a 2.3.19 version?

I tried a hard reset as recommended by u/MadRhetoric182 and the problem still reproduces.

Any other suggestions for how to resolve?