pjam

Do you happen to remember where this stat came from? I have not heard about it and would be interested in learning more about it

Which part is gone?

There’s a paper about it, linked from the blog post: https://arxiv.org/abs/2306.06391

Yes, but the discussion here was about it being a gradual, gradual type system, as in, the gradual type system being added gradually

Pretty sure your first paragraph was enough, don’t really see the point of bringing up a rape victim example.

I mean, “dutonians” from PagerDuty is enough to illustrate how ridiculous this whole thing is

What are these clear indications (beside the potential draft point)?

I am not qualified to make any comments on the legal difference between the terms either, and I should also add that I am an ESL, so take that with a grain of salt.

Reading the original comments about being "liable", it felt like another way of saying "there are consequences to your decisions, and as the author you bear some responsibility of what you put out there", which imo is pretty far from how the author of this blog post described it, hence me calling "a pretty big stretch"

Ha, perfect, exactly what I was looking for, thanks for pointing it out, didn't realize I was looking at a subsection of the thread, my bad.

But it confirms what I was thinking, going from "liable" to "criminally prosecuted" is a pretty big stretch imo.

Assuming the "criminally prosecuted" piece is a reference to that thread [1], based on what other comments have also pointed out, did anyone in there actually say that, or imply it? I read that thread and didn't see anything close to that, there is clearly harsh language in there, such as:

> Look if you can't understand that this is a thing that will happen in the real world and that people will potentially suffer as a result you shouldn't be writing a crypto library.

Which is still far from suggesting someone should be prosecuted.

[1]:https://lwn.net/Articles/893327/

Feeling required to post about the Building Git[1] book, really love it, for anyone interested in a walkthrough of rebuilding many of the most of important git features, from scratch, in ruby.

[1]: https://shop.jcoglan.com/building-git/

This. Sure, floating point numbers come with a footgun, but the title is so clickbaity, would it really hurt to name it: "What I wish I knew about floating numbers before relying on them?"

> the dynamism of js is disappearing

As an outsider, really curious to hear more about this. Is it from an ecosystem point of view, where the "dynamism is disappearing" or more from a day to day, the fact that writing TS is significantly different than writing JS? Or even something else?

International Entrepreneur Parole

The progressive rehashing described in the article is very similar to what Redis does [1].

Just thought I'd share a example of a use case where the incremental rehashing logic makes sense.

[1]: https://github.com/redis/redis/blob/unstable/src/dict.c

> Long distance running will wear your meniscus out.

Is there any research to back that? Everything I’ve ready says that it is not a fatality and that it is possible to run, for many years (life?) without destroying your joints.

It’s my understanding that your statement is as accurate as saying “driving a car will result in you getting in a car accident”. It’s extremely possible and it has happened to many people but it doesn’t mean it _has_ to happen

This is great and really useful to me! I am also, like others here, in the process of writing my first "book": https://redis.pjam.me/. Mainly inspired by https://shop.jcoglan.com/building-git/, rebuilding Redis, instead of git, in Ruby.

> For my first few sections I wrote the code as I wrote the sections, but then Lak made the suggestion that it would probably be easier to write the code first and then write the chapter

I can echo this a thousand times, I've written the last three chapters this way and this has made a huge difference, wish I had known that earlier!

I will also add that it really made me learn so much because even though I thought I knew quite a bit about Ruby (I knew early on that I didn't know much about Redis). So many times I found myself trying to explain something and realizing that I didn't actually know how it worked and ended up spending hours (days?) researching the inner workings of said thing

PS: Using quotes around book mostly because that's the imposter syndrome kicking in, I was calling it "a series of blog post" for a while, to kinda downplay it

This, 100%. I've been working on a side project that is essentially rebuilding Redis but in Ruby, only to learn how things work (https://redis.pjam.me/) and the Redis code base is fantastic. As someone with basically no professional C experience, the clarity of the code base makes diving in fairly easy

How does Redis "not do data consistency"? Same question for HA? On the HA point, my understanding was that it was one of the reasons to use Redis Labs, because they handle a lot of the setup and management of the infrastructure required to provide a setup that does provide HA.

> most people are using it as a cache

Maybe, I actually have no idea, have you seen numbers?

> Their valuation reflects its use as a cache

How so?

> Did you geo replicate message broker?

No

Redis _can_ be used as a cache, but it's not the only use case.

I've personally mostly used it as a message broker (celery in python, resque in ruby), but it can definitely be used as a database.

Bottom line, it's a very flexible tool, and can be more than "just a cache".

Redis in Ruby is a project I'm currently working on, so far the first three chapters are available.

The idea is to attempt rewriting Redis, in Ruby, to learn more networking, threads, processes, system calls and so on.

I like the idea, but I would be really reluctant to use a gem that has no tests, especially when the core methods are clearly not trivial, a bunch of them are ~100 lines long. Not that the number of lines tells how complicated a method is, but I think it is a good indicator.

I used both for almost a year and while I really enjoyed working with tastypie, I found Django Rest Framework to be even better.

- I think Rest Framework's documentation is way better than tastypie's.

- I found tastypie's source code to be overly complicated, while DRF was a little bit better

- The browsable API is really nice

- I love DRF's API, such a Class Based Views, it felt like the continuation of Django, instead of a complete new thing.

We didn't design the gem to handle "dev" data, the idea was really to handle "real" data, such as Product in our case. Though if you feel like there would be a use case for dev seeds, I would be happy to discuss that with you (either here/twitter/mail etc ...)

Hey, one of the engineers who built this over here, happy to answer any questions you have.