I'm using Arc, and wondering how you synced the toolbar's color to the background.

I am not sure what ARC means in this context?

Probably Arc browser: https://arc.net/

Oh I just tried it on ARC. I'm not sure how they synced though.

I see, nice accident :)

But why? Whats the use case?

Some people need to run macOS-only software, this potentially makes it a bit less painful than the alternatives for the same reason containerized versions of other finicky setups do.

In the README there's a blurb with:

> Run Mac OS X in Docker with near-native performance! X11 Forwarding! iMessage security research! iPhone USB working! macOS in a Docker container!

> Conduct Security Research on macOS using both Linux & Windows!

I can imagine this being useful for CI builds, for instance. On the other hand, this is probably against Apple’s license agreement, so businesses would want to stay away from it.

Whats that profiler being used?

Looks like the one built into chrome. You can open your browser and attach a node instance so you can debug and profile it.

Here's a basic How-to:

* Run node with `node --inspect <file>`

* Open Chrome and go to `chrome://inspect`

* After it finds your target, click the inspect button to launch a debugger.

It looks to me like the profile viewer is actually speedscope ( https://www.speedscope.app/ ). I find it nicer for exploring profiles compared with Chrome's built-in viewer.

To use with Node.js profiling, do the `node --inspect` and `chrome://inspect` steps, then save the profile as a .cpuprofile file and drag that file into speedscope.

Another thing I've found useful is programmatically starting/stopping the profiler using `console.profile()` and `console.profileEnd()`.

That is a great tool. Also, I learned about perfetto the first time today, after doing Javascript profiling for a few years.

Author here.

Answered this elsewhere here: It's the `--cpu-prof` argument with node and the resulting profile is loaded into speedscope.

> In my experience, I have to fight to keep my devs from over engineering their solutions and just get something going.

In practice tho, the grass is always greener on the other side. You either wish the developer had just hacked something to get it going, when the feature failed, or you wished they had put more effort to make it more abstract and scalable, when the feature set for scaling.

Everyone's a genius on hindsight. Getting it right is more of a mix of experience, gut feel and luck imo.

Oh man. Was planning on using Auth0. Never heard of Okta, but reading the comments in here has confirmed my suspicion of the company's core value. Now I'm having doubts.

Okta is an awesome company, there will always be doubters, do your own research, and don't trust anonymous chats on some internet forums, including myself.

Which reminds me Facebook's wall worked perfectly for them. On the other hand, I wouldn't mind signing up yet another account among the hundreds of accounts I already have.

View page source. What a beauty ️️.

Came here to post exactly the same. You CAN write human readable html!

Really? He doesn't close the <p> tags.

That's only a problem for XHTML. HTML5 implicitly closes the previous <p> tag when you open the next one; thus, a <p> inside a <p> is an implicit </p><p>, if you will.

Why does VS Code auto add the closing <p> tag when you open them then? It doesn’t do it for, say, <img>. Bug?

Feature. <p> tags can function as containers for text and other elements, and VS Code can't distinguish between <p>, with the special handling, and <div>, without it.

Okay, to be fair, that does sound like a bug.

Didn't know that. Thanks :)

That’s optional in HTML5

People need standardization. The docs are usually the source of truth or go-to for any disputes. Whatever's written there is the best practice since literally everyone who uses it would have read it.

I don't mind being targeted as well and if they push me cheaper and better promo all the better. It's despicable however if they start to skew the prices in their favor due to your interest in the item.

As a developer, no one seems to know what's the best solution. But if they're not the one implementing it, then suddenly everyone's an expert and has an opinion.