Hacker News new | past | comments | ask | show | jobs | submit | nsteel's comments login

I don't want to be harsh but suppliers killing the product you're trying to build around isn't that unusual. It's horrible, and you should 100% stop working with them next time, but it happens. I'm really not surprised they killed Tofino. It's a cool architecture but I don't think there's an interesting market for Intel here, at this time. And if we remove the Tofino stuff from this article, is there much left...? I don't think killing Tofino is particularly relevant to Gelsinger being "wrong" or "right" for Intel.

    Recipe of the day 
    Sriracha Maple Bacon
Is this the North American version of "healthy"?

I clicked on breakfast:

  - Sugar covered donuts  
  - Iced cinnamon rolls  
  - French toast  
  - Cinnamon roll bites  
  - Nutella Croissants
Healthy indeed.

"popular and healthy"... Those two sets are clearly reasonably disjoint!

Free accounts can access the Spotify API, last time I checked.

I've been also thinking this. They should have a tier for users that want to use 3rd-party integrations, and/or a tier for people who want to create such things. Strava could also do something like this. However, both companies have been going the other way and crippling their existing free APIs, and then suffering user backlash. It's almost like it's a bad idea to remove features... Who'd have thought.

https://www.reddit.com/r/Strava/comments/1gv4dob/strava_anno...


As I already posted to the growing thread of discontent at https://community.spotify.com/t5/Spotify-for-Developers/Chan... this is Spotify's usual deprecation strategy and they've done this before to their APIs. I think it's usually due to incompetence but this time that feels like only half the story. Sadly, despite their frequent self-sabotage, they still have the best API by a million miles.

Anyway, anyone with a private project that doesn't mind a manual step, can grab an access token from https://open.spotify.com/get_access_token using their browser. There's also projects like librespot (and various ports) which can provide access programmatically[0] using Spotify's client ID. Oauth is useless at preventing this kind of access.

[0] https://github.com/librespot-org/librespot/wiki/Options#acce...).


Even for those that want extended access, what's suppose to be a simple review process is absolutely broken. Their dev forum is full of people who have applied and been left waiting for months with no communication.


HBM has a very wide, relatively slow interface. A HBM phy is physically large and takes up a lot of beachfront, a massive waste of area (money) if you're not going to use it. It also (currently) requires you to use a silicon interposer, another huge extra expense in your design.


> A HBM phy is physically large and takes up a lot of beachfront, a massive waste of area (money) if you're not going to use it.

The M3 Max dropped the area for the interposer to connect two chips, and there was no resulting Ultra chip.

But the M1 Max and M2 Max both did.

I have yet to see an x-ray of the M4 Max to see if they have built in support for combining two, have used area for HBM or anything exotic, but they have done it before.

Could you recognize HBM support in an x-ray?

As for the Ultra, they used to have 2.5 TB/s of interprocessor bandwidth years ago based on M1, so I hope they would step that up a notch.

I don’t put much stock in the idea of the 4 or 8 way hydra. I think HBM would be more useful, but I’m just a rando on the interwebs.


Could it just be they realised there's only a tiny market for such a chip? You can do a better job with a dedicated, more powerful chip, rather than sticking two lesser chips together. It's really expensive and compromises both designs.

I'd be really surprised if we see any consumer CPUs with HBM anytime soon. But it would be cool!


> It also (currently) requires you to use a silicon interposer, another huge extra expense in your design.

Guess what the Ultra chips use? That’s right, a silicon interposer. :)


OK, but that's an ultra expensive chip, pretty much by definition. The suggestion was to burden other products with that big expense, and that doesn't make sense to me.


I guess I was pointing out that they already do that with the UltraFusion interconnect that’s on the Max chip found in notebooks but never used there.

But the more I think about it, the more I bet they are creating a native Ultra chip that is not a combo of two Max chips.

I bet the Ultra will have the interconnect so you can put two together and get the often rumored Extreme chip.

They will have enough volume for their own datacenters, that the Mac Studio and Mac Pro will simply be consumer beneficiaries.

It makes more sense in this framing to put HBM on these chips. And no DDR5.

In this case, the M4 Max has neither HBM nor the interconnect. I’d love to see someone de-lid and get an X-ray die shot.


They'd be very expensive. Is there really a consumer market for large amounts (tens of GBs) of RAM with super high (800+GB/s) bandwidth? I guess you'll say AI applications but doing that amount of work on a mobile seems mad.


Yeah, I feel similarly about the development of NPUs. I guess it might be useful if we find more maybe non-AI uses for high-bandwidth memory that’s needed on the edge and not in centralized servers.


I agree with this comment but you really didn't need the first 4 words.


Wouldn't it make more sense to create an issue on their GitHub repo about this?


agreed , not sure why they think that ycombinator cares more than their official github repo page


If you believe their GitHub org/accounts to be compromised, it kind of makes sense to verify if that's true or not outside of GitHub. With that said, wouldn't hurt with a GitHub issue regardless.


Does this support non-python dependencies too e.g. gstreamer? It wasn't clear to me.

I'm very wary of a new tool announcement that doesn't appear to mention why the existing tools/solutions were not sufficient. Which gap does this fill?

Edit: the answer to my second question is at https://venvstacks.lmstudio.ai/design/


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

Search: