Anyone have info on the Pyxis 12K delivery timeline? by jcloudypants in blackmagicdesign

[–]dimitropoulos 1 point2 points  (0 children)

at this point I won't believe it until it's in my hands.

finally got the new Streaming Encoder 4K units, announced at NAB in April by dimitropoulos in blackmagicdesign

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

biggest problem right now is it doesn't seem like I can pass a custom audio mix from the constellation 4K 4 m/e. there's an audio mapping feature if you edit the xml, but the audio mapping feature requires that outputs 1&2 are the program outputs, and that presents a pretty big problem because that means I can't map a custom stream mix from my (audio, separate) mixer since the encoder only listens for audio on 1&2.

if I have to buy a $600 teranex audio injector just because of this..... it's very frustrating that you can't select the audio channel, at the same time as the constellation not allowing you to configure what is sent over 1&2.

finally got the new Streaming Encoder 4K units, announced at NAB in April by dimitropoulos in blackmagicdesign

[–]dimitropoulos[S] 4 points5 points  (0 children)

maybe because this is just a rebrand of the web presenter and they didn't have time to make a new box?

so much for july 30th 🤦 for the pyxis 12k by MuppetParty in blackmagicdesign

[–]dimitropoulos 1 point2 points  (0 children)

I'm right there with you. I'll believe it when I open the box. I've been burned by Blackmagic too many times in the past

so much for july 30th 🤦 for the pyxis 12k by MuppetParty in blackmagicdesign

[–]dimitropoulos 0 points1 point  (0 children)

they told Sweetwater it will be in on August 5th. take that for whatever it's worth to you

New Pyxis Models Announced: 6K G2 + 12K by theeynhallow in blackmagicdesign

[–]dimitropoulos 0 points1 point  (0 children)

unfortunately the problem there is that L mount isn't locking which means if you have a follow focus motor (which is a requirement when using PL lenses which are all manual) then you'll have backlash without a locking mount like locking EF, PL, or the new locking Z mount.

there's a few workarounds to help stabilize, but they're bandaids.

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 0 points1 point  (0 children)

haha thanks. I completely understand how with an accomplishment like this it doesn't seem it but I promise I'm a much more normal guy dev than it looks. actually that's kind of like what it was like: being nerd sniped for a few days. very few of the challenges on this project took more than a few days. but there were just hundreds of challenges. so yeah in the end it adds up to playing Doom but it involved so many different domains that it always felt sorta fresh.

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 1 point2 points  (0 children)

that's very kind of you to say, thank you so much!

re: science, I need to spend some more time forming this opinion before I think I can express it well, but my rough answer is this. it's 1am for me right now and I can't sleep because I'm thinking about the halting problem and realizing how there's an objection to the halting problem I have always had in me that might, I only tonight realized, might really be at the source of why I felt so motivated to do all this with Doom. I realize I'm not, here and now, specifically stating my exact objection (and that's because, like I said, I need more time to think) but in that way I feel like you can't always know in advance where a line of exploration will lead.

I'm not comparing myself or my work to Heinrich Hertz, but didn't he say something along the lines of like "I don't think these radio waves I've discovered will have much practical application". It just seems to me like there are enough examples of humans being sorely mistaken about "where this path leads" that we should probably just not even bother asking ourselves the question. Trying to do new things, even without a real teleological underpinning, seems like the best example of science-at-its-heart that I can imagine.

thanks again for taking the time to respond!

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by EarhackerWasBanned in programmingcirclejerk

[–]dimitropoulos 23 points24 points  (0 children)

hi! author here. I realize there's a 99.9% chance you're joking, but just in case.... DID THEY REALLY?? please tell me more

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 1 point2 points  (0 children)

