materielle

6 ms·

61.
by materielle 1y ago
But this is the problem. Our premier academic institutions shouldn’t merely exist as job training programs for big tech. If anything, tech is still one of the better off fields in the university. Look at history or literature programs for w
62.
by materielle 1y ago
The C++ standard committee is definitely smart. But language design requires sense beyond just being smart. They didn’t do the best with what they had. Sure, some problems were caused by C backwards compatibility. But so much of the complex
63.
by materielle 1y ago
I’d also point out, that even in the compiler space, there are basically no production compilers written in Haskell and OCaml. I believe those two languages themselves self-host. So not saying it’s impossible. And I have no clue about the t
64.
by materielle 1y ago
I agree with this, airline price discrimination is an example of the market actually working correctly. Most people could afford to pay more for airline tickets. It’s just that they’ve done the math and they don’t want to. I plan carefully
65.
by materielle 1y ago
I’m not sure that the library comparison really works. Libraries are maintained by other humans, who stake their reputation on the quality of the library. If a library gets a reputation of having a lax maintainer, the community will react.
66.
by materielle 1y ago
> At the expense of hollowing out domestic industry This doesn’t seem obvious to me. Trade happens because it mutually beneficial. The counter factual to reducing trade isn’t that we would manufacture the equivalent amount of goods here
67.
by materielle 1y ago
Python is about 35 years old at this point. It was the better language that had the better design and the fixed problems at some point in time. Sure, maybe a committee way back in 1990 could have shaved off of some the warts and oopsies t
68.
by materielle 1y ago
I think I understand what you are saying, and I agree. Google has all sorts of great infra projects that simplify complex domains. Those are solved problems now, so nobody notices it. The existence of incidental complexity isn’t evidence t
69.
by materielle 1y ago
Why stop there? We should bring back elevator operators. And station a traffic guard on every corner instead of traffic lights. Let’s bring back tool booth operators. And let’s delete Google calendar and bring back secretaries while we’re a
70.
by materielle 2y ago
Everyone is missing the point. Fine, maybe the math is off and it took 3 days instead of 2. The issue is that Cursor tends to be demoed for incredibly small, green, and simple projects. Most of us are working on codebases with at least over
71.
by materielle 2y ago
Yea I totally agree. This is selective memory. Perhaps there were peaks and troughs in individual technologies. Late 2000s / early 2010s felt like a good time for operating systems, for instance. But is everyone forgetting having to na
72.
by materielle 2y ago
This is the P in CAP theorem: partition awareness. I used to work on distributed systems, and network partitions were a frequent enough occurrence that they weren’t considered an extraordinary event. By that, I mean that we wouldn’t page du
73.
by materielle 2y ago
One interesting thing covered in the Ladybird monthly update videos, is that most of the web platform tests are text encoding tests for Asian languages. If you remove them, Ladybird is closer to 60% and Servo to 50%. Still good, and the poi
74.
by materielle 2y ago
Standard library omissions aren’t there just because. For almost any functionality missing in the standard library, you could point to 2-3 popular crates that solve the problem in mutually exclusive ways, for different use cases. Higher lev
75.
by materielle 2y ago
Most of the things people like about NYC were either: 1) Built at least 100 years ago. De-facto relics of a government and society that no longer exists. 2) Things built by the people in spite, not because, of its public policy and govern
76.
by materielle 2y ago
I was listening to a Titus Winters podcast, and I’m not sure he exactly put it like this, but I took it away as: There are two problems with automated testing. 1) tests take too long to run 2) difficult to root cause breakages. Most devs so
77.
by materielle 2y ago
I think everything you said is totally correct for open source library owners. But let me offer a different perspective: Hyrum’s law is neither a technical contract nor a social contract. It’s an emergent technical property in a sufficientl
78.
by materielle 2y ago
Go is definitely of the “worse is better” philosophy. You can basically predict what someone will think of Go if you know how they feel about that design philosophy. I remember that famous rant about how Go’s stdlib file api assumes Unix, a
79.
by materielle 2y ago
I love Go for writing servers. And in fact, I do it professionally. But I totally agree that for parsers, it’s not the right tool for the job. First off, the only way to express union types is with runtime reflection. You might as well be c
80.
by materielle 2y ago
The problem is that DRY principles have be cargo culted way past the point of being useful. People see two pieces of duplicate, or even similar code in a monorepo, and they feel the urge create some sort of shared directory to de duplicate
81.
by materielle 2y ago
That’s why I specifically qualified my comment “within the context of a typical crud api server”. I remember this being true 10 years ago. Java web servers I maintained had a huge problem with tail latency. Maybe if you were working on a 1
82.
by materielle 2y ago
To put this another way: the Rust borrow checker attempts to tie memory lifetime to stack frames. This tends to work well for most crud api servers, since you allocate “context, request, and response” data at the start of the handler functi
83.
by materielle 2y ago
I’m curious how Go stacks up against C# and Java these days. “Less languages features, but a better compiler” was originally the aspirational selling point of Go. And even though there were some hiccups, at least 10 years ago, I remember th
84.
by materielle 2y ago
To add onto what you’re saying, this is surely part of Google’s strategy: obfuscation through complexity. The anticompetitive schemes they engage in are so complicated and require so much background context that it’s basically impossible to
85.
by materielle 2y ago
Is there anything technical preventing Go from being like this? Besides the fact that nobody has put in the hard work to make it happen? Not a leading question, I’m curious if there are any technical complications with fast-reload Go.
86.
by materielle 2y ago
I would point out that there is a special syntax / api when you deference “any” in Go. And you are explicitly prompted by the language to consider the case where you receive an unexpected type. I think this is an important detail, beca
87.
by materielle 2y ago
If the company follows normal at-will employment practices, there would be no need to mention it. The fact that they explicitly call out this practice is probably a sign that they lay off a larger percentage of new hires compared to the ave
88.
by materielle 2y ago
https://blog.carlana.net/post/2021/requests-golang-http-clie... I don’t think that article discusses the timeout issue. So all the issues mentioned in that article, plus the timeout issue. The end result is you ha
89.
by materielle 2y ago
That’s definitely part of it. The other half is hyrum’s law. There’s a lot of situations in reasonable unordered map implementations where the elements, by chance, do happen to be ordered. Just due to arbitrary implementation decisions. B
90.
by materielle 2y ago
Interesting, I agree with the the main idea: in general I find Go a productive language, but there’s a few rough edges. The specific examples don’t ring true to me though. Instead of named arguments, use the functional optional pattern. An

More ›