A browser plugin for Unity

Re:A browser plugin for Unity by chrismorgan on Saturday July 25, 2020 @01:29PM (#23950912)

The current title here on HN of “Firefox in Unity” is incorrect. This is based on Servo, not Firefox. From what I understand as a very casual observer that hasn’t been keeping up with things, Servo’s architecture is rather more conducive to this application both in embedding convenience and rendering, being able to render pages in a way that will make them perfect quality regardless of your 3D perspective, whereas I imagine Firefox might still be at the “rasterise the viewport and use it as a tile” level, though maybe WebRender (applying Servo’s renderer to Firefox) has resolved that? As I say, I haven’t been keeping up with things. Anyway, the correct title for the article is “A browser plugin for Unity”.

[ Parent | on HN ]

Re:A browser plugin for Unity by dang on Saturday July 25, 2020 @02:42PM (#23951451)

Ok, we've changed the title to what the article says.

"Please use the original title, unless it is misleading or linkbait; don't editorialize."

https://news.ycombinator.com/newsguidelines.html

[ Parent | on HN ]

Re:A browser plugin for Unity by andybak on Saturday July 25, 2020 @07:05PM (#23953076)

Whilst I understand the motivation behind this guideline, it seems to be applied with little regards for it's usefulness.

Post titles need more context than the original article title because posting to HN strips out most of that original context.

[ Parent | on HN ]

Re:A browser plugin for Unity by dang on Sunday July 26, 2020 @02:26AM (#23954907)

You probably have that perception because cases that you dislike stand out like sore thumbs, while all the other title edits escape notice. If you think about it, that pretty well guarantees the feeling "it seems to be applied with little regards for its usefulness"—because all the "useful" edits are by definition excluded.

You can use petercooper's title edit tracker to see some of them: https://hackernewstitles.netlify.app/. It doesn't show all of them, and it doesn't distinguish between edits by submitters and edits by mods. Probably we should just publish the official list—I feel like title editing is the most consistent and easily defensible thing we do.

[ Parent | on HN ]

Re:A browser plugin for Unity by andybak on Sunday July 26, 2020 @09:14AM (#23956829)

Thanks for the reply.

What do you feel would be the harm if the policy was modified to

> "Please use the original title, unless it is misleading or linkbait or lacks sufficient context; don't editorialize."

It just seems like there's frequently times when the original title is completely baffling out of situ.

[ Parent | on HN ]

Re:A browser plugin for Unity by dang on Sunday July 26, 2020 @05:37PM (#23960383)

The issue there is that sometimes a little bafflement is a good thing. Not too much, not too often, but enough to make readers work a little: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que.... It slows the mind down and makes it engage a bit in figuring-things-out mode, which is good for curiosity. I think it's a valuable mechanism for interrupting the internet reflex brain, with its rapid reactions to literally everything, that mostly governs us online.

[ Parent | on HN ]

Re:A browser plugin for Unity by leeoniya on Saturday July 25, 2020 @08:39PM (#23953491)

agreed.

this policy applied as dogma does more harm than good on a frequent basis here. especially given the clear nature of this article where there's no debatable nuance.

[ Parent | on HN ]

Re:A browser plugin for Unity by c-smile on Saturday July 25, 2020 @02:16PM (#23951279)

> "rasterise the viewport and use it as a tile"

Yes, rendering HTML/CSS using solely Unity's backend is problematic at best.

For the Unreal Engine though it is perfectly feasible.

Here is Sciter Engine (HTML/CSS/script) rendered directly into DirectX scene: https://sciter.com/see-sciter-lite-unreal-engine-in-theaters... using Sciter's DX rendering backend.

[ Parent | on HN ]