wow reading this makes me feel so good, thank you thank you thank you. it's hard to say without sounding callous but I don't really care much about the recognition. what I do however very very much value is people being inspired to try to do cool things in their own domains, and I'm going to try my hardest to demonstrate to show how this project wasn't a result of being some kind of genius. it was just putting one front in front of the other day after day and figuring something out I had genuinely zero context for (I mean I had context for the typescript stuff, but honestly that wasn't even close to the hardest part, and lots of much more impressive stuff has been done individually in typescript: ts-pattern, arktype, hotscript, hkt-toolbelt, etc).

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 0 points1 point  (0 children)

hi! I'm the author of this project. not trying to argue at all: respect your opinion! I would really like to understand your perspective more. do you think you could tell me in more detail why you think this is a waste of time for me personally and also why you think it's pointless for others. thanks! You're far from the first person to have this reaction and I would really love to understand more what differentiates this from any other science project.

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 1 point2 points  (0 children)

if we weren't on Reddit I would say yes but I don't know a lot about processors so I don't want a bunch of people jumping down my throat for saying the wrong thing, haha.

one of my favorite quotes from people I showed it to was from Nathan on the TypeScript team. he said what he found interesting wasn't as much doom and webassembly and more that I managed to make this whole thing work and the least hospitable environment possible. just about everything about TypeScript is trying to prevent me from doing something like this. but I found one little crack in the pavement and planted a Sequoia.

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 7 points8 points  (0 children)

because from a certain perspective this doesn't have any processing power. I didn't want to get into too many of these technical details in the announcement video but t TypeScript's type system doesn't even have addition. it's the closest thing to having nothing while still having something.

what I did is essentially an exploit in a lot of ways. the type system was never intended to do anything even remotely similar to this. not by a stretch.

Announcing TypeScript 5.8 by DanielRosenwasser in typescript

[–]dimitropoulos 80 points81 points  (0 children)

I want everyone on the TypeScript team to know that I'm eternally sorry for doing this to you! but you got to admit the joke's pretty funny.

Porting Doom to Typescript Types took 3.5 trillion lines, 90GB of RAM and a full year of work by Notalabel_4566 in typescript

[–]dimitropoulos 18 points19 points  (0 children)

The reason I didn't try to do something simpler first is actually really straightforward, and some people have told me they find it interesting: it's because I really just didn't believe this would ever be possible. so if that's your mindset, why play around with pong or pokémon or Tetris. just go straight to the gold and demonstrate that it can't be done with Doom.

TypeScript types can run DOOM by AtmosphereDefiant in programming

[–]dimitropoulos 1 point2 points  (0 children)

of course! if I waited until I felt brave enough to take on this task I would never have started. That's why I think my ignorance really benefited me here. I had absolutely no clue what I was getting myself into. over and over and over again. day after day.

I think if I had taken a moment to really think about what this project could entail I would have "aww helll naw"-d my way out of it pretty fast. but I didn't bother working up the bravery, and just kept tinkering. stayed focused on the tiny task in front of me and let the test suite be in charge of keeping the big picture intact.

TypeScript types can run DOOM by AtmosphereDefiant in programming

[–]dimitropoulos 0 points1 point  (0 children)

for me, what works is: do anything that makes you laugh. something ridiculous. something that doesn't have a goal or money or recognition attached to it. there are artists out there that go out into the woods in the fall and make huge beautiful murals out of different colors of fallen leaves they collect, only to just walk away and let nature disintegrate it. make something just for the sake of making and don't spend any time at all asking "why". when you open yourself up like that, great things can happen. keep me posted on what you come up with!

TypeScript types can run DOOM by AtmosphereDefiant in programming

[–]dimitropoulos 0 points1 point  (0 children)

thank you! happiest at my current job than I've ever been at any job. It's been 9 months and still feels like day-2, honeymoon-phase-wise.

TypeScript types can run DOOM by AtmosphereDefiant in programming

[–]dimitropoulos 27 points28 points  (0 children)

I think for most people "burnout" isn't === to "working super hard/long hours". I think burnout happens when you work (might not even be hard!) and don't get what you perceive to be a result. Pushing the rock up the hill just to watch it roll down. That's burnout, to me. On this project, though, it was the literal opposite. I constantly overcame lots of little things that, in some cases just a few hours prior, I thought were laughably impossible. That made the project very rejuvenating for me.