LysPJ

For anyone unfamiliar with the term (like me!), Wikipedia says Eproctoring is:

[...] a form of exam proctoring which involves monitoring student behaviour during exams administered electronically [...]

I've seen quite a few developers say that they chose the M1 Air over the M1 Pro mainly because they didn't want the touchbar.

Heat pumps are very widely used here in Norway. I wouldn't class our winters as "mild" :)

In the article, there is the following quote:

> "But you’re thick like me", he said

For any readers who aren't familiar with British slang: the word "thick" means "stupid" in this context (as you have no-doubt worked out!).

I've been extremely happy with my M1 Air. I waited until Golang and Docker were available (around Jan 2021), but I haven't suffered any workarounds or hacks.

To be honest, it has all been much smoother than I expected, but YMMV.

The wording of the "act on your behalf" message is very frustrating indeed. I don't like to think about how many app installs I've lost due to the wording of this message. I've had worried users query me about it directly, but presumably many more have just abandoned the installation without contacting me.

Here's another GitHub forum thread asking about it:

https://github.community/t/enable-you-to-trigger-actions-in-...

A trivial wording change would go a long way toward fixing this problem. Unfortunately according to GitHub Support (post 15 in that thread) "The current wording is not considered a bug."

:-(

> I wish they had something for worker processes

It may not fit your needs, but did you know that you can invoke other Cloud Run containers from a Cloud Run container?

Alternatively, you can enqueue Cloud Tasks from a Cloud Run container. Those Cloud Tasks can in turn invoke Cloud Run containers.

Not sure if they fit your usecase, but I use both of these approaches and they really expand the capabilities of Cloud Run for me.

For me, Pocari Sweat is the king of Japanese sports drinks. It has been a few years since I visited Japan, and I still have a unopened bottle of Pocari Sweat "on standby" :)

I really like this quote from the CEO (Maxim Shafirov):

“Basically, we wrote all this so that making software would be a pleasant and creative process.”

The relevant post on golang-announce:

https://groups.google.com/g/golang-announce/c/2-Rj3P5uRLs/m/...

Hi Hakim, this looks really great. Thanks for creating it :)

A minor bit of feedback on the webpage: I spent a while looking for a link to an example presentation, but couldn't find one. I eventually realised that the entire top section is an example presentation. This is so cool!! I wonder if adding some text next to the arrow ("Try the demo", or similar?) might help people find it? The demo is so nice, it would be a shame if some users don't spot it.

Ha, interesting approach :) I like the idea, but I wonder if it might trash too many non-spam emails for me. Have you had any problems with false-positives?

Speaking of Jira alternatives, I recently discovered Kitemaker [1], which is really nice. The UI is clean and it's fast too (has keyboard shortcuts for everything, etc).

[1] https://kitemaker.co/

Perhaps. There is the danger that those employees aren't party to all the relevant information, so their version of the story might be inaccurate too.

Thanks for the recommendation!

I've also found this list, which might be useful: https://best-sci-fi-books.com/16-best-solarpunk-books/

Do any HN readers have recommendations for Solarpunk novels?

Thanks, that makes sense. I'm currently doing D3.js rendering within a Vue component. I suspect that my code will be cleaner if I switch to the Vue.js constructs for managing the DOM, rather than D3's enter()/exit()/update(), so even if the performance is ultimately the same, there should still be a maintainability win.

It sounds like it's worth me doing a Vue implementation and running some benchmarks.

Thanks, that's helpful to know about how you implemented it in Vue vs D3, and that there wasn't a noticeable performance difference for your use case.

Do you find there is any performance difference using Vue.js to do DOM manipulation rather than the D3 methods?

Am I right in thinking that you are using Vue.js to create/delete/update the DOM elements? If so, how does performance typically compare to using the usual D3 enter()/exit() etc methods for that?

Out of interest, how did the performance compare between the React+SVG and D3 implementations? (and what sort of data size / structure were you working with?).

> D3 is amazing. But before choosing it, you should know exactly what it is, and whether it helps in your specific use case.

I agree. D3 is really great, but not always the most appropriate solution.

I agree that migrating off a cloud provider can be very hard. However, architecting your system with portability in mind can help a lot, as rumanator points out:

> I think building somewhat cloud-agnostic to ease friction of provider migration is good

Of course, that's not always an option if the system is already built, but it's definitely a good approach.