jolt42

Actually the birth of Human Factors was related to this... Alphonse Chapanis, a psychologist working at the Army Air Force Aero Medical Lab in 1942, investigated the issue and discovered a design flaw. He observed that the controls for the flaps and the landing gear in the B-17 cockpit were nearly identical and located close to each other.

100%. The needs of the client rule, and REST rarely meets the challenge. When I read the title, I was like "pfff", REST is crap to start with, why do I care?

Would you roughly say 100x more portable?

The only way to verify is open that sucker up and count.

Just another tool that can be used for good or bad.

why? if nuclear weapons got the green light, do you expect a different outcome?

Coupling and Cohesion likely has nothing to do with the language.

Lisps don't support OO, concurrency like Go, or type checking but you can write a DSLs for them. Not useful? How about a rules engine?

The limitation with regex is that's it's context free, whereas a regular grammar is simpler and more powerful IMO.

Because they are really really difficult to get right almost as difficult as building a new language. But when they work well they can be a real boost.

The discouragement of macros I think is a knee-jerk reaction. Build around data structures and functions first, and then use the thinnest macros around that can be quite maintainable.

"poor insulator", seems like an odd statement, but it's all relative I suppose. It's certainly better than the masonry or steel that this will replace. But if you take the air pockets out of it, then it's not going to be as good, but likely better than steel.

IIRC, Microsoft was also charging Dell for a copy of Windows even if they didn't install it on the PC! And yeah OS/2 was ahead by miles.

> that kind of code is just too formulaic, transactional and often boring to do

No offense, but that sounds like every programmer that hasn't done front-end development to me. Maybe for some class of front-ends (the same stuff that Ruby on Rails could generate), but past that things tend to get not boring real fast.

As well as some-> (exit on null) and cond-> (with predicates) that are often handy.

Wish I hadn't been funding Intuit after using FreeTaxUSA this year. Maybe the import isn't as great, but I found it overall a bit more intuitive than TurboTax

Didn't Kurt Godel prove there will always be gaps?

I don't see it as a bigger leap than the internet itself. I recall needing books on my desk or a road trip to the local bookshop to find out coding answers. Stack Overflow beats AI most days, but the LLMs are another nice tool.

But not a calorie tax.

Maybe if you find the right local group, you can barter with your left overs?

100%. Dealing with legacy issues is much more laborious and also complicates hygiene.

It seemed to me TOPLink had this figured out, and then hibernate took it all away.

"frontend" is the wrong word, he should have said "web". Writing desktop UIs or mobile apps tends to be elegant. And probably "SPA frontend" as server-side UIs are also much cleaner.

The 3 branches of government were based on Isaiah 33:22: For the LORD is our judge, the LORD is our lawgiver, the LORD is our king. It sounds like a language that includes rules, but I don't think it's been invented yet.

Oh, you mean "Programmer #1" using the original assembly language?

For a gambler, yes, but for a biological system? Stuff falls apart, it's like any progress continually gets wiped.

Time means more entropy, so I would think that makes the calculation much more problematic, no?

I think I did something similar. I found a grassy gradual slope and had them go down it. They didn't have to think about peddling until they lost some speed.

@OP "Model our domain as a graph of attributes and relationships" and "generate resolvers". I'm curious what your model looks like so that you are able to "generate resolvers"? I had looked into using Malli as the model, but curious what route you took.

unless you are a regular seller, Amazon is completely not worth it, right?