rfl890

>Windows 8 and above also have their own asynchronous DNS API on NON-POSIX land. Interesting. Which API?

What is the point of making hardware synths on a Pi when you could just make a VST?

Site's HTTP-only. Shows a warning in Firefox

The optimal path to mathematical mastery is "Error establishing a database connection"?

I don't know of any network latency <=1ms over the public internet, so 10ms overhead might be 2x at best.

Relax, dude. https://xkcd.com/386/

Why isn't DoT sufficient?

What?

Think "therein lies the rub"

So I can run a full powered PCIe 4.0 16x GPU on 1 PCIe 8.0 lane???

For 300 years, they were running around too fucking hammered to invent anything!

The random Polish in the middle got me

Snatch (2000) isn't on it? Blasphemous.

You could also set up a wg server, have both clients connect to it and then pass data between the two IPs. There's still a central relay passing data around, NAT or no NAT.

Isn't this a WAN and not LAN?

Windows has kept FILE opaque for as long as I can remember. Granted, that's not very long, only 10 or so years.

Looks like a parody of this website: https://motherfuckingwebsite.com/

Felix Cloutier's page has always been my go-to

If you want to learn more about this Lumina probiotic stuff, read this article: https://www.mcgill.ca/oss/article/medical-critical-thinking-...

That's the caveat, the contract you sign when you start an open source project. You have to have the mindset of simply not giving a fuck about who does what with your code and how much they make from it. Then you can be at peace. If you don't want to (or can't) adopt that mindset for a particular project or at all, that's completely fine and normal. OSS is not for you. As soon as you want compensation for your work, things start to go south. See the whole core-js situation and what went down for an example.

Well, if you're writing open source because you want to write open source, then none of this matters. If you are worried about corporations stealing your work, that should drive you away from OSS. OSS should stay "hobbyist" for the individual developer.

Nevermind, I was confused.

This was published after TFA, how is it the original?

YMMV. I rocked a flip phone (ZTE Cymbal) for 5 years and only just recently learnt it was called T9, in modern days I don't think it's such a common term.

the library is named libt9, I believe the author is aware of this...

Just wondering, why did you make an entire container image instead of trying to compile it from source first?

Thank you for your response. I don't feel that you unnecessarily exposed anything, just that not much explanation was given. Take a look at The Rust Programming Language's "getting started" section[1]. The installation steps are clear, the code is deconstructed and explained, and you are made familiar with the basic CLI tooling. Looking at yours, installation steps are clear, but I'm just given commands and code to paste with no explanation as to what it all does. Sure, I could go browse the man pages, but it's easier to ease into reading manual pages after a gentle beginner's explanation.

Although, given that you mentioned teaching, maybe the page is intended to be presentation-style (less information on the page, more to be explained vocally)? But you can correct me if I'm wrong.

[1] https://doc.rust-lang.org/book/ch01-00-getting-started.html

I'm very confused at first glance. What are "coder scripts"? Why is "std" repeated 3 times in "dk StdStd_Std.Run"? What on earth is "Tr1Stdlib_V414Io"? The entire tool comes off as arbitrary and confusing, at least to me. I would really quite appreciate a brief primer on the language and its design decisions, architecture and syntax. So far, I'm just having assorted bits of information thrown at me with no real structure.

(Note: I have never touched OCaml. Is this some weird OCaml thing?)

Switching to desktop mode fixed it for me

Check OP's about. They are the author.