asa400

9 ms·

91.
by asa400 10mo ago
Agreed - I like your phrasing of it. There are some good ideas in OOP. I don't know that I'd go as far as to credit OOP for those ideas, but things like polymorphism and encapsulation can be very useful. What I objected to was, as
92.
by asa400 10mo ago
No thanks, I'll pass on the amateur psychoanalysis. Good luck to you sir.
93.
by asa400 10mo ago
I'm sorry you felt the need to post this in response to a figure of speech. Please keep your moralizing to yourself. Thank you.
94.
by asa400 10mo ago
I worked on a project where a dev wanted to mock out the database in tests "for performance, because the database is slow". I almost lost my shit. Even funnier, this was all hypothetical and yet taken as gospel. We hadn't eve
95.
by asa400 10mo ago
I can’t concur with this enough. I’ve been on projects where mocking _literally made the project less reliable_ because people ended up “testing” against mocks that didn’t accurately reflect the behavior of the real APIs. It left us with fu
96.
by asa400 10mo ago
It's a question of incentives. For safety regulators, the incentives are all on the side of limiting acute downside (e.g. a plane crashing), not maximizing potential aggregate upside (e.g. millions of tons of fuel saved per year and mi
97.
by asa400 10mo ago
I wholeheartedly concur based on my experience with Rust (and other languages) over the last ~7 or so years. > If I call a function which returns an object of type T, I can safely assume the object lasts forever. It cannot be mutated by
98.
by asa400 10mo ago
Other than knowing this about SQLite beforehand, is there any way one could discover that this is happening through tracing?
99.
by asa400 10mo ago
> I assume you're on a quest to assert a "let a completely unregulated free market roar" position No. I’m genuinely curious, because I agree with you about how critical these components are. I ask because it doesn’t seem t
100.
by asa400 10mo ago
Clarifying because I think the downvoters maybe misunderstood the nature of my question: I meant, in the opinion of the parent commenter should the principals of Samsung etc. be jailed? I wasn’t taking a position myself, just asking what
101.
by asa400 10mo ago
> I might have a different take. I think microservices should each be independent such that it really doesn't matter how they end up being connected. The connections you allow or disallow are basically the main interesting thing abo
102.
by asa400 10mo ago
How much RAM should they be allowed to buy? Who should decide that?
103.
by asa400 10mo ago
Serious question: should the principals of the RAM manufacturers be jailed?
104.
by asa400 10mo ago
You don’t even have to train an AI. At this point, in lieu of evidence to the contrary, we should default to “it loses committed writes”.
105.
by asa400 10mo ago
> Hiring is not an entirely rational process Agreed! I'd go so far as to say hiring is irrational in the aggregate. The usual "rational" artifacts, if we can call them that (coding challenges, resumés, etc.) serve almost e
106.
by asa400 10mo ago
I'm not sure what this cheap snipe accomplishes. I've been writing Rust professionally and personally since at least 2018 and this has never happened to me. There are plenty of real criticisms one can make about Rust (I've ma
107.
by asa400 10mo ago
> Erlang is, by my accounting, not even a functional langauge at all. How do you figure? The essence of FP is functions of the shape `data -> data` rather than `data -> void`, deemphasizing object-based identity, and treating funct
108.
by asa400 10mo ago
> And yet, as the industry grew and all sorts of people from all sorts of backgrounds converged in this space, the tolerance and appetite for funky/terse waned in favor of explicit/verbose/accessible. It's probably fo
109.
by asa400 10mo ago
> One of my coworkers gave me some great perspective by saying, "at least it's not written in Bash!" I wish bash was the thing that was dying. As an industry, we need to make better choices.
110.
by asa400 10mo ago
> Rust is a cool language and I hope it eventually settles down enough to be considered for "real" projects. I keep seeing folks with this "when will Rust be ready" sentiment and it feels a bit dated to me at this poi
111.
by asa400 10mo ago
> what's the perception re: current blockers for widespread adoption? Years ago, it was nothing more or less than third-party libs and frameworks. That must be better by now, or there's a short-list of what's missing? It&#
112.
by asa400 10mo ago
From your experience, would you call these behaviors bugs, or are they more known issues that result from SQLites specific implementation quirks? What kinds of workloads were you throwing at it when these types of issues happened? Asking as
113.
by asa400 11mo ago
Whenever people bring up binary formats I have to bring up Erlang External Term Format (ETF)[0]. It's the native format Erlang nodes use to serialize data to communicate with each other, but it's just a simple Type-Length-Value bi
114.
by asa400 11mo ago
> Many people that adore Elixir also think Ruby is a no go, despite the latter being a strong influence. Arguments against Elixir tend to revolve around its lack of traction, not its lack of seriousness. Elixir is funny. I've done E
115.
by asa400 11mo ago
> unwrap() and the family of methods like it are a Rust anti-pattern from the early days of Rust. It dates back to before many of the modern error-handling and safety-conscious features of the language and type system. I think your argum
116.
by asa400 11mo ago
You probably know about these, but for the benefit of folks who don't, you can forbid slice access and direct unwraps with clippy. Obviously this only lints your own code and not dependencies. - https://rust-lang.github.i
117.
by asa400 11mo ago
Speaking as someone in the US, I've worked at multiple companies (some startups, some small businesses, some larger) that have either outright imploded or had mass department-level layoffs inside that 1-2 year timeframe. Some of them I
118.
by asa400 11mo ago
It's true that message sends with Erlang processes do not perform rendezvous synchronization (i.e., sends are nonblocking), but they can be used in a similar way by having process A send a message to process B and then blocking on a re
119.
by asa400 11mo ago
Sorry, this is going to be a slightly longer reply since this is a really interesting question to ask! Elixir (and anything that runs on the BEAM) takes an entirely different perspective on concurrency than almost everything else out there.
120.
by asa400 11mo ago
Thank you for saying it. I’m getting exasperated at how many people in the comments are making some variant of the “lazy programmer wrote code that took a shortcut” argument. Complex system failures are not monocausal! Complex systems are i

More ›