Yeah, I don't understand why everyone is trying to invalidate their experience or suggest workarounds (implying that they are the problem); this isn't stackoverflow.

Every TV I have interacted with in recent years is slow and terrible, except for really old ones. The TVs are the problem, and we shouldn't be making excuses for that.

Welp, that took up a chunk of my day. This is as far as I got tricking it into doing webgl (it just renders a triangle):

if(!window.g){gc=document.createElement('canvas');g=gc.getContext('webgl');c.parentNode.replaceChild(gc,c);k=Object.keys(g.__proto__);d='void main(){gl_';str = `g395(g41,g318())g310(g41,new Float32Array([0,0.5,0,-0.5,-0.5,0,0.5,-0.5,0]),g46);a=g322(g139)g382(a,'attribute vec3 c;${d}Position=vec4(c,1);}')g313(a);b=g322(g138)g382(b,'${d}FragColor=vec4(1,0,1,0);}')g313(b);d=g320()g302(d,a)g302(d,b)g376(d)g393(d)g435(0,3,g128,0,0,0)g406(0)g404(g12,0,3)`.replace(/g(\d+)/g,"\ng.\${k[$1]}");eval("eval(`"+str+"`)")}

I assume there are far more advanced methods than what I managed to do, so it's probably possible to actually get that to 140 characters.

Every time I think I couldn't possibly make it smaller, I manage to shave off a few more bytes. Got it under 400 now:

x.arc&&c.parentNode.replaceChild(g=c.cloneNode(),c);x=g.getContext`webgl`;f=Float32Array;eval(`d=320()395(41,318())310(41,new f([0,n=0.5,-n,-n,n,-n]),46)${z='382(a=322(13'}9),'attribute vec2 c;${d='void main(){gl_'}Position=vec4(c${w=",0,1);}')313(a)302(d,a)"}${z}8),'${d}FragColor=vec4(0,1${w}376(d)393(d)435(0,2,128,0,0,0)406(0)404(12,0,3)`.replace(/\d{2,}/g,"\nx[Object.keys(x.__proto__)[$&]]"))

Most of the amazing stuff on dwitter.net is using plain old fillRect

Clever math does the heavy lifting on dwitter.net

Yeah, that's fair, but I just wanted to see if I could do it this way (for funsies)

This should work: function scale(multi) { cnv = document.getElementsByTagName('canvas')[0]; cnv.width = 358 * multi; cnv.height = 360 * multi; window.focalLength = 200 * multi; window.init(); } scale(4);

Very nice.

Paired that with cnv.requestFullscreen() for a much better experience.

Then I started noticing the dropped frames every few seconds due to GC pauses.

> Major GC

> Duration 43.52 ms (self 26 μs)

> Collected 53.1 MB

Ouch!

I cheated (for science)

I've had the most success doing 3d scanning with Heges. The LiDAR works pretty well for large objects (like cars), but you can also use the Face ID depth camera to capture smaller objects.

I did end up getting the Creality Ferret SE (via TikTok for like $100) for scanning small objects, and it's amazing.

Oh! $100 is a great price. I always see it at around $300-350 and I haven't bought it...

I take it back; I double checked and it was more like $180. Still worth it IMO.

Does it scan hard surfaces pretty well, or does it mangle the shapes? Think car parts.

I did a test scan on a small object (1:12 scale doll), and it seems to capture fine details really well, but I can't say for sure that it would be suitable for things like car parts; you would have to try it and see I suppose.

I used to want the visual c++ 6 icon lol

This is absolutely every experience I have with python.

I clicked the frogs, but nothing happened. Am I doing it wrong or is it broken?

wait, I reopened the link in a new tab and it's suddenly working; not sure what's up with that.

Short and sweet was the goal. Cheers for giving it a go.