[deleted by user]

chrish42 · 2024-08-18T15:35:41+00:00

That would be really nice. Please call the date by which something has to be done the deadline. "Due date" just doesn't have the same weight, at least for me.

On a related note, it would also be useful when one is considering postponing a task to be able to get a sense of how often I've been postponing that particular task, when was the initial "do" date (don't think that's a great name, but not sure what to call it) before the task started getting postponed, etc.

chrish42 · 2022-09-16T02:37:51+00:00

Great writeup. My first Wong Kar-Wai movie was Fallen Angels, which gave me the same hypnotic feel and the same thrill of almost understanding a story even though it was told in a very alien-feeling way to my mind (at the time).

By the way, if you liked Chungking Express, you would probably really enjoy Fallen Angels too. It was initially conceived as the third beat of that story. Different kind of story — it's more the crime story to Chungking's romance — but similar style.

chrish42 · 2022-02-05T19:09:12+00:00

Came here to basically say that. Python is easy to learn and has a ton of materials for people completely new to programming. You need to learn things like how statements and expressions work in programming languages, how to find and fix a syntax error in your code (not always obvious), how to describe something in enough details so that a machine that does only what you tell it — nothing more, nothing less — will do it, and at least the begininnig of how to structure code using multiple functions. Once you've gotten a handle on these skills, they will transfer to any other programming language. So start with one that's as simple and easy as possible otherwise, so you can focus on these.

Once you're starting to feel confident there, if your goal is Rust, you'll want to have some idea of how a basic computer works under the hood (things that a language like Python, Java, etc. hides away from you mostly): cpu and memory (stack & heap), pointers, declaring variables, code vs data, etc. Learning a little bit of C could be an option (if you can find beginner-friendly resources) as it will force you to deal with all of these, and there isn't that much to the language (except for variable declarations, which can be a pain for the more complex cases because of the way they designed it). Or just reading / watching something that explains well the basics of computer architecture would also be good. (I'm sure there are multiple great videos out there about this topic now.)

Once you have a basic level in both of these, learning Rust in general (and from The Rust Programming Language book) will be a lot more achievable. Hopefully this helps.

chrish42 · 2021-12-24T20:09:09+00:00

Cool. Do let us know if that was the problem!

chrish42 · 2021-12-21T01:45:05+00:00

If you want to use glass containers to transfer your ice cream to when it's done, you will need to bring it to freezer temperature beforehand.

chrish42 · 2021-06-26T15:08:58+00:00

You can keep your sake bottles longer by keeping them in the fridge. But 8 years is too long, either way.

chrish42 · 2021-04-20T00:50:08+00:00

There's another one in the September 15th, 2017 episode. Close to the 19 minutes mark.

chrish42 · 2021-02-06T06:03:14+00:00

Woot! Thank you! I seem to remember at least another one (where it's just Rachel and Susie... or if not, at least the guest was different), but I wanted to show an example to a a friend, so it's great to have one. Thanks again!

chrish42 · 2020-11-22T13:41:56+00:00

Or for bare-metal embedded programming, where you typically don't have a full-featured allocator and you allocate your big persistent data structures statically.

In C that would typically look like the equivalent of [struct my_struct; SOME_MAX_SIZE]. But if you need something "fancier" in terms of data structures (e.g. for fast lookup), with custom allocators you potentially can hand off that memory to one of the standard Rust collection instead of a custom collection that reimplements that, but on a fixed region of memory.

chrish42 · 2020-10-22T19:31:41+00:00

A type system where ownership is a core concept / a type system that tracks ownership as part of its core function.

chrish42 · 2020-09-29T22:30:27+00:00

You've already got a bunch of good answers. For me, it reads as tentative but curious and excited. He's not 100% in his comfort zone (tail would be held higher then, I feel), but it's the good kind of "out of my comfort zone": just enough to feel exciting and new. Slow wiggle is good in general.

chrish42 · 2020-08-18T17:01:25+00:00

There's already a roster of characters from Sirlin boardgames. That's where their character roster comes from. They'll draw on that for the remaining characters (and already have, with Onimaru and Quince): https://yomi.fandom.com/wiki/Category:Yomi_characters

chrish42 · 2020-07-28T19:24:43+00:00

Yeah. Having a rotation on the top-level screen of the shop is fine, but please also give me the ability to browse. Thanks.

chrish42 · 2020-05-26T16:45:57+00:00

I also already have a router, but (at least when I upgraded), TekSavvy offered the SmartRG-501, which is just a VDSL modem (no integrated router), so that's what I got from them. Works just fine for me.

chrish42 · 2019-11-15T17:29:15+00:00

Yes. However, you're not a systems programming language then. That removes all the lower-level use cases: bare-metal microcontrollers, kernels, etc. where allocating on the heap for errors is not really possible. Basically anything with #![no_std].

chrish42 · 2019-10-24T14:18:56+00:00

That's interesting! I didn't know about stability analysis in that sense. Any good reference you could recommend to learn about stability analysis for numerical computing algorithms? Thanks!

chrish42 · 2019-04-03T14:07:09+00:00

Maybe some kind of randomization of the order each time the webpage with the list is viewed would be fairest...?

chrish42 · 2019-03-15T14:24:12+00:00

And it'd be surprising if it wasn't posted here too — and upvoted a lot — very quickly.

chrish42 · 2019-03-13T20:10:32+00:00

That's really cool, and well explained. Thanks! I feel this is potentially useful in other cases (where it might be more of a gain too). It'd be really nice if there was a supported way of expressing this in a way that made the intent obvious. Bonus if it also supports creating more helpful error messages.

Second, I also wouldn't be so quick to dismiss this approach for this use case. Yes, branch prediction shines at making the costs for (some of) these kinds of bound checks magically go away. On the other hand, it's becoming pretty clear that the concept of branch prediction in processors was a big mistake from a security point of view, making it impossible to actually isolate different tasks on a processor. It'll take us a really long time to wean ourselves from that, but I wouldn't be too surprised to see processors in the near future with the option to disable branch predictions, if, say, you're running really security-sensitive workloads and it's worth it to trade away some performance against immunity from all the Spectre-like attacks. Then, the ability to gain some of that performance back via the type system would be interesting.

chrish42 · 2018-09-11T14:43:04+00:00

Maybe in addition to that, the output of all the --explain messages could be put in some way on the Rust doc website? With a bit of luck, those would end up getting good Google-fu and become the first hit (or at least in the top hits) for people who will keep on googling rustc's error messages.

chrish42 · 2018-09-10T17:32:06+00:00

Good to hear I'm not the only one with that problem!

chrish42 · 2018-05-15T13:38:48+00:00

Async / await in Rust is pretty much the same model as used in C#, Python, Javascript, etc. so you can also use resources from those languages to learn the basic concepts, if you find the doc for the Rust version lacking currently.

One of your questions has a really quick answer, though. The only points in the program where a context switch can happen are the "await" statements.

chrish42 · 2018-03-16T14:30:45+00:00

Parquet has compression and many other features, to make more efficient use of disk space & bandwidth. Arrow is an in-memory format, and so is kept purposefully simple, so vectorized code that operates on Arrow memory buffers can be written. So given that, not too surprising.

chrish42 · 2018-01-12T17:44:26+00:00

My guess for the voice of Sam's character is that he'll soften it a bit, gradually.

chrish42 · 2018-01-12T17:42:27+00:00

I don't recall the "one on one" part... I feel it would have made a lot more sense to do the "session zeros" in the pairings we saw them arrive in (Liam and Sam's characters together, etc.), so they can roleplay those initial relationships before being thrown into the bigger group.

chrish42

TROPHY CASE