HNHacker News
TopNewBestAskShowJobs

morning-coffee

412 karma · joined May 9, 2023

submissionscomments
morning-coffee··on Fair coins tend to land on the side they started
Well, I suppose if you need fodder to fill your CV, this is one way to do it.
morning-coffee··on We Built a Self-Healing System to Survive a Concurrency Bug at Netflix
Also uttered by others who thought borrowing money was more important until they could figure out a way to control spending.
morning-coffee··on Programming languages that blew my mind (2023)
Nice article. Amazed they came across Prolog but not Forth!?

Prepare to have your mind blown: https://ratfactor.com/forth/the_programming_language_that_wr...

morning-coffee··on My Time Working at Stripe
Very well said and spot on. Thanks for posting.
morning-coffee··on My Time Working at Stripe
Exactly... if you want to be miserable at work, by all means, "slack off as much as possible".

I think we forget the big picture that "no one gets out alive" and that it's up to each of us to spend the time we have in a way that makes us happy. If you can afford to not spend 1/3 of your time at a job in order to fund the remaining 2/3 of your existence, lucky you! But if not, choosing to slack off at a job you hate is essentially choosing to throw 1/3 of your life away being miserable. (Not judging if that's your choice, but its baffling to me.)

morning-coffee··on The 1600s were a watershed for swear words (2022)
TIL that `false` is (was) a swear word. (I just hope the compliance checker for my source code doesn't start flagging it, as I'd hate to have to replace them all with `!true`... as that just makes the code read like flam-flam.
morning-coffee··on Async Rust is not safe with io_uring
Where do you conclude "Rust promises I/O safety in the future"? An RFC is not a promise to do anything... it may represent a desire... a possibility, but you taking that leap and implying a promise is a flagrant misrepresentation.

Now let's take "the future" part... you seem to be impugning Async Rust for something it's not even purported to do in the present. What's the point of this?

You found a bug in monoio it seems... I don't see the argument you've presented as supporting the premise that "Async Rust is not safe".

morning-coffee··on Why Safety Profiles Failed
> "No mutable aliases" is a mistake; it prevents many useful programs.

Yes, it prevents many useful programs.

I think it also prevents many many many more useless broken incorrect programs from wreaking havoc or being used as exploit delivery vehicles.

morning-coffee··on My negative views on Rust (2023)
If your goal is to converge on correctly functioning software, you know, for the benefit of the users of it, then fail-fast can help. If your goal is to optimize the sleep patterns of devops people and make changes to code without testing before releasing it to production, yeah... do what you need to do. :)
morning-coffee··on My negative views on Rust (2023)
First, things don't panic a lot in my experience writing Rust for the past three years. Second, when things do panic, it indicates a defect in the code that needs to be fixed. Aborting the program with a stack dump is the perfect behavior for seeing the state and the invariant that was violated and then figuring out the fix. Contrast this to C or C++ "limping along", usually until a later invariant causes a crash and being further away from and obscuring the true root cause, and we see why C and C++ code is generally still so bug-ridden relatively speaking. Fail-fast is not just a buzz word and program bugs are not recoverable errors. See https://joeduffyblog.com/2016/02/07/the-error-model/
morning-coffee··on The Rise of Worse Is Better (1991)
> Rust will only protect me from things my customers don't care about and don't understand.

Are you suggesting your customers don't care about CVE's, even indirectly when it affects them?

morning-coffee··on Why does man print "gimme gimme gimme" at 00:30? (2017)
One man's funny easter egg is another man's non-deterministic trigger for errant behavior in their workflow with possible real-world consequences, I suppose...

Yet another reason I have a hard time trusting software that is the product of integrating many disparate pieces with different engineering processes into something used in any life-safety or mission-critical application.

morning-coffee··on Human genome stored on 'everlasting' memory crystal
Yeah. That and

> a revolutionary data storage format that can survive for billions of years

Clearly it hasn't been verified to be able to survive for billions of years, but it is thought to be able to survive for billions of years based on extrapolation from tests done over time scales multiple orders of magnitude smaller.

morning-coffee··on The Strange Case of the Rogue HP-12c Calculator
Over my thirty some years of software development, I've witnessed many new entrants to the field not being aware of certain fundamentals learned long ago. I would theorize it's going to become more and more likely as patience for acquiring a deeper understanding, in general, among engineers I work with now seems to be at an all time low. Now-a-days it seems the move fast and break things mentality has taken over.
morning-coffee··on QUIC is not quick enough over fast internet
The UDP optimizations are already there and have been pretty much wrung out.

https://www.fastly.com/blog/measuring-quic-vs-tcp-computatio... has good details and was done almost five years ago.

The solution isn't in more UDP offload optimizations as there aren't any semantics in UDP that are expensive other than the quantity and frequency of datagrams to be processed in the context of the QUIC protocol that uses UDP as a transport. QUIC's state machine needs to see every UDP datagram carrying QUIC protocol messages in order to move forward. Just like was done for TCP offload more than twenty years ago, portions of QUIC state need to move and be maintained in hardware to prevent the host from having to see so many high-frequency tiny state updates messages.

morning-coffee··on QUIC is not quick enough over fast internet
There are no ACKs inherent in the UDP protocol, so "UDP offload" is not where the savings are. There are ACKs in the QUIC protocol and they are carried by UDP datagrams which need to make their way up to user land to be processed, and this is the crux of the issue.

What is needed is for QUIC offload to be invented/supported by HW so that most of the high-frequency/tiny-packet processing happens there, just as it does today for TCP offload. TCP large-send and large-receive offload is what is responsible for all the CPU savings as the application deals in 64KB or larger send/receives and the segmentation and receive coalescing all happen in hardware before an interrupt is even generated to involve the kernel, let alone userland.

morning-coffee··on ReMarkable Paper Pro
We've reached "peak something" with this much collective energy spent contemplating an expensive and complicated "solution" to a problem that is solved pretty simply and cheaply by a good spiral bound notebook and a nice pen.

I love this marketing soundbite too:

> “reMarkable gives me the deep focus required to work on complex problems.”

Mmmm. Yeah. I usually have to find a quiet place and eliminate distractions to get deep focus, but nice to know I can just carry this new device around with me and never lose deep focus!

morning-coffee··on Small asteroid to hit Earth's atmosphere today
> On the other hand, what's the chance of something like this happening with a much bigger asteroid.

The same as it's always been, which is to say you can live your life without worrying about it.

If our technology advances such that we can observe/find more and more of these, that doesn't affect the chances that a particularly sized asteroid hits the earth or not.

morning-coffee··on There's a place for everyone
When you use the word "everyone", curious if you really mean it considering that set contains individuals like Adolf Hitler, Shiro Ishii, Josef Fritzl, etc?
morning-coffee··on The Art of Finishing
Came to mention same thing I heard from a CS instructor in a freshman class way back in 1987... "Software is never finished, only abandoned."

But I'm curious to know details about what this means:

> number more the 3 nodes in a PERT serial traversal, and do not have redundant options.

Would you mind elaborating or providing a bit more context I can go search on and learn about? Thanks!

morning-coffee··on The Art of Finishing
Same! For me its some combination of paradox-of-choice for what to go learn about or work on next combined with variable-ratio-reinforcement compelling me to practically do a depth-first traversal of all the cool possibilities.

I think at some point I'll need to turn it all off.

morning-coffee··on The Art of Finishing
I really like this take! I've been doing software professionally for over thirty years, and really relate to all of the discussions here and the root post. I typically beat myself up about "why is this task taking me so long?! it should be easy by now!", etc. But it's likely because I typically take the "focus on the next hardest problem first, otherwise I'll only have all the hard problems to solve at the end" route, and have to use the high-power gear all the time.
morning-coffee··on Experience the Apollo 11 Lunar Landing
I love it... that's a great way to present it.

Man, those folks were impressive to be juggling all that information and have the communications processes in place manage it all... and calmly. (Steely-eyed missile men, indeed.)

I was born a month after they landed, and while growing up, the Apollo program was the inspiration for becoming an engineer.

morning-coffee··on Two Dots Too Many (2008)
Not only reminds of "Punctuation Saves Lives!" (Let's eat, kids) but also this: https://www.youtube.com/watch?v=rFeVfwDvTyM
morning-coffee··on How I learned to stop worrying and love userspace networking
Thanks. I read a bit about WireGuard... seems to create a tunnel over UDP as you say. Where I got off track is the following comment in the article:

> Who says you need to do networking in the kernel though?

I thought it implied they were bypassing the kernel entirely. This isn't true at all if it's still using a UDP socket to send... there's still a ton of code in the kernel to handle sending and receiving UDP. It's also a helluva lot less efficient in terms of CPU consumed, unless one is using sendmmsg, because it's a syscall per tiny datagram between user space and kernel space to get the data onto the UDP socket...

morning-coffee··on How I learned to stop worrying and love userspace networking
Didn't really convey where the magic happens to get whatever frames are produced by the userspace TCP/IP stack to whatever mechanism puts those frames on some wire... isn't it still making some syscall? IOW, where's the I/O happening?
morning-coffee··on I've built my first successful side project, and I hate it
> (look, I'm sorry, I also cringe when I write those words)

Just came to say I laughed and really appreciate the honesty in that statement. :)

morning-coffee··on Postmortem of my 9 year journey at Google
But does it still give it all en-masse to the NSA? https://www.aclu.org/news/national-security/five-things-to-k...
morning-coffee··on Project Oak: Meaningful control of data in distributed systems
Rust's compiler can prevent data races, for example. (It forbids mutation in the presence of aliasing, which is the root of it.)
morning-coffee··on What you learn by making a new programming language
The timing of this article is great for me as lately I'm fascinated by the Forth language and the simplicity behind its apparent strangeness. I've been tempted to start playing with similar ideas just for fun.

(https://ratfactor.com/forth/the_programming_language_that_wr... is a great read, btw.)

← PreviousPage 3 of 5Next →