HN user

porcc

88 karma
Posts0
Comments62
View on HN
No posts found.

We saw this happen with Stable Diffusion and it's not surprising we see this happening here. There is a lot of interest in taking these models that are in striking distance (single order of magnitude) from running inference and training on consumer level hardware and as such a lot of energy is going into making the optimizations that can get us there.

Generally speaking, research is not usually done with consumer usage in mind, so what this is, and Dreambooth etc. for Stable Diffusion was, is that gap between researcher software and accessible software being bridged.

So many parts across the stack need to work well for this to go well. Early support for popular software is a good example. This goes from partnerships all the way down to hardware designers.

I'd argue it's not about engineering more than it is about good organizational structure.

A GPU from 2008 has to fill a quarter of the pixels at half of the refresh rate and has no latency, weight, or heat requirements. The Quest 2 has to carry a massive burden being on a face and fill nearly 4k pixels at 72 FPS. Meta has stringent requirements on maintaining that FPS to prevent VR sickness

Classic problem of the game is too easy for the developer because they've been playing it for so long. The controls are unintuitive but fun if you're willing to take a beating for a while. Even after a long time learning tho there's a strong lack of control, a little bit of rotational friction tending to keep the ship upright would go a long way

Probably it's just a hard problem. Max for Live is a bit more general purpose than TD but still has its limitations I'd imagine. Enso lang is the best attempt I've seen for this: https://enso.org/

Funny to think that the developers who haven't paid for the ability to remove the splash screen are also the ones likely to have optimized their games poorly

Intuitively maybe. In practice definitely not. Creator of xxx with 100 stars has obvious and easily understood impact where "contributor" could mean anything

The incentives here seem strongly skewed towards having your name on a new framework for career purposes rather than improving the ecosystem at large

Not the same size, the comparisons are misleading as both those phones look small compared to the 13 max. The SE has a form factor that matches many Android phones, small-phoners (like me) want to go smaller than that if possible.

https://www.phonearena.com/phones/size/Apple-iPhone-12-mini,...

I had the previous SE from years back and it's still my preferred size, the current mini is significantly bigger than it.

As an aside, I had to switch to the 12 mini as the old SE started becoming unusable due to its age. I did switch to a Pixel 4a temporarily but that was too big for what I wanted and traded it in as soon as I could.

Macbooks are abysmal for window management, for example. There are some lightweight tools that can manage some placement but they are neutered in one way or another. Deeper integration requires disabling BIOS-related security which I am personally uncomfortable doing, and still doesn't offer full control like you'd get on other Unix systems. Most of the OS is similarly untouchable.

Another example is Safari and its extensions ecosystem: an Apple license is required for publishing and as such even basic tools (stylus etc.) can require the user to purchase with no guarantee of developer support in the medium to long term.

OOTB the biggest example is the Mac-style hotkeys, its a persistent and extremely annoying problem for new Mac users and is, from the outset, unfixable via any sort of configuration, BIOS or not. Concretely: CTRL + T for new tab is now command + T, however switching tabs is still CTRL + Tab (Mac control is more like alt, in this case).

It's an eternal reminder that you are now stuck doing things the Apple way even if it's just relearning all of your hotkeys.