NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


it's especially weird when they run into Python and start trying to apply all of the ones the language design obsoleted, saying the language is really hard because it fights them with an immune response.

it's even weirder when you realize modern Java has learned a lot of those lessons from languages like python

does java have a viral resevoir lurking deep in it's blogging intestines or something


You must log in to comment.

in reply to @NireBryce's post:

Honestly I've cultivated a theory for years now that Java - the pure, uncut stuff, before the modern facelift - actually breaks programmers' brains a little bit. Java devs are always the worst when I've interviewed them, and, as you've seen, they keep circling back to patterns which honestly emerged primarily because of Java's own type system limitations (like the FactoryFactoryFactory nonsense, or hell even just sticking everything into class methods even in languages which - like Python - encourage standalone functions). Even if their brains are glued back together later, those fracture lines remain.

so there's a complex morass here.

  1. java is the 2000s Business Language. So it's blogosphere is just absolutely polluted with consultantposting

  2. the consultants have no idea what they're doing because they're now third-generation-consultants, in terms of who trained them (especially at business schools)

  3. java culture is intermeshed with the consultancy culture, partially because oracle but sun before it provided those as services, and a cottage industry grew around it. see also: no one understands agile because the consultancy had to protect itself by inventing new ways to say "agile can have middle managers too it's ok please hire us to train yours"

  4. Java has the Oracle Aura of Ambient Dread ever since the buyout

  5. Javaschools especially did not really instill in people that java was just one language instead of How Programming Is

  6. actually java had some good ideas just please don't bring them to python. please. go bother common lisp instead

but most importantly

  1. the philosophy that grew up around java, as far as I can tell, in the gestalt, is that java would make programming easier to consistently budget for (and more outsourcable) by turning programmers into interchangable parts within the assembly line. This didn't work, due to the realities of software design, but there's a lot of damage done. Whether this was intentionally to drive down wages is unclear but honestly I don't think that's their intent, as wild as it is to say that about Oracle, since Sun was doing it before them.

I think this last point is also why the obsession with design patterns enough that ppl tunnelvision and don't notice when the patterns already exist in the language they're using, under different names and different shapes.