blueish

Some people may not see the use case, but the popularity of SNAP has shown that there is a user base for this product. What's interesting to me is Facebook's decision to completely copy the use case in an attempt to capture the market. They've tried to do so with Instagram Stories & DMs, as referenced to by the post, but I'm curious about the rationale to make it a standalone app, which would hurt adoption.

I suppose the idea is the entry point - Instagram's entry point is viewing content, not creating content (the feed is the first thing that shows up when opening the app). Threads is the same as SNAP in that the first entrypoint is to create content: it opens the camera.

It'll be interesting to see if this can succeed in finally pushing SNAP out, as one benefit for users is leveraging the existing social graph from Instagram, whereas you must add people for SNAP.

From my memory, this is meant to be more introductory material for people first learning computer science, rather than a guide for people who are attempting to learn a lisp. My school (UBC) uses Racket and this book as the intro level CS course.

Speaking as someone who's graduating this year, I wasn't exposed to it at all in my undergrad. I might be covered in one or two upper levels, but I hadn't heard of it until taking a graduate course where we talked about verification.

You can remove Pocket from the address bar. All you do is right click it and the only option shows up as "Remove from address bar", so you don't have to stare at the reminder if you don't want to!

I think that'd be an even harder behavior for the ai to come to though, since they'd have to recognize those benefits for the other team and their origin, and then finding that taking Roshan prevents those benefits. I think that's a next step after discovering the benefit of taking Roshan.

I'm surprised they felt confident enough to lift a lot of the restrictions so soon. A lot of them seemed like big game changers I wouldn't expect the ai to be able to exploit so easily. Especially the introduction of Roshan and invisibility, they mention implementing some randomization, it seems like it would take quite a big commitment in terms of resources to take Roshan where the AI wouldn't even realize the benefits immediately (namely the Aegis, the XP and gold they would have to value against the loss from farming/taking towers).

The introduction of the other heroes also comes as a surprise, I wouldn't have expected them to have the ai utilizing new abilities. They don't mentioned how they are picked, other than the ai having a random draft of them (does the ai pick their composition?)

I had a conversation with a friend about this, and the outcome was the idea that BGP could be extended with functionality for this case. There needs to be a way to brand "negative" traffic or routes advertised with some sort of reputation system. In the event of a DDoS attack coming from an AS, you could have intra-AS weight for any given AS such that if an AS reports malicious traffic from a route, it's given a lower weight and traffic is less likely to route to that AS in favor of a less specific prefix. This would encourage any given AS to act in desirable ways, as their actions (or actions coming from within them, e.g. a customer of theirs being the source of a DoS attack) would have consequences.

From my memory, creates an object, gets all the other active nodes in the cluster, moves them to that node and then back to the original node, showcasing the object passing feature of the language.

I recently took a compilers course from Hutchinson, and he talked a bit about the design behind object passing in Emerald from a compilers point of view, how once you have garbage collection, it's easy to implement moving objects between nodes of programs. Interesting concept that I was surprised to find wasn't as commonplace!

I wouldn't call it hand wringing, as I think all the points were valid, but yes, the employee sent out the message he intended to (the real alert over the test alert).

I think the article addressed those points rather well. It highlighted the fact that Glover wasn't the only one doing these things, but his unique position made him a supplier for one of the more exclusive pirating clubs.

The author did a rather good job tying a few story lines together coherently to portray a few of the human interest stories at the heart of the piracy movement. Is the headline and top subject a little grandiose? Sure, but the heart of the article didn't claim that Glover was the only supplier of the pirated records, only that he was the supplier for one of the clubs that typically leaked the records first.