Does anyone have examples of people migrating from Go to Java? I suspect this has more to do with moving away from functional and/or reactive programming.
Go is 12 years old (1.0 in March 2012). Young compared to Java, but old enough for codebases to have gone through a few write-rewrite phases. Case in point - this thread is about code that Walmart got when it acquired a company founded in 2014.
Sure, but Walmart is moving from a niche language to a mainstream one. Significantly easier to make that business justification. Go to Java should require a lot more political capital to champion such a change.
For what it’s worth, the 2023 stack overflow survey said 14% of professional programmers used Go vs 1% for F#. (Java at 30%)
Given the description also describes moving from a custom event sourcing engine to Kafka it doesn't seem to be moving away from reactive programming. As much as anything it seems like something of an "Apache Effect" that some Enterprise Highly Paid Consultants came in, told them they were doing "everything wrong" and that everything would be better with off the shelf open source components and that the "best" language for working with off the shelf open source components is Java. Most of that isn't true in various ways, but the number of Enterprise HPCs that love Java despite that language's deficiencies is surprisingly high. (Though maybe not that surprising given Oracle owns Java today and has always directly and indirectly owned a lot of HPCs in the Enterprise space.)
There's a very strong "nobody ever got fired for choosing IBM" effect surrounding Java. I can list specific situations where I'd prefer another platform all day long. But there are only a few specific situations I can think of where I would say Java is not a defensible choice.
And giving advice that's optimally defensible is the Highly Paid Consultant's actual job. You don't bring a consultant like that in when you're playing to win; you do it when you're playing to not lose.
I've never seen such a big protest. The transit system in Hamburg was completely overloaded. People standing around Alster lake, you couldn't even get close to the actual point where the protest was scheduled to happen. Those protests possibly may be ineffectual and what not - they certainly weren't small.
Both Hamburg and Munich protests needed to be canceled in the middle of the thing because the huge crowds were considered dangerous (I think rightly so).
Haha yeah the world is just run by silly fools who make silly mistakes (oops, just drafted a law limited your right to protest - oopsie!) and just random/lucky investments.
> these guys don't know what they're doing, even if tens of billions of dollars are at stake
also known as "never attribute to malice that which can be explained by incompetence", which to my gut sounds at least as likely as a cui bono explanation tbh (which is not to be seen as an endorsement of the view that cui bono = conspiracy...)
I don't actually think (2) is part of the razor[1]. If it is, then it doesn't make sense because (1) is an absolute (i.e. "never") which is always evaluated boolean "true", therefore statement (2) is never actually executed and is dead code.
Nevertheless I agree with you and think (2) is wise to always keep in mind. I love Hanlon's Razor but people definitely should take it literally as written and/or as law.
There’s been attempts to revise the SQL standard to accommodate various types of temporality as a “first party” feature.
I think that we won’t see traction at the RDBMS “kernel space” until it’s in the SQL standard. There are many valid and complex options to choose from, and there are successful solutions in user space that aren’t overly burdened, performance-wise, from being in user space.
FWIW, the “audit table” approach is the approach that people who study this field gravitate towards. Mainly because it maintains consistent ACIDity in the database, and maintains Postgres as the single point of failure (a trade off vs introducing a proxy/polling job).
Makes a lot of sense to me. Intel's production cannot keep up and so it's only TSMC and Samsung with a big gap. I think some people will be surprised when TSMC starts taking more and more of the profit from the value chain in the next few years.
