tacticus

The offense is using market control in one section to control another market.

Windows being tied to AD only was the offense. Windows being tied to IE was the offense.

Google being the place you buy ad services from, and the auction house that places them and the service a website owner sells ad space to. is the offense.

> that can be really convenient for your organization

Yeah just like the AD bundling with windows was convenient. Up until you had no other choice than retaining an AD if anyone wanted windows anything.

> Binance cares most about serving the remaining 95% of humanity that does not live in the US.

That totally explains why they put so much effort into catering for US whales.

and yet the "are you sure you don't want edge" popup isn't requried in this use case.

combine that with the fact that their own apps will only open in edge in future versions makes it not like chrome on android.

> the experience of the developer making it.

Is a infrequent commonly one time thing that pales in comparison to operating it.

No i mean the fact that Nvidia is now claiming that the memory the CPU has access to can be counted as memory for the GPU. the fabric is neat. the "We have 500 GB of ram per gpu" claim is questionable.

`Nvidia discovers DMA`

Tesla seems fine using the CCS connector everywhere else in the world.

And CCS is capable of of doing 360Kw of charge (with the current 400V units and a chunk more on any 800V unit) which is a tiny bit more than 250 max on the NACS

> if Boeing ships the 777X

Though even a 737\757 replacement is 10 to 15 years away with airbus getting more and more of the order book.

From memory the No Red Port Left is also about Red on Red passing for ships

> the plan all along

BINGO

> In a message queuing system, there is no rebalancing - you just add nodes, which then also get messages, typically in a round-robin fashion.

And hope that the DNS\config propagates to the calling client and that the library can reliably add and remove nodes.

> Retrying

Wanna bet it's a built in feature in your messaging system?

Cause the whole publish op can fail at which point you have to retry sending it. or it published but you lost the ack (seen with AQ more than once) so now you send that message again and hope you remembered that whole duplicate message handling

I fail to see how it's better.

> inherently have all these features, without needing any other tooling.

Providing your queuing service magically scales. and you can just scale that infinitely

If your queue is the bottle neck (yes it happens) how do you know there are more nodes getting added to it? How do you rebalance the topic over multiple new nodes in the queue?

> I shudder when thinking of how we would have handled such failures if we used sync processing.

easily. oh look i got an error and retried a few seconds later and it went to a new isolated backend running separately somewhere else or after it started again.

> It immediately demands your attention.

it immediately demands the attention of the ops team that you've thrown all problems at while hoping that the magic queue never stops being magic.

while the client is sitting there going "WTF, where's my shit?"

> you've implemented a queue, right?

Yeah you have just without having to run it on top of a shared DB. message queues are just shared DBs with some extra ordering

Something something sonos old gen products being bricked...

Using a proper domain and real certificates is literally the right thing to do. It prevents anyone squatting on your domain and breaking internal shit.

Same as the rest of the coiner nonsense

The app teams i've seen loving it were app teams that siloed off ops but hey maybe your use cases were not mine.

I'm seeing too many places using it in some form of RPC style system as part of some "workflow" orchestration magic system with unicorns and ponies for everyone

And so painful in the short, medium and long run for anyone who has to troubleshoot or operate it.

So my plan for the audio problem is to use a set of raspberry pis with USB-gadget stuff enabled to be a webcam & soundcard then running them as a usb device. The webcam is going to be an RTSP feed (with the microphone audio) from the main system to push it through and pulseaudios network side of things to do speaker\headphone out.

it's a bit complex for what i need but it should work well.

That's a first.

:P

(and yarp.)

Wow it's a substantially different experience with most that i've been across here.

Almost every subbie I've met even those building residential properties have a few mobile apps for doc management and so many ipads for plan review\access\defecting

The last plumber I worked with had the quote in my email with updated pricing and online billing before they got back to their ute.

:O

I wonder if they moved to different solutions when they started bringing in subbies?

for a counter example. I'm currently getting a small house built and the near by land developers are mostly using the SAAS solution I worked at to manage the construction\design of each subdivision.

There are a fair few doc management for construction companies around now. So i'd be surprised if any large project wasn't using a managed or self hosted one today. and several of them have fancy tools that can pull in 3d models and the like. (oracle bought one that i worked at)

So how was life at internode or aussie?

About the same you need to stock the shelves

And when you tell them no what's the chance they listen and don't suddenly volunteer you for a search.

Which won't stop it happening with a package manager either.

Even immutable repos are going to have fun with DMCAs.