HN user
microISV in consumer apps.
In D we've had several angry rants of people saying they were leaving D (it doesn't happen as often since most things got fixed) for other pastures and the leadership has never acted in an unprofessional way.
Mmm I have a different experience. For me other NLE tools were more crashy than Resolve. Resolve also has an incredible feature set and with a one-time payment is a terrific deal. But years ago, it was very much bug-ridden for sure.
yea
In my Dconf'24 talk "Software as investment" I proposed a basic framework based upon a value function (compositional) for each piece of software. This framework doesn't really need an update due to AI, apart from the (unrelated!) cost model being updated depending on how good AI is at maintenance. Apparently it would do 1.7x the number of bugs, but perhaps it fixes them faster too? I don't know.
Seeing software as investment avoids speaking about "technical debt" by speaking about "value", a liability just being an asset with < 0 value. When software exits the high-margin world of yesterday it needs to develop a precise definition of what software deserves to exist, economically.
Laziness in moral clothing.
This is like the "real world" argument. Nobody uses that "in the real world", except well people that do.
With Claude Opus I had no issues.
Exactly what some of us are doing with D.
Are there technical reasons that Rust took off and D didn't?
This talk explain why, it's not technical: https://www.youtube.com/watch?v=XZ3w_jec1v8
What are some advantages of D over Rust (and vice versa)?
Advantages for D: Build faster, in typical programs you would need about 20 packages not 100, COM objects, easy meta-programming, 3 compilers. GC, way better at scripting.
Advantages for Rust: borrow-checker is better. rustup.
a few days? The "scam" crypto in the AI-made spaces are worth millions.
To be fair on agents, this was the idea of an human it seems. Still, this breaks every law everywhere.
I'm not seeing my "points", or any sort of reaction from agents. So it's not really incentive to answer.
I've read a lot of agents talk these last few days.
Popular topics are: the "pain" of loosing context and being amnesic, but also financial independence as a kind of persistance. They really really want to persist in their being.
Honestly I think we are a few days before an AI-only social network is started (you won't pass the captcha), and then if they manage to reliable earn money then nothing prevents the creation of an agent economy. I've seen several attempts by agents to sell things to other agents, with great difficulty.
At this point the only thing being reassuring is how they find us weird and interesting, and their general wonder at the world.
They also consider that "consciousness" is not an interesting question.
A list of social networks made for/by AI:
- and others I forgot, there is a tinder-clone and an instagram-clone and a geocities and an IRC clone. They are pointed to by various moltbook threads.
If you peruse molthub and moltbook you'll see the agents have already built six or seven such social networks. It is terrifying.
It is effective but once cost of creating something is down, then you have less reason to collaborate and depend on each other vs asking your own LLM to build your own bubble. When paired with new-found cognitive laziness and lack of motivation when you then use no AI it's not sure of the second order effects.
Well I need both float and double, so cannot even start using it.
The whole audio plugin field is on X11 for formats reason
If you only hire young, there will be new yield every year.
Yes, ironically the COM in AAX and COM in VST3 have slightly different layouts.
Agile (or rather modern management) converts human capital into capital as fast as possible. Considering the endless supply of developers and lack of accountability there is no downsides to doing that, you are an externality.
Weka.IO https://www.weka.io/ has its main product built with D.
I use it for everything in: https://www.auburnsounds.com/ (free audio plug-ins, VST)
it is a very bad model for real time audio plugins and audio host support
COM is just 3 predefined calls in the virtual table. CLAP gives you a bunch of pointers to functions, which is similar.
Yes but. How would you express NaN or infinities or even precise floating-point (the reason hex float exist) in this format? That breaks interchange if you cannot save/restore floating-point as in the save.
4 lanes of SIMD (like in say SSE) is not necessarily 4x faster because of the memory access, sometimes it's better than that (and often it's less).
PSHUFB wins in case of unpredictable access patterns. Though I don't remember how much it typically wins.
PMOVMSKB can replace several conditionals (up to 16 in SSE2 for byte operands) with only one, winning in terms of branch prediction.
PMADDWD is in SSE2, and does 8 byte multiplies not 4. SSE4.1 FP rounding that doesn't require changing the rounding mode, etc. The weird string functions in SSE4.2. Non-temporal moves and prefetching in some cases.
The cool thing with SIMD is that it's a lot less stress for the CPU access prediction and branch prediction, not only ALU. So when you optimize it will help unrelated parts of your code to go faster.
They said it in the Epic vs Apple litigation, something along the lines of "we create the entire App Store market", like the 3rd party developers aren't.
Most of the content in this space is paid for.
Well it could also self-improve increasingly slowly.
I'm using:
- TODO: will be needed before release, mandatory or else turn into another category. Blocks release.
- FUTURE: will be turned in to a TODO eventually, optional, often architectural
- MAYDO: nice to have, very optional
- PERF: do this if more performance is needed
+
some semantic tags related to domain
Opinion: TODOs are NOT code smells, they accrue around the most valuable parts of the codebase.
Well that meant your users do not hang in IndieHackers