the fundamental flaw with that approach is that it is totally unreasonable to have government apps in anything other than open source and fully public systems. nothing else can really be trusted, and any private/closed source option should be disqualified from the get go.

the reason is simple: you can't trust private entities or opaque systems, and you can't trust government either, thus the solution has to be fully transparent or you're doing nothing.

the problem with that is that it is hard, expensive and/or inconvenient.

coding in go (or whatever) and transpiling is just an extra step on top of that. not without benefits, mind! there are surely many situations where that is appropriate. but that still doesn't mean it is universally the "right thing". which brings me to:

> just to avoid learning or making a new language

there simply is no "one language to rule them all" nor there ought to be one. my entire career has been about learning different languages, techniques, tools, systems, environments and workflows. lots of them, nearly non stop. javascript has its nice place, and i like it vanilla, in all its weirdness and unapologetic untypedness. :)

how is javascript not a real language?

> There's no reason to use an interpreted

there are loads and loads of reasons to use "interpreted" languages. that you can't think of even a single one while still pretending to be knowledgeable in the field is really intriguing.

> bloated, weird language

oh, i see, this is all just a religious rant. carry on!

if curious (or fomo) it would have taken you about 15 secs to find out what glassfish is, which is still probably 15 less than what you wasted on this mini rant. from there it's up to you to go down the rabbit hole.

nice, but too complicated. slice a cabbage, add some salt, pound it, stash it for 10-15 days, enjoy. easy peasy and delicious (optionally pour some olive oil, vinegar and pepper on the serving for flavour).

just make sure i has enough juice to stay covered. odds are it doesn't; popular wisdom is topping it up with some extra brine. i prefer white wine.

you can still call it spec-programming but if you don't audit your generated code then you're simply doing it wrong; you just don't realize that yet because you've been getting away with it until now.

really? it depends on the type of development, but ten years ago the coder profession had already long gone mainstream and massified, with a lot of people just attracted by a convenient career rather than vocation. mediocrity was already the baseline ("agile" mentality to at the very least cope with that mediocrity and turnover churn was already at its peak) and on the other extreme coder narcissism was already en vogue.

the tools, resources, environments have indoubtedly improved a lot, though at the cost of overhead, overcomplexity. higher abstraction levels help but promote detachment from the fundamentals.

so specific areas and high end teams have probably improved, but i'd say average code quality has actually diminished, and keeps doing so. if it weren't for qa, monitoring, auditing and mitigation processes it would by now be catastrophic. cue in agents and vibe coding ...

as an old school coder that nowadays only codes for fun i see llm tools as an incredibly interesting and game changing tool for the profane, but that a professional coder might cede control to an agent (as opposed to use it for prospection or menial work) makes me already cringe, and i'm unable to wrap my head around vibe coding.

we're told that we need connection, but what we seek in others is really ourselves: our meaning, our purpose, we need to matter. what we actually find in others is only the illusion of that. it works (usually) and it feels good but not necessarily for everyone and there are ways to do that all by yourself. just be nice to yourself and enjoy existence. some will contemplate you as a weirdo, but that's their conditioning kicking in. it may not be for everyone, but there's really nothing wrong with that.

i was raised in a crowded family. i had dates and got married and got kids. i have a few friends left, some family left, aquaintances, sport comrades, sporadic contact and interaction with all of them ... but i spend most of my time alone and doing my thing, and rarely get bored, days fly. sometimes i might feel empty, lonely, depressed ... well then i reach out, or just soldier on, or distract myself, i know it will pass. and i think everyone has such moments, i had them all my life, being permanently crowded just distracts you from that. all in all, looking back, i'm having the blast of my lifetime and this is how i want to live the rest of it.

-tracker, -alert or -status would be more proper titles.

white on dark grey with phosphor green around? not really.

no, it isn't. we need both, they're different aspects of the same thing. hyperfocusing on the former and disregarding the latter is just as bad as doing the inverse, and is exactly the problem i was describing.

if you're building real systems you should focus on both.

> Coupling as Hom-Set Size ... The second interface is easier to implement, test, mock, and evolve.

i would doubt that. this just hides the complexity of multiple interfaces inside single, more general interfaces. if those "arrows" actually exist you will have to test and evolve them anyway, and adding some extra classification level does little apart from adding complexity.

> Pipelines ... Why This Matters ... Testability: Each morphism can be tested independently

i agree ... and this just contradicts the previous point about hom-set size.

> The arrows are what matter.

everything matters. i'm aware of the benefits and appeal of category theory, but i don't see the need to shoehorn it into everything, this just seems an example of evangelization of extremes. iow: if your only tool is a hammer everything looks like a nail, and that's not conducing to good design.

i barely got to play with one for a few hours during an "ai" course, so i didn't really figure much of it out but ... oh yeah, it was "cool"! also way-way-way over my budget. i then kept an eye for a while on the atari transputer workstation but no luck, it never really took off.

anyway, i find this article quite out of place. what hordes of romantically spoiled lisp machine nostalgia fanatics harassed this poor guy to the extreme that he had to go on this (pretty pointless) disparaging spree?

also, qa is simply not optional, and agile actually stresses that pretty strongly.

i still remember when tables were forced out of fashion by hordes of angry div believers! they became anathema and instantly made you a pariah. the arguments were very passionate but never made any sense to me: the preaching was separating structure from presentation, mostly to enable semantics, and then semantics became all swamped with presentation so you could get those damned divs aligned in a sensible way :-)

just don't use (or abuse) them for layout but tables still seem to me the most straightforward way to render, well, tabular content.

then again i would admit that this news is kind of off-topic here, but still ... there's a difference between moderation and outright censorship. in the land of the free! i wonder if all these paid buffoons realize how poisonous this is and that it is backfiring.