james-mcelwain

People are leaving California because of the housing crisis, which is undoubtedly a huge issue, but is an indicator of massive demand to live in California, not that people are fleeing the state due to fiscal mismanagement

Their "list" is basically just a list of states with debt, that completely ignores their ability to issue new debt and generate revenue (i.e. that people actually want to live in California and not Kansas), while ignoring the fact that many of these states with "balanced budgets" provide basically no services and are liable to getting wrecked in times of crisis. I mean, the fact that Kansas is so high on this list should tell you all you need to know.

Pension is being used as a term of art here not how anyone uses it in standard parlance.

Mercatus is a Koch funded think tank -- hardly unbiased and a poor source here.

You're being willfully obtuse here. No one in the US would call their 401k a pension.

Is Nim a viable alternative to Rust? Didn't it just release 1.0? Their production users list[1] doesn't look very impressive. The size of ecosystem matters a lot.

[1] https://github.com/nim-lang/Nim/wiki/Companies-using-Nim

I really don't think my initial comment was that hostile, but I can see why it could be read that way. I appreciate what you're trying to say here, and should probably work on framing things positively to avoid this kind of contention.

Part of why the Raft paper is so excellent is because is does leave you feeling like you could explain/implement the algorithm. I don't want to discourage people from being excited about these ideas, because I am too.

That being said, I am generally frustrated by the lack of humility that many software engineers exhibit. "Easy" is a trigger word for me, and I really think is something that should be expunged from most of our vocabulary when referencing software.

Right, my point was just that there's no such thing as a "mostly works" consensus algorithm. By definition these algorithms are intended for systems that can't tolerate failure.

If you feel confident you've built a complex algorithm like this correctly on the first try you probably haven't. Hubris and distributed systems just don't mix.

Verifying correctness to back up our empirical claims is often the hardest and most overlooked part of software engineering.

I feel like setting up the tests to validate that your Raft implementation is actually correct would take at least a weekend by itself.

Not that I disagree with you, but 2-6 basically come down to "it lacks a Lisp-like REPL."

I do think that the REPL workflow is way underappreciated and missing in Intellij. What I like about it is that it still focuses on working on semantic intent rather than editing text. In this way, it's similar in some sense to the idea of working on S-expressions rather than text.

> See for example the abortions... are nonetheless lives lost due to the disaster.

Unless you have some additional evidence of euthanizing newborns or otherwise near-term pregnancies, abortions do not count as lives lost to the disaster to anyone but political reactionaries.

I'm taking issue with the use of the word "dramatically" not the claim that it could improve patient outcomes.

It's not like we're going around incubating healthy people -- you have to be pretty sick to get put on a ventilator. Even if the treatment turns out to be a net negative, most of these patients didn't have very good odds in the first place, so it's pretty unlikely it would affect the death rates "drastically."

This is also what I do, but it seems so antagonistic and deceptive. I want my relationship with my PM to be productive and collaborative.

I don't know if something is wrong with me, but I simply cannot "decompose" a single feature into 500 different sub-task Jiras.

I understand why it would be super cool if software worked like that, but I have to iterate on features holistically and sometimes speculatively.

At least for me, software development has never been able to be so cleanly broken down into "first, implement the button" type tasks.

But maybe I'm just dumb.

Was curious so looked this up -- the North American market is bigger than the EU by ~50 million people.

This is my experience especially with ORMs. It's really hard to optimize when your "top query time" list is just a list of your most frequently called methods, where there's no single obvious pathological case, but lots of little inefficiencies.

This might be the correct advice in many scenarios but is essentially playing with fire. A company that wants revenge could easily bankrupt you with even the smallest contractual leg to stand on. Your 200k base comp isn't going to look so sweet when you're paying a lawyer $1,500 an hour to defend you from some tech giant.

"Jamstack" has to be the worst name for an architecture ever. "Javascript", "APIs", and "markup"... uhhh you mean like what the entire web already runs on?

There's nothing wrong with Java generics. Reified generics are a design choice. As someone who uses a lot of non-Java JVM languages, I'm thankful interop is easier.

How does the size of the business change the material facts here? You shouldn't be able to take profit when you're sitting on top of a 0% interest government loan intended to keep you solvent.

It's important to remember that there are still a lot of front-end folks who aren't interested in application engineering, but still might find these frameworks useful. For those kinds of people, static typing is a harder sell.

For anyone else, yeah, they should probably be using TypeScript in 2020.

Look at the YouTube channel they linked.

This kind of Sinophobia is so unwarranted -- China has done the best to control this disease outside of maybe S. Korea.

> but I haven't seen it downplayed on the Federal level at all

We truly must be living in different universes.

> i've done medical billing systems too and it is, indeed, crazy but what's make you think the gov. would be any better?

Well, first of all, because there's no medical billing in M4A. It's free at point of service, so I'd hope they do better at billing considering they don't need to bill at all.

There's a huge, gigantic difference between not having a military at all and spending 1 trillion a year to be an imperialist superpower. It's almost like... there's a middle ground.

This only works if the assumption is that it would be equally safe for pilots to operate a new plane without training. I'm not willing to fly under that assumption.

No, it's a way of saying that Java != the JVM. The JVM's GC is not "awful" precisely because so many Java frameworks are awful.

> the JVM's awful GC

This just makes it seem like you are trolling. JVM devs have done more to advance state of art in this area than any other language. The problem is that most JVM apps just produce too much garbage, not necessarily that the algo itself is awful.

Either way, there's no such thing as an optimal GC algorithm, just different trade-offs depending on your use case. Not everyone cares about latency.