hbrn

48 ms·

571.
by hbrn 4y ago
> As for when these tradeoffs are appropriate, hard to say And that is my biggest problem. If you don't know whether you need something, you don't need it. Or you just don't have enough expertise to understand why you need
572.
by hbrn 4y ago
Microservices and Serverless are another two. IMO the only hyped up piece of tech that was actually good in the last decade is containers (but not the orchestration, just containers).
573.
by hbrn 4y ago
To add to that, even if you have microservices everywhere on the backend, JWT is still rarely a good choice. Those services are typically exposed to customers via some sort of API Gateway/BFF. So if your clients don't speak to mic
574.
by hbrn 4y ago
Assuming "at scale" means you have no other option than horizontal scaling. At this point differences between databases start to shrink. Most of the complexity and features are being moved to the application layer, and your databa
575.
by hbrn 4y ago
Not necessarily, but could be. Have you heard of brainstorming? The worst thing you could do is to ban mistakes. Innovation is doing something that hasn't been done before. Inevitably that leads to mistakes. Being sloppy also leads to
576.
by hbrn 4y ago
Isn't it even harder to re-define names in a company? There might be 3 people involved in re-definition, but it affects 15 people. How are we going to notify those 15? Do we even know who those 15 are? Are we going to create a weekly r
577.
by hbrn 4y ago
> you are doing a bad job of producing an up-front system design Or, it could be that you're actually innovating and requirements are changing faster than you write code. A late change in requirements is a competitive advantage. The
578.
by hbrn 4y ago
Feels like we're going in circles. I guess that's what you get for nitpicking :) JIT can indeed do a lot of tricks to reduce JIT overhead. But you can't present that as a benefit of JIT over AOT: AOT doesn't have JIT ove
579.
by hbrn 4y ago
> Java specification says that NullPointerException would be thrown when we access the null object fields. Does this mean the JVM has to always employ runtime checks for nullity? Once again, we're talking about how JIT can be faste
580.
by hbrn 4y ago
Are you sure you're not confusing zero-cost with almost zero-cost? Even zerolog talks about negligible costs after most aggressive optimizations, not zero: https://github.com/obsidiandynamics/zerolog If you&#x
581.
by hbrn 4y ago
Can you show me how exactly does the optimization/deoptimization of unused branch look like? You need detect that you got into an unused branch and that requires... a branch! In order to be able to optimize presumably dead branches you
582.
by hbrn 4y ago
We're talking about optimizations that JIT can do compared to AOT. The link you shared talks about skipping compilation for certain branches to speed up the JIT compilation . Such optimization makes startup faster, but it doesn't
583.
by hbrn 4y ago
Nitpicking here. > JIT compiler can see that a function has never been passed a null object It cannot. It can only see that function has never been passed a null object so far . And the cost of such optimization might be that edge cases
584.
by hbrn 4y ago
If those two lines remove 100 of complaints per day but add 10, it's still a net positive change that creates value. Especially since special requests were never supposed to be a guarantee in the first place. The fact that one type of
585.
by hbrn 4y ago
What might look like a most successful set of design decisions for you, can be viewed as a set of unfavorable tradeoffs by somebody else. To squash or not to squash is a never ending debate precisely because of that. There isn't a righ
586.
by hbrn 4y ago
> But not because of Capitalism, despite it. The one country that made a difference self-defines as Socialist. You do realize that reforms that led to poverty reduction in China were deeply capitalistic? Allowing privatization, reducin
587.
by hbrn 4y ago
> Honestly pathos and emotions can guide us in my eye just as much as logos can. Emotions allow your biases to manifest, letting you focus on thousand suicides and turn a blind eye to famine for millions. And even feel virtuous while doi
588.
by hbrn 4y ago
> Capitalist exploitation of our natural resources is causing disasters and untold suffering all over the planet. And socialist/communist exploitation somehow has doesn't lead to the same consequences? Isn't China exploiti
589.
by hbrn 4y ago
> all we've gotten is mass suffering Do you really think there was less suffering 100 years ago? By what metric specifically? Over the last 100 years poverty rate has been steadily decreasing, hunger rate has been steadily decreasin
590.
by hbrn 4y ago
If they are so good at central planning, why do both Amazon and Walmart have 3rd party sellers?
591.
by hbrn 4y ago
I don't think you're arguing in good faith. > Proxies have been around for at least a decade Having Proxy described in ES5 standard and having it supported in browsers is two different things. IE market share at that time was a
592.
by hbrn 4y ago
I absolutely despise slow software. But what I meant to say is that performance of modern frameworks is comparable. There's a huge UX difference between 250ms and 500ms page render. Not so much between 25ms and 50ms. When I'm look
593.
by hbrn 4y ago
I'm surprised how many people are pointing to the halting problem. It might be the most well known thing about Turing Machines, but doesn't seem like the most relevant here. Turing equivalence seems more interesting. Intuitively I
594.
by hbrn 4y ago
Flow "early version" (0.1.0) was released in 2014. Now there's a chance that they had another version used internally at least 3 years prior, but at this point we're just speculating. But IIRC nothing in React docs at th
595.
by hbrn 4y ago
Big Five is based on factor analysis, it's hard to call it pseudoscience. They didn't invent traits and then came up with fake data to prove their model. It's the opposite: they used statistical methods to discover those trai
596.
by hbrn 4y ago
My comment was in response to "JSX with TypeScript" being a great feature of React. We may debate whether it's actually great, but this feature is accidental, there was no foresight. Facebook was using React in 2011, TypeScri
597.
by hbrn 4y ago
I think I can do a healthy disagreement without harassment. > Computers should work for us; if they can automate and enforce something, we should let them I agree. But in my experience type hints are often treated as a goal, not as a low
598.
by hbrn 4y ago
Because Proxy wasn't supported when React was designed. I bet if they were to design it a year later, they would go with Proxy. But it wasn't an option at the time, Proxy is not something you can polyfill. Now, the community doesn
599.
by hbrn 4y ago
Same here. I used type annotations before static analyzers became popular, and was quite happy with them (though I would not enforce them). They were a great source of documentation. And yes, like any documentation, occasionally they can de
600.
by hbrn 4y ago
All the major frameworks require you to work off a foundation that's built for high interactivity, and I believe going with one of the major ones (except Angular) is still a good bet. Technically you can use Vue as a library to add int

More ›