• 0 Posts
  • 227 Comments
Joined 3 years ago
cake
Cake day: August 2nd, 2023

help-circle




  • I’ve been lurking in various watch-related forums right before this release, and all the drama leading up to this has been hilarious:

    FYI: this “watch” is a collab between a brand (swatch) that makes <$100 disposable watches (the watch movement is sealed such that you can’t repair/maintain it) and a brand (AP) that makes $30k watches with a long waiting list. The collab was announced first, then the specs of the watch, then the actual watch itself (being on a keychain?). Each round of announcements led to a new wave of drama.

    1. There are people mad that this collab devalues their $30k watch brand
    2. There are people mad that the watch is an exact plastic replica of their $30k AP Royal Oak
    3. There are people mad that the collab watch doesn’t come on a strap, but is instead a glorified keychain
    4. There are people mad that said keychain comes at a price of $400, is plastic, and cannot be maintained (mechanical watches need regular maintenance, this plastic piece is destined for the trash in 4-5 years)
    5. There are people mad about the colors
    6. There are people mad that said colors devalue their $30k watch
    7. There are scalpers selling the watch on eBay before the watch was released for $3k
    8. There are strap makers making 3D printed straps for the thing as soon as the watch was announced, at the price point of the watch itself ($400)
    9. The release event almost entirely consisted of scalpers. Every reasonable watch person thinks it’s overpriced garbage
    10. This is NOT a limited release watch. These plastic watches will fill the oceans for years to come
    11. Swatch had to close stores due to public safety issues with these scalpers
    12. There are scalpers that stole a “sorry were closed today” paper sign from a swatch store and selling it on eBay

    The best part: nobody is actually interested in the watch. It’s almost all scalpers and people owning a $30k watch having a meltdown.

    Edit: if you are looking for a <$400 mechanical watch that is worth the money, I recommend the Seiko 5 or Orient Bambino instead of this plastic toy. Learn to regulate and maintain it by yourself, it’s easier than it looks. My Max Bill runs at a rate of +0.5s per day after regulation. Watching a fully mechanical minute hand sweep (as well as the date flicking over instantly at midnight) is such a joy.


  • This is practically impossible. We have proverbially locked the keys in the room. IP/UDP/TCP are here to stay due to the prevalence of buggy/nonstandard middleboxes (hardware firewalls, ASIC switches, NAT routers) in the Internet.

    We have new protocols, new theories for networking (look at NDN, in which is physically incapable of being censored or ddosed). However, anything that doesn’t conform to existing IP/TCP/UDP will get dropped by these so-called “middleboxes”. Even things that DO conform to IP/TCP/UDP will sometimes get dropped by these middleboxes (e.g. new TCP extensions, QUIC, etc). We cannot build an Internet replacement without almost fully scrapping every piece of networking equipment deployed since the 90s.

    Middleboxes were supposed to be a temporary solution until we could transition to a new protocol like IPv6. Companies went for the cheap solution and violated the end-to-end principle of networking instead. Now we’re paying the price and stuck with it.



  • Because the goal is to get people to learn/think about something. We don’t care what you use as long as you retain knowledge taught in the course. If what helps you learn is LLMs, then go for it.

    Problem right now is there is a significant amount of people that are using these tools to do the thinking for them. And this is when Office Hours, Homework feedback, Email (I guarantee all students emails are responded to within 24hrs. Most are handled within 30 minutes) are all available and paid for (by tuition). I am even happy to schedule one-on-ones if privacy is a concern, but none of this is being utilized.



  • We are allowing LLMs for all of our homeworks. As long as you can solve the problems in the indicated way with a reasonable answer.

    In case you are not sure about the “indicated way”, there are practice questions with detailed step-by-step solutions for each hw problem that you just have to change the numbers/equations a bit and you’ll get points.

    What we’ve noticed is that the year-after-year averages are significantly higher, especially this year. However, students are bringing in details that we explicitly didn’t go over in lecture and putting that on the homework (e.g. Delayed branching in Computer Architecture, because it’s a random quirk of MIPS that even assembly programmers don’t have to deal with). None of these details are ever mentioned in lecture or the practice homeworks (in a few cases, they are mentioned with the explicit wording “do not worry about this now”)

    We can only assume people are copying the homework into LLMs and copying the results straight down. The latest exam had a question where students were asked to analyze a specific chunk of assembly code to deduce certain properties about it. Approximately 20-30% of the students didn’t know the FORMAT to answer it, despite it literally being item 1 on last week’s homework.

    And when I say format, I don’t mean exactly “you must write these exact words or you lose points”. It’s literally just point out “line A and B have this property X because of attribute Y”. Just including ABXY as shown in the practice homework is enough. But apparently people are too lazy to read a 10 bullet point answer…









    1. All NICs already work off of DMA to access/copy packets into/from memory. Yes, even your $10 ones. So “would need DMA to stand a chance” doesn’t have any technical meaning other than putting a bunch of words together.

    2. The bottleneck for TCP is sequence number processing, which must be done on a single core (for each flow) and cannot be parallelized. You also cannot offload sequence number processing without making major sacrifices that result in corrupted data in several edge cases (see TCP chimney offload, which cannot handle the required TCP extensions needed to run TCP at 1Gbps). So no, “more offloading” is easy to say but not feasible.

    3. Who needs it: data centers trying to scale legacy software, or dealing with multi region data replication (rocev2 is terrible for long distance links). But no, no home user would need it