ece

DJL is pretty great.

Reminds me of deep blue not knowing what to do and moving randomly while being white in the first match against Kasparov. It won.

Apple is free to bring the App Store to Android, while Google can't do the same.

I think Intel Arc GPUs also support them, from my reading. Apple seems to as well since the M1, but Metal.

I also found this: https://github.com/psanford/tpm-fido

FIDO2 should be used more, hopefully more sites end up supporting it sooner rather than later.

As the article points out, divesting some stores in some locations isn't a long term solution that has worked in the past. I don't think it's in anyone's interests to have oligopolistic supply chains and grocery stores. If you look at the other related story on HN today, you'll see the top 4 grocers have jumped from 10-15% of the market share to ~35% and plenty of suburban and rural havoc caused by mergers.

If the status quo is sustainable, which it seems like it is, then there is little reason to not consider these mergers monopolistic and stop them.

It's a bit ironic that city councils that kept Walmart out, are powerless to stop something like this. I mostly can't look at this from a less-competition-good POV, but hey, not just the lawyers, but the monopolists will do just fine too.

Walmart is irrelevant if there aren't any near you.

I think the problem is with a known bad driver blocklist not working like it should. It's something that should prevent installation even if the user clicks yes.

The problems are on the supply side they say, we don't have much control over the supply side they say. Blunt hammers shouldn't be used here. MMTers are right. https://mobile.twitter.com/StephanieKelton/status/1483454011...

Yeah, I don't know what the Google/Jibe/carrier relationships are, but Google made an exception for Samsung[1], which I suppose could've been carrier approved too. Looking more at it, it seems like Google Messages is still the RCS client, and it's exposing messages to Samsung's app.

Honestly, it's kind of hard to blame Signal and/or Google if carriers are involved here. I mostly use Signal and Element, so if those two had a single client, that'd be fine. But, I think Signal probably still favors a centralized system, and they have added ongoing call transfers from and to mobile/desktop, and now Stories and the money transfer (not a fan), so I suppose it's up to the users to choose.

[1] https://www.sammobile.com/news/google-messages-rcs-integrati...

SMS is carrier owned and had an API. What you're saying doesn't surprise me, but I guess an RCS client written by Google and can't talk to iPhones isn't exactly an upsell.

I'm not an author or artist, but you only need to search for tweets about copyright on Twitter to see it benefits the rightsholders a bit too much. If the term was shorter, maybe it would be different. Of course the reason the term is longer is because of rightsholders.

It's hilarious because of Simula's size compared to the rest, and because it doesn't include Apple/Valve, and really, only those two should even be on the list at all! They literally subpoenaed everyone except their real potential competition. I get it, they subpoenaed whoever they could. I think the FTC in the Bloomberg story linked in the post said it best: "It reflects their scorched-earth defense strategy here to fight in whatever manner is available to them"

There isn't anyone with a current model headset like the Quest, that is even remotely close in market share in the US.

This is growth at all costs. Big companies buying up established independent developers to add to their services while consumers have less choice. AB/MS, Figma/Adobe, it needs to stop.

The Within deal is above $400 million. Doesn't seem like shelfware money.

The end of the article seems pretty consistent with FTC's view: Meta can compete with better hardware and software on it's own.

How about a look at Meta's app sales to prove that? I think this list of who the subpoena was served to is pretty hilarious, and it's even more hilarious that Apple's not on this list:

Alphabet Inc.

ByteDance Inc.

HTC America, Inc.

Huawei Technologies USA, Inc.

Nintendo of America Inc.

Panasonic Corporation of North America

Samsung Electronics America, Inc.

Simula VR, LLC

I think the malicious intent is all on Meta's side. They have a head start with Occulus, no one else is even close in the US.

From your link, the FTC says:

> "Meta already owns a best-selling virtual reality fitness app, and it had the capabilities to compete even more closely with Within’s popular Supernatural app. But Meta chose to buy market position instead of earning it on the merits."

I don't buy that VR is so young, we're a couple generations in now on multiple platforms. There are still new entrants in the space, which is good, and they would be negatively impacted if there were less established independent developers. Facebook had a head start, and they're trying their best to lock up the market before Apple/others enter it.

> VR is still up for grabs

Curious statement, considering the FTC is trying to preserve competition in the space. Excite and Altavista weren't trying to buy up the biggest websites around at the time.

If Stadia's core audience was supposed to be occasional gamers, then that audience didn't exist. Not to the extent Google thought anyway.

That's the nice way of putting it, but yeah, cancelling things people like and/or not providing enough value (if your internet is fast enough) is going to hold a service back too.

Let me translate that:

Antitrust regulations "would impose rules that are bad for our bottom line, and would offer consumers choice."

"We got so big because of lax regulations and mergers like the Doubleclick merger that weren't stopped, and we still want to keep buying out any potential competitors."

The real co-sponsors. Or at least, cosponsors-lite.

A physics teacher in high school recommended RPN to me, and the 48G. I went through college using the builtin equation library quite a bit.

I wonder how hard it is to just sell a GPU and say it's CUDA compatible. Google built their own toolchain over PTX, AMD could do the same, and have CUDA compatibility if they wanted. I think the difference here just might be that Google's still buying A100s, while AMD wouldn't be.

HIP/ROCm support should absolutely be better supported on all AMD hardware for more adoption, instead it seems to barely register like OpenACC or Vulkan compute. Intel might have better luck with OpenAPI.

I tried getting pytorch vulkan inference working with radv, it gives me a missing dtype error in vkformat. Fp16 or normal precision have the same error. I think it's some bf16 thing.

If undervolting is the new overclocking, you'd have to wonder if that changes anything.

This is what the new EU DMA regulations are hoping for too.

You have IAPs.