A few nerds like us getting all wrapped up in environmental impact is going to be overshadowed by 1 day's worth of laptops bought at a single Costco. Unless you're able to affect a large group of people (ie: what Framework is doing), I wouldn't get too worked up about the impact of custom PCBs vs old ThinkPads - on any reasonably scale, it just doesn't matter.
I agree, it's probably a better idea to stick to something that was sold in high volume - if only for replacement parts down the road. If one really needs low power, an older M series Mac would also suit the bill (sacrificing many of the other benefits of course).
It's substantially worse on the JVM. One's intuition from C just fails when you have to think about references vs primitives, and the overhead of those (with or without compressed OOPs).
I've met very few folks who understand the overheads involved, and how extreme the benefits can be from avoiding those.
Conversely I've met many folks who come into managed environments and piss away time trying to wrangle the managed system into how they think it should work, instead of accepting that clever people wrote it and guidelines when followed result in acceptable outcomes.
The sort of insane stuff I've seen on the dotnet repo where people are trying to tear apart the entire type system just because they think they've cracked some secret performance code.
In what way is it worse? The range of values they can contain is well-specified.
And you have a frame with an operands stack where you should be able to store at least a 32-bit value. `double` would just fill 2 adjacent slots.
And references are just pointers (possibly not using the whole of the value as an address, but as flags for e.g. the GC) pointing to objects, whose internal structure is implementation detail, but usually having a header and the fields (that can again be reference types).
Pretty standard stuff, heap allocating stuff is pretty common in C as well.
And unlike C, it will run the exact same way on every platform.
My favourite JVM trivia, although I openly admit I don't know if it's still true, is the fact that the size of a boolean is not defined.
If you ask a typical grad the size of a bool they will inevitably say one bit, but, CPUs and RAM, etc don't work like that, typically they expect WORD sized chunks of memory - meaning that the boolean size of one but becomes a WORD sized chunk, assuming that it hasn't been packed
". While it represents one bit of information, it is typically implemented as 1 byte in arrays, and often 4 bytes (an int) or more as a standalone variable on the stack "
Man so much of this thread is full of such high minded philosophizing, it's like we're debating wine instead of talking about interfaces for doing things.
Like, maybe I just want to make an interface to configure my homemade espresso dohickey, do I have to wear a turtleneck and read Christopher Alexander now? I just wanted a couple buttons and some sliders.
We don't all have to be experts in everything, some people just need a means to an end, and that's ok. I won't like the wave of slop that's coming, but the antidote certainly isn't this.
Why do you want sliders when a config file would do the same just fine?
It's true that design theory writing is annoyingly verbose and intangible, but that doesn't make it wrong. Give someone a concrete language spec and they will not really know how it feels to use the language, and even once they do experience its use they will not be able to explain that feeling using the language spec. Invariably the language will tend to become intangible and likely very verbose.
But to answer your question: no, it's of course perfectly serviceable to just copy the interface others have created, and if the needs aren't exactly the same you can just put up with the inevitable discomfort from where the original doesn't translate into the copy.
Don’t be so anti-intellectual, there’s enough of that around. A simple problem is going to have a small set of simple design solutions; the philosophising readily admits that. Nothing’s getting in your way.
Those bug bounty programs now have to compete against the market for 0-days. I suppose they always did, but it seems the economics have changed in the favour of the bad actors - at least from my uninformed standpoint.
That still exists in the OSS world too, having your code out there is no panacea. I think we'll see a real swarm of security issues across the board, but I would expect the OSS world to fare better (perhaps after a painful period).
There was a time when this kind of thing would fly. When the one in charge is a giant orange child-man who can't keep a consistent thought across a single sentence, it makes it clear that the whole thing is narcissistic theatre. It doesn't surprise me that his underlings would try to emulate it, and do a bad job in the process.
I don't like being a part of the reactionary 'orange man bad' crew, but this is really shockingly bizarre. It's not the kind of behaviour you expect from a real leader of a real superpower. And it does make you think - perhaps there's something to be said about the USA not being nearly the power that it once was, and maybe this is what it looks like after you crest the apex of power.
I knew a guy who found an interesting 3d printing niche: 2 way radios for professionals (mainly SAR crews) are always getting fetched up on clothing, and you're often finding the radio turned off because the knobs got moved. Dumb problem, should have been solved by fundamental engineering years ago - but whatever. He built a 3d printed shroud for a variety of popular radios, and now makes a living selling these.
He's a tech guy, but no engineer. He saw the need (he works on a SAR team), saw the solution and made it happen. Inspiring, really.
I do a bit of 3d printing stuff myself. Personally, I'm attracted that it's getting more professional. I can use it as the impetus to learn real engineering/CAD, etc. Not in an "I'm an engineer" way, but still using real principles to make better things. You don't have to be intimidated if you keep your identity small and let it inspire you instead.
I've been having ongoing issues with a manager who responds in the form of Claude guided PRs. Undoubtedly driven from confused prompts. Always full of issues, never actually solving the problem, always adding HEAPS of additional nonsense in the process.
There's an asymmetry of effort in the above, and when combined with the power asymmetry - that's a really bad combo, and I don't think I'm alone.
I'm glad to see the appreciation of the enormous costs of complexity on this forum, but I don't think that has ascended to the managerial level.
> ...a manager who responds in the form of Claude guided PRs
I think the job of a dev in this coming era is to produce the systems by which non-engineers can build competently and not break prod or produce unmaintainable code.
In my current role, I have shifted from lead IC to building the system that is used by other IC's and non-IC's.
From my perspective, if I can provide the right guardrails to the agent, then anyone using any agent will produce code that is going to coalesce around a higher baseline of quality. Most of my IC work now is aligned on this directionality.
reply