The crash of 2008 imparted many lessons to people who were only dimly aware of finance, especially how complexity was a way of disguising fraud and recklessness. That was really the first lesson of 2008: "financial engineering" is mostly a way of obscuring crime behind a screen of technical jargon.
--
If you'd like an essay-formatted version of this thread to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:
We’re having trouble with the “Somehow bypass this licensing scheme if the user compiled Cork themselves” part
Do you have any ideas on how to solve this? If you do and you help implement it, you’ll get a spot in the “Special thanks” section of the readme and within the app itself, as well as a free license or cash equivalent of the license
@davidbures Dumb suggestion: is it ok if “build it yourself" comes with a DEBUG requirement? ie. if you build and run from Xcode, you want to not do licensing checks, right? Just wrap the licensing checks in an #if DEBUG segment, then they'll be skipped only for debug builds. Want the release build? Modify the code or go get a license.
All this highlights the increasing divergence between the UK and the US when it comes to labor rights. Under the Biden Administration, @NLRB General Counsel Jennifer Abruzzo has promulgated a rule that grants a union automatic recognition if the boss does anything to interfere with a union election:
I was unable to push an archive build in #Xcode until I removed some preview content? The build otherwise works fine until I try an archive. Something feels wrong there but I don’t have time to do more than comment out the “offending” code
RDE is already quite big project with a few subprojects and it's hard to track feature requests, reports, milestones, their dependencies and to collocate and organize them properly and share publicly.
That's why for last few weeks I was looking at different project management/bug tracking solutions.
From what I found so far it seems that Bugzilla is the best option at the moment.
@ctietze We currently develop a Multiplatform SwiftUI App for both iOS/iPadOS and macOS. The app is non Catalyst! And so it often happens that we have to implement one and the same view separately for iOS and macOS because they differ too much in detail.
@lanodan I think checking the size of that is probably reasonable for things like memory allocation, though I suspect that it's just a list of all the types in stdint. (And why they can't just use sizeof is a mystery. It is really obvious what's going on if you see if(sizeof(size_t) == 8), and even trivial compilers remove the branch when compile-time constants are compared, but some preprocessor macro for _SIZE_OF_SIZE_T is at least an extra level of indirection, and it is practically guaranteed that they are using #if instead of just if.)
The foundational tenet of "the Cult of Mac" is that buying products from a $3t company makes you a member of an oppressed ethnic minority and therefore every criticism of that corporation is an ethnic slur:
This actually says something about cultural continuity because back in 2004, when Apple was a roughly $3Bn (not $Tn) company, it really was a minority pursuit in a sea of Windows, universally oppressed by corporate IT departments! It only shifted after iPhone ...
The foundational tenet of "the Cult of Mac" is that buying products from a $3t company makes you a member of an oppressed ethnic minority and therefore every criticism of that corporation is an ethnic slur:
If you'd like an essay-formatted version of this thread to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:
I used to call myself an Apple fan, but I’m clearly not unhinged enough to qualify these days.
Apparently their latest thing is to claim that nobody has ever in the history of governance tried to regulate access to market-making private infrastructure
OK, so, my HLSL struct definition in #unreal works fine in the material custom HLSL node, but the Niagara custom HLSL node apparently... can't have functions in structs?
Why the fuck isn't it on the GPU? Put it there. ... but, of course, ALL the code had to be bracketed in an #if GPU_SIMULATION so the code flat-out won't compile...
Pass it the wave specifications in a different format, because Niagara scripts can take a wide variety of formats.
If 1), I have to find a way to re-code everything.
If 2), I have to have THREE different ways of encoding the same waves.
DEBAG is not a typo: it suggests that the main code requires a paperbag to be present at all times while the app is being used, and the Swift ”if” macro-like code is a ”de-bag”, a workaround.
Hello, I'm Chris, or Kartoon (she/her)! kartoonkrazy on tumblr and pretty much everywhere else. I generally have no idea what I'm doing. things I'm into in no particular order
This is a script called m5.awk that I randomly found after reading a paper about it on the ACM website. The paper’s worth reading too but the script is just a piece of work. Commented to the brim, clean, and most importantly, useful as hell. it could be a replacement for m4. It allows you to embed AWK in text files, and...
> Another restriction is that the C compilers accept only a subset of the preprocessor
directives required by ANSI. The main omission is #if, since we believe it is never nec≠
essary and often abused. Also, its effect is better achieved by other means. For
instance, an #if used to toggle a feature at compile time can be written as a regular if
statement, relying on compile-time constant folding and dead code elimination to discard object code
We're happy to announce the results of our first #grants cycle!
Four projects were selected by our panel of advisors, and $2400 was disbursed by IFTF to support these projects. We had a range of proposals and the final slate shows great diversity - interpreters, accessibility, history, and sprouting new communities!
We are delighted with the results of this program - thank you all for participating!
Ice Cubes have some very visible slowdown when scrolling the timeline on the Vision Pro. I’ve tried everything I can, and I can’t isolate it. The profiler gives me nothing interesting, and I’ve been attempting to remove every view one by one and come to no real conclusion. I have no idea what is going on. My guess is that it’s the iOS micro stutters people are telling me about but more visible but I’m not even sure anymore.
@dimillian Have you tried profiling and looking in SwiftUI Instrument in Instruments.app? .help is one of the performance hogs in my experience, that's something I had to #if!os(visionOS) off. Another thing I found was the usage Buttons... (resolving button style was super expensive) so switched to onTap + hoverEffect + .accessibilityAddTraits(.isButton)
@isurujn previews are compiled (might be stripped from final binary with optimizations enabled). You have to explicitly wrap them in #if DEBUG to avoid compilation errors.
Wading in to the SwiftData waters and added saving to a context, and I’m impressed. Gave the app an infinite loop at the view layer and we’ll fix that later.
Doodled a couple candidates for a development and alternate app icon! Someone has to bring a little culture.
Just that tiny bit of progress today but the momentum is what’s important. #BuildInPublic#iOSDev
Today: separated main module sources from tests, fixed grid sizing, fixed app icon display, updated #if DEBUG exclusions for production. In-progress: session renewal, starting with local unit tests.
Well this is neat... (raw.githubusercontent.com)
This is a script called m5.awk that I randomly found after reading a paper about it on the ACM website. The paper’s worth reading too but the script is just a piece of work. Commented to the brim, clean, and most importantly, useful as hell. it could be a replacement for m4. It allows you to embed AWK in text files, and...