11,909 karma · joined February 22, 2016
https://celtera.dev
https://ossia.io lead dev
https://twitter.com/jcelerie
I mean in my case i'd be absolutely fine doing work that sucks infinitely if that means that my users are happy. It really drives me crazy all the discourse I've seen over the years about devs that care about their own quality of life/job. Like, no, the only thing that should matter to you is your users, no matter the job. If what makes them genuinely happy is for you to take dirt out of a hole and put it back, and on top of this you get paid, we live in completely different planets if you don't rush to the nearest shovel.
I don't know how it is in your country but where I grew up it's well-known that the cops will come knock at your door fast if you transmit at power or frequency bands you shouldn't be transmitting.
same reason I spent my entire career so far writing open-source code that anyone can copy ? (it's GPL, but imagine 100% companies actually caring about that). Ideas can't be owned.
More generally, do you really think humans randomly come up with new ideas, in any act of creation, such as art, science, etc.? Why do you think art studies and stuff like Oblique Strategies exist? How long should one wait for a specific random human without any formal education in physics to have 50% chance of coming up with a new workable theory of cosmology?
I don't understand this part. When I was doing freelance consulting, my job was quite often "come to our office, scan this 40 million lines codebase and fix stuff for the next week". It was never a problem to read and get up to speed completely unknown codebases if you have basic programming ability. Much harder to do something that fits floaty business objectives though.
I wonder if it's just a consequence of a gigantic training set full of comments completely out-of-date with the code, leading to the model considering this "normal"
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).
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
really says a lot that someone can say this apparently absolutely seriously
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.
> 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.
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.