> The credits for my code are protected (with the GPL you have to tell where your code originates from)
But that's literally anathema to the spirit of GPL. Copyleft exists only as a reaction to copyright which is sadly ingrained in legal systems, but the original thought about free software, at the time of GPL inception, is that in an ideal world, copyright shouldn't exist for software ; it's leveraged by GPL only to protect against abuse of copyright holders that could close open code, which is thus made impossible "legally" with the GPL. AI makes this distinction fal into "practically" as pretty much anything is "open" for individual use now (e.g the only use that matters).
Attribution and copyright are separate. Who says that, even if copyright didn't exist for software, attribution also wouldn't?
If anything, the remark that I have to make to the parent is that in principle attribution is also required by non-copyleft licenses. However, I doubt it's respected for the hundreds of crates or npm modules in a typical Rust or JavaScript project...
Even the true copyright abolitionists (who want companies like Oracle to be able to fork their software and make a billion dollars releasing the binaries) still use MIT license which requires attribution.
I'm a copyright abolitionist, but I think Oracle should be required to release the source code with their binaries as a basic consumer protection. I also don't care about attribution.
> In both photoshop and painting, the human using the tool decides what strokes to use.
except for the million posters and album covers unironically made with a real photo passed into one of photoshop's "Artistic" filters to make it look like some impressionist painting
Well what's better ? I have so many pictures of posters of old events or storefronts saved on my phone because they were so astronomically bad it'd have been better to not have any poster at all. Today's AI makes it look even worse but I'm hopeful that in five years we'll all live in a world generally more agreeable to look at and not "concrete with pink and yellow fluo paper smashed on top of it" like https://www.alamy.com/stock-photo/music-poster-wall.html
or
https://www.alamy.com/stock-photo/france-poster-wall.html?ps...
because the cost of making things enjoyable with more colour and detail will have come down. Maybe we can finally go back to Art Nouveau if the cost of making it comes down!
As I said, "Today's AI makes it look even worse". But the post makes me hopeful than in a couple years, actually good graphic design can come out from AI. It still looks terrible and AI even for the best posters it highlights, but noticeably less than the random ice cream or coffee shop where I live with fully ai-generated interior design, memorabilia and menus.
I mean I understand that this can happen, my point is that we should code things in a way where the huge majority your code will still work no matter if you have an old rhel box or the latest archlinux, just like today we can port doom to pretty much any platform without too much trouble.
> I only have the nagging question that if it’s so easy, why would the clients not do it by themselves?
I mean, that's exactly what's starting to happen, we have more and more clients to whom we propose a quote and their answer is "guess i'll just vibe code it" or come to use with an app that they vibe-coded and does the job, and they're content with it. So far it seems to work out just fine for them.
I was wondering "hopefully C++ allows you to pick across these axes so that you can build yourself the async primitives that work best for the problem at hand" and then: yes!
> We cannot attribute C++ to any particular design point in the taxonomy provided in Table 1 because each axis is configurable. Although elegant and neutral, the choice of full programmability makes each library an async dsl; knowledge transfer between projects within the same language becomes exceedingly difficult.
It is not if you think in terms of these axes and which solve your particular problem and not any particular specific design. Take for instance the simplest program one can imagine: a network video player. E.g. some server sends you RTP audio & video frames and you have to play them back correctly, with a nice GUI on top.
If you want to do this in a way that is as efficient as possible you need to be aware of all possible ways of async interoperation:
- connecting & receiving packets from the network in a classic network state machine where coroutines shine
- handling vsync vs not-vsync for displaying the video frame
- conforming to whatever async paradigm the hardware video decoding system you want to use is going to provide you with, e.g. Intel QuickSync vs VideoToolbox vs NVDEC...
- handling the synchronous model of audio playback driven in pull mode
- handling the synchronisation between audio / video, and thus the async patterns that support multi-threading as your audio thread can't be your video or GUI thread
- handling the async model of your GUI library for your play / stop button's callbacks.
There's zero chance that a single async model fits all of these equally well without tradeoffs, so you have to have the knowledge anyways.
Agree with your post except the adjective "simple" for a network video player.
Decoding video/audio and talking to the right OS APIs and GPU is far from simple. It is reasonable to implement a http1 client from scratch by hand. For decoding, you need libraries/dependencies. And suddenly you have to find the intersection of dependencies that play nice in your async model of choice.
> A human given a task that requires internet and given a system with no internet would most likely raise the issue to their superiors or otherwise go through official channels to have the tools available to do their job.
i'd be curious to see a study on this. I'd guess it'd be closer to 60/70% compliance and 30/40% "trying to hack things" for humans.
imagine picking some Vue framework over Qt when talking about "the stable road future kids walk down to become professionals". There's software written today in Qt that traces back all the way to the mid 90s and are still top-of-the-line for their business.
The project I'm working on has been based on Qt since Qt 4 era, has been through people vouching for JavaFx, Angular, JUCE, React, Electron, and a dozen other frameworks over Qt, and had entire competitors based on web tech come and wither. How many Vue software will still be written in Vue 20 years from now ?
Structurally, Qt is sometimes worse given the compatibility issues. There are desktops where Qt5/Qt6 software runs fine if you can get it to compile, but the GL interface has been broken on many platforms for over a decade.
If folks don't plan on maintaining things after a release cycle it no longer matters how one ports disposable code. On mobile the App life cycles are short. Quasar does exactly what Qt has been doing for years, but just abstracts the compilation pipeline for each MacOS/Win11/Android/iOS/Linux platform. For simple stuff it works fine, and generates solutions in under an hour.
>How many Vue software will still be written in Vue 20 years from now ?
Probably all of them in their bloated glory, as the build artifacts do not rely on a single unstable external fragile framework library heavily coupled to the operating system releases.
Personally I prefer wxWidgets for desktop, but it is not appropriate for every project. =3
> There are desktops where Qt5/Qt6 software runs fine if you can get it to compile, but the GL interface has been broken on many platforms for over a decade.
do you have example / bugreports of this ? for my app I run tests across a wide range of laptops, platforms and distros, across nvidia / intel / amd / llvmpipe / ... and it all works fine. hell, with the help of Claude I managed to port back the current dev branch of Qt6 back to Windows XP, with working OpenGL.
But that's literally anathema to the spirit of GPL. Copyleft exists only as a reaction to copyright which is sadly ingrained in legal systems, but the original thought about free software, at the time of GPL inception, is that in an ideal world, copyright shouldn't exist for software ; it's leveraged by GPL only to protect against abuse of copyright holders that could close open code, which is thus made impossible "legally" with the GPL. AI makes this distinction fal into "practically" as pretty much anything is "open" for individual use now (e.g the only use that matters).
https://www.gnu.org/philosophy/fsfs/rms-essays.pdf
reply