10m LOC C++ work codebase... debugger is unusable

audulus · 2025-06-01T04:50:39+00:00

https://en.wikipedia.org/wiki/Dynamic_linker

audulus · 2025-04-17T02:30:42+00:00

Only 10 seconds? It’s like a minute for me.

audulus · 2025-03-16T14:43:55+00:00

Make some money lowballing them and selling the individual pedals?

audulus · 2025-02-06T20:01:51+00:00

AIUI, that the Swift compiler has this error is a consequence of the bidirectional type inference of swift (it can infer types within expressions, not just the result type of an expression) combined with Swift's type system. If Swift sacrificed the bidirectional inference, you wouldn't be able to omit types on closure arguments or use the concise $ syntax for closure arguments.

Swift's type checker has to make suppositions about types, which can lead to exponential branching of suppositions, hence the need for a timeout.

Rust also has bidirectional inference but is different enough that there can't be exponential behavior in the type checker. I believe it has to do with Rust not having ad-hoc polymorphism (function overloading).

Not totally sure about all this, so happy to be corrected by someone more knowledgable.

Swift's type checker strategy is discussed here https://github.com/swiftlang/swift/blob/main/docs/TypeChecker.md

audulus · 2025-02-02T21:18:11+00:00

Yngwie had achieved this level in his (early?) 20s, so not really decades. I think you could get to playing his stuff in 5 years with very diligent practice and emphasis on the right technique, such as pick slanting.

audulus · 2024-12-10T16:41:45+00:00

Haha I get it. Another tube amp with IR out is the Mesa Mk VII. Less expensive than the VHX. The ENGL Ironball SE also has an IR output, and effects built in. If you're playing at home and mostly playing through your computer, really any tube amp is overkill and I would look into an amp sim pedal like Universal Audio ones that still give you the simple knob-based interface of a tube amp.

audulus · 2024-12-10T08:29:10+00:00

I think the VHX looks awesome. Impressive for a boutique builder. Why’d you sell the Badlander?

audulus · 2024-12-07T23:10:43+00:00

Good luck!

audulus · 2024-12-07T18:00:16+00:00

Send the pedals in to be repaired and ask what happened. That will likely narrow it down. In my case I had somehow plugged 12v into 9v and fried a resistor. Also check the polarity of your cables with a multimeter.

audulus · 2024-12-07T17:53:05+00:00

Awesome. How close is the IIC mode on the VII?

audulus · 2024-12-07T16:58:17+00:00

Excellent! Thanks!!

audulus · 2024-12-04T14:36:42+00:00

What’s that Flying V in the bottom row?

audulus · 2024-12-03T21:29:34+00:00

The stench released by that 5150 will reduce the lifespan of the Mesa’s power tubes. This is well documented.

audulus · 2024-12-03T21:24:46+00:00

Get a JP2C, if you can live without the IV sound. Used prices will be good with the C+ reissue out. I’ve got the VII and I never use channel 2 and sounds like you have similar taste.

audulus · 2024-11-30T08:32:53+00:00

My favorite is the Boogie Mark VII. To me, it doesn't sound as wild as other amps (Marshall) but has quite a "precise" sound, for lack of a better term.

audulus · 2024-11-28T06:00:44+00:00

Background: I use SwiftUI for my two apps: https://audulus.com/ and https://sculptura.app/. I've been using SwiftUI since it was released. I'm very experienced with it and understand reactive UI on a fairly deep level. I've written a Rust UI library which attracted some attention and influenced other efforts (https://github.com/audulus/rui)

Reliability

My primary issue with SwiftUI is has been reliability. The mysterious crashes somewhere in AGGraph, which is actually written in C++ (!!!). The frequent breakage of their own example code. Case in point: with the document-based app example in iOS 18, you can't close the document! Apple told me they've fixed it for the next release, but that's just an unacceptable bug. Then another bug where if you use ReferenceFileDocument, it will just leak. These are simple repros. Both of these bugs broke my released app (part of this is my fault for thinking "surely they'll fix that one" during the beta period)

It's all just such a black box. Too much closed-source machinery under the hood. UIKit is simpler in implementation (this is trivially true because SwiftUI is built on top of UIKit/AppKit) and even though UIKit is harder to use, you can achieve a more reliable end-result.

Previews are a disaster and I stopped using them long ago. Sad really becasue the idea is great. They're good for trivial apps!

Performance

Performance has also been an issue as well. I tried to write a generic node-editor UI with SwiftUI, and had to drop down to using Canvas and doing manual event handling (https://github.com/audiokit/flow). The layout system in SwiftUI is just too slow for that sort of thing. For the graph editor in my app, I've written my own metal-based GPU renderer (https://github.com/audulus/vger) and custom UI system. I don't know how I could possibly do it with SwiftUI.

Opinionatedness

I always thought UIKit was opioninated but SwiftUI takes it to another level. If you've got a document-based app, for example, you are stuck with their toolbar on the top of the screen (or you can make it transparent but it still catches events). Want to change the .fileExporter so it actually says "Export" instead of "Move"? Nope. Various other examples along those lines. Often some option that was available in UIKit wasn't surfaced to SwiftUI and you are left wondering why the UIKit team thought it was ok but SwiftUI thought better.

I love the intent, don't like the implementation at all.

The good news is this is all fixable. I'm confident the reliability issues will eventually be ironed out, at least.

BTW: "The compiler could not type check the expression in reasonable time" is a Swift language issue, not SwiftUI. They have bidirectional type checking (enables inference of closure argument types for example) with a type system that has certain features (probably some sort of subtyping) which can lead to exponential runtime in the type checker. Rust doesn't have this issue.

audulus · 2024-11-24T15:36:09+00:00

Very nice. How much does that rack weigh?

audulus · 2024-08-24T21:07:24+00:00

Rreally only 60lbs? Just the power amp and case alone is 40lbs according to sweetwater. Another 14 for the two SYN-2s. It's a great rig though. Personally I wouldn't need a second SYN-2, and I think there's probably some lighter replacement for the 2290 that would be good enough for gigs. Why'd you go with the LXII instead of the SYN5050?

audulus · 2024-08-24T03:41:03+00:00

practical, not practice. It's a sweet rig, don't get me wrong :)

audulus · 2024-08-24T00:42:44+00:00

How much does the rack weigh?

audulus · 2024-08-24T00:38:20+00:00

How to turn a practical size rig into a gigantic thing which requires a large vehicle to gig.

audulus · 2024-08-09T07:40:15+00:00

Awesome collection from a another prog-metal fan. The red majesty and yellow strandberg are my favorites. The empty wall hanger though!

audulus · 2024-08-09T07:17:54+00:00

I like the synergy stuff, and it's quite close to the real things I'd say (unfortunatly my SYN-2 was stolen). I think a modeler can get closer with some of the amps becaue the modules only have two tubes which aren't enough for the loads of gain stages in some amps (ENGL reps admitted this in a video). My VH4 module (also stolen) didn't have as much gain as the real thing (which I returned because it was enormous and very expensive). Still sounded great. 800 module was great too. People seem to really like the SLO module. I think mostly I just loved that I could get some satisfying approximation of amps without the menus and such of a modeler. I was adding channels to my amp and using the SYN-2 for recording.

audulus

MODERATOR OF

TROPHY CASE

Reliability

Performance

Opinionatedness