Hacker Newsnew | past | comments | ask | show | jobs | submit | _kb's commentslogin

Turn them into biogas to create more energy for DCs.

That's certainly true to an extent. Other commenters have already highlighted necessary complexities. There is absolutely a lot of very entrenched "ways-of-working" that add unnecessary complexity, as with every domain. Not everything is a technical problem though and the social / process side of this sort of setup is what can make it work at all.

The approach that you're hinting mostly describes the general direction of remote production (https://video.matrox.com/en/media/guides-articles/what-is-re...). The big traditional players are already across that (https://www.grassvalley.com/ampp/, https://www.rossvideo.com/use-cases/remote-production/), AWS also has a plethora of services to lock you into their stack (https://aws.amazon.com/media-services/), and there's interesting new players too (https://www.tryiris.ai). There's a heap of different workflows out there, and OB trucks like the one highlighted here are just one of those.


ST 2110-22 is codec agnostic. It just standardises CBR compression, for which JPEG-XS is a good fit today.

For plug-and-play IPMX (https://ipmx.io/about/) is looking to be a pretty promising approach that combines ST 2110 with NMOS, auth, encryption and other useful features. It's targetted at the ProAV market but IMO should be mostly suitable for consumer use.


Ooh, you're right, and it just adopts the IETF RTP payload types for that. Cool.

Also forgot about IPMX.


Wish I was seeing more ST 2110 and IPMX open source work about. Would really love for good or at least common protocols to be broadly usable, available, via some good libraries.

Jpeg-xs did indeed get ffmpeg support a couple months ago. https://www.phoronix.com/news/FFmpeg-Merges-JPEG-XS


Platypus on a penny farthing.

This is a really good take.

I think the core caution is this is not type-level checks. Anything this validates still needs to be eval'd. It's not a guarantee of correctness for all inputs but does look to be a fairly light (and useful) tool to make unexpected states easier for you and others to identify.


Hard disagree. This is what brutalism looks like in sunny, subtropical Brisbane, Australia: https://commons.wikimedia.org/wiki/File:QPAC_Exterior.jpg

If the straight concrete isn’t your thing, they’re also currently extending it with a glasshouse: https://www.snohetta.com/projects/queensland-performing-arts...


Wow that is already ugly without the water stains

Looks even worse in the sun. At least it belongs in the depressing, shitty weather.

What's depressing and shitty about Brisbane's weather?

I think they're saying that brutalist architecture feels out of context in Brisbane's weather, whereas the gloomy dreary feeling of the building fits in perfectly in the former USSR's gloom

Predicated 90% humidity at 3am this evening does not fill me with a great amount of joy.

I think the above commenter may be referring to the rather more unfortunate UK climate though.


I don't hate brutalism but I'd much rather have the https://en.wikipedia.org/wiki/Royal_Exhibition_Building than QPAC, rain or shine.

I think both look ugly and megalomaniac.

You're entitled to that opinion, but if you give an alternative for how a big multi-storey building for large events and crowds should look then it will move the discussion forward.

To me the issue is that the alternative to brutalism isn't classic, art deco, art nouveau, googie, etc. It's soulless glass and steel designs.

I'd rather have classic, art deco, etc. to brutalism but I'd MUCH rather have brutalism to modern glass and steel.


Eh... The concrete looks to me like a bland imitation of Spanish Adobe style building.

It's better than most of the brutalism we have around here, I'll grant you that, but still not really my cup of tea.


For images surely this is the next pivot for hot dog / not hot dog.



If so, one benefit is you can quickly and safely mix up your set of agents (a la Inverse Conway Manoeuvre) without the downsides that normally entails (people being forced to move teams or change how they work).


It's already been linked in comments here but there's been a bit of exploration in that area with Hedy. There's some good references to prior work and comments of relevance in this paper https://hedy.org/research/A_Framework_for_the_Localization_o....


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: