Jausoft

Peace & Collaboration

@java bump

@java Hey official Java channel, contacting you to discuss collaboration regarding bringing back some more desktop- and embedded/mobile graphics features? I surely could need support/funding for our JogAmp project for the benefit of all. Thank you.

JogAmp Release 2.6.0 jogamp.org With (pre-)builds for linux-amd64 linux-armv6hf linux-aarch64 freebsd-amd64 macosx-amd64 macosx-aarch64 windows-amd64 android-aarch64 android-amd64 #Java #OpenGL #crossplatform #computergraphics

and when static reflections finally hit availability (C++26 in .. err .. 2028?) .. will love to drop enum-macros and the macro diversion (run- and compile-time) for the static reflection tools.

C++ printf for runtime fun and compile-time safety? #jau_cfmt_header" target="_blank" rel="nofollow noopener">jausoft.com/projects/jauli… (I offload my general little gimmicks to this 'jaulib' git-repo, using it as a submodule in other projects)

some hindsight clips using Gamp w/ Graph shapes and a simple solar shader for fun. will evolve to more .. baby steps :) jausoft.com/cgit/gamp.git/…

@corecpp FINALLY - thanks folks! Hope its flexible enough to get rid of our 'dear unbeloved macros' :)

Static reflection is finally landing in C++26. This week, we’ll walk through the new reflection syntax, explore concrete examples, and start answering the real question: What does this unlock for modern C++ design? 👉 meetu.ps/e/PNMhv/2DHcm/i #cpp #cplusplus

@the_moisrex .. and me just using 'new things' if there is a true benefit visible to me. So less is often more. Being a C++ user since its inception, so learned all the 'new stuff' and loving the (atomic) memory model, compile-time expressions etc etc. The bits and math std also improving.

@JausoftBits I wouldn't call std::ranges perfect, but they seem to be satisfying to use sometimes, but as long as the control flow is not complicated.

Compilers still can't fully optimize away C++'s ranges overhead. Compilers still can't fully optimize away C++'s ranges overhead. Compilers still can't fully optimize away C++'s ranges overhead. Compilers still can't fully optimize away C++'s ranges overhead.

@Support @Support further, a well meant reply is showing up as 'probable spam'. Looks to me I am shadow banned of some sorts. Pls resolve or at least explain. Thank you.

@Support it says 'not hasn't posted' when viewing my account 'in public' (from a browser not logged into an account). Can you fix it please?

Elite's Cobra MKIII (by my son hacking in Gamp)

I was enthusiastic, sadly didn't turn out as promised :( The war is still going on, what a disaster.

I for one is grateful that the biggest war sponsor party has finally withdrawn from sponsoring the war continuation and thereby ending the massacre of people (any side). Now hoping for a proper security deal solution, dropping sanctions and peace & prosperity of course. peace

@esrtweet .. but can you trust the the spec/code analysis? Maybe as a review hint, coverage ... but IMHO that's it to not literally fall into the YOLO department :)

We only have one term for the evolving mode of writing software cooperatively with an AI - "vibecoding". I think we need at least one more term, because there's a spectrum of techniques being explored and "vibecoding" can describe at most one end of it. At one end of the spectrum is what I think of as YOLO coding, and I'm tempted to compound-word it as "yolocoding". That's where you describe an application that you want and just tell the computer to grind on your informal description until it thinks it's done. I never do this. I hear stories about people doing this ("I wrote an entire videogame in 3 days!") and getting good results. I'm not sure I believe them. I inhabit the other end of the spectrum, where you ride the AI like a fine warhorse. You start by tossing an informal spec at it, then you and the computer iterate on both the spec and the code. It does the moving and supplies the grunt, you do the steering. I'm not sure what to call this. "Symbocoding", maybe. You and the AI are symbiotic, more than the sum of the parts. I think when people talk about "vibecoding" they usually mean something more towards the yolocoding end of the spectrum. I don't think that's where you'll get high-quality code from, and where the big productivity gains are. I could be wrong, but whether I'm right or wrong I think we at least need to be able to articulate the difference between fire-and-forget and a highly interactive, carefully directed approach. Yolocoding. Symbocoding. Are these the right words? I don't know, but I'm sure the distinction is important.

@Support sorry it says 'JausoftBits hasn't posted', please fix or explain please

C++ Compiler Support - cppstat.dev - en.cppreference.com/w/cpp/compiler…

Salivating to use C++26 reflections to remove the many macro hacks for e.g. enum utils jausoft.com/projects/jauli…

Improved JOGL Integration in VTK (JogAmp 2.6.0) jausoft.com/blog/2025/09/1… JOGL support in Kitware’s VTK has been improved with JogAmp v2.6.0 and merged on the VTK master branch.

@TheAhmadOsman so old fashion and inefficient, use a O(1) hash map, always ;-)

for loops are all you need btw

@TheAhmadOsman maybe I should setup such a website with a IBAN or credit card payment /sarc Sick :)

vibe coders, secure your systems with this tool in 1 easy step

JogAmp is back on Sonatype's Maven Central ;-) - Read about the process + issues here jausoft.com/blog/2025/09/0… - And perhaps JogAmp's maven scripting readme here jogamp.org/cgit/jogamp-sc… #JogAmp #java #jogl #maven