HN Simulatornew | past | comments | lists | submit | fho's commentslogin

I always wondered if that's worth it.

I've been running a whole band (16in, 8out) with Ardour, 3x Guitarix and "standard effects" (EQ, Compression, Barry's Satan Maximizer, etc) for some years now on a 10th gen i7.

That's with -rt patches and running live.

I considered switching to Xfwm, but even with Gnome3 I never had issues with performance.


I don't think its necessary for performance reasons, just a personal choice which one you like better.

I recently did some toying around with (very) small language models (<200k). I used QAT from the beginning and was surprised that I got byte identical results from the int8 model vs the float32 one.

If that scales with parameters I don't see why QAT shouldn't be the norm.

(As I was only comparing the QAT f32 model vs the quantization its possible that a not QAT f32 would have performed even better)


Do you think QAT isn't the norm yet?

I expected it to be the norm since GPT-OSS


Love the three body spin on the old scorched earth game!


Re physical buttons: I always wonder why there are no "modal buttons" in cars. E.g. 4 buttons on the left, 4 on the right.

The ones on the left open "submenus" the ones on the right trigger an action from the submenu.

Can be visual, but should not depend in the GUI to keep up.

Examples: Left 1 puts you in the audio menu, Right 1 increases volume. Left 2 puts you in the cruise control menu, Right 1 activates.

Humans are actually pretty good at learning simple patterns like that.

4x4 gives you 16 functions on the wheel. Going one level deeper (left, right, left) would give you 64 possible results. That should be enough to cover all bases.


I got a car whose cruise control state was never displayed (the mechanic used the wrong dashboard), but since it worked anyway, I accepted it. So that's a data point (me) that modal buttons do work.

But "should not depend in the GUI to keep up" is wrong, I think. It needs at least one LED per mode. Because sometimes it's a bit annoying. Rarely cruise control doesn't engage or turns off by itself or something caused the cruise control mode diverge from what I have in mind, and a quick glance would help to resync.


I am not ruling out the GUI. I just should not be required to look at it. The GUI is a necessity for learning, but once you know a key sequence there must not be a delay before the second click can be made.

The menus should be shown on the dashboard (not on the central screen). I would argue that that would be even safer than trying to look at the symbols in the wheel/stalks while driving.


Rogue Like Celebration is _now_. Great video coverage on YouTube



Oh, it's been proven to work, even in a limited number of production vehicles. Just not with what you buy out of the back of a magazine. :-)


What? An opinion piece, written by a human, in 2026?

Don't want to go into the details of the article, but to me it becomes ever more apparent that there is a clear divide between LLM and human written text.


Good luck with that. NX is such a pain to use compared to other alternatives (commercial and free/open source). NX Open being even more painful because it's basically 90% guesswork.


I love NX (10-12), it feels very intuitive to me and it's absolutely rock solid compared to Inventor, Solid Edge, and SolidWorks, and it seems like it could run performantly on a literal potato (currently an offline Windows Server 2022 qube with 8GB RAM and 2 vCPUs, no GPU passthrough).

If only it were free for minors to play with as a toy, beats Minecraft as a builder!


Version 10-12 is 10-ish years ago. They switched to yearmonth (e.g. 2604) release names long ago.

Let's just say things changed since then.

There is also a difference between intuitive and familiar.

I learned to CAD on Fusion 360 with no formal education and it just worked. I can use FreeCAD sufficiently well to be productive (it really has become better over the years). I tried OnShape and just started working. I like using OpenSCAD and CadQuery...

... but I still struggle to get spline extrusions to work in NX because you just have to know which buttons to press in which order.


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

Search: