I don't think i could test static functions with this.

7:43 One correction: the router does not encap the packet with GRE|IP. The Maglev does this when it processes the packet. The IP points to the selected backend. From the paper: "When the Maglev machine receives the packet, it selects an endpoint from the set of service endpoints associated with the VIP, and encapsulates the packet using Generic Routing Encapsulation (GRE) with the outer IP header destined to the endpoint".

If he smacks his lips one more gd time

very nice presentation.

19:18 and this is how webpack screwed up.

I'm quite old, but came late to computing (early 90s). I only ever saw 10Base2, not 10Base5

Nice!

Communist

I understand why the guy is confused about Result's T and E being in the order that they're in, since most other languages do it in the reverse (likely because of Haskell starting it). My question is why the heck they were in the other order to begin with. I THINK it's because it's inspired by or actually derived from the Either type, where "right" sounds more like it should be the primary type than "left", and so it was made the primary side. But you could have named it "first" and "second" or "primary" and "secondary" or something like that and made it so that the first type listed is the primary type. This has bugged me since the first time I saw it, and I was so proud of Rust for doing the obvious thing.

uhm

There's a strawman title. Why couldn't you?

I'm not a programmer but I watch all of Benno Rice, dude knows his stuff and how to keep me engaged.

Thank you! Extremely on the point!

Hello sir this is Kiran I am a person with vision impairment in the sense blind person I am fond of learning web accessibility so please give me a chance to interact and learn the things I know little bit of the Weber celebrity of possible operable understandable and robotic little bit I want to learn

This guy likes avoiding the word checksum.

most people don't really plan a rewrite, they try to do the "new code base from scratch" and thus this new code base is not exposed to all the problems the old code base had been and this is how they recreate the same bugs. Also because when people make rewrites they use the same programming language or some language that lacks the ability to assist the developer in eliminating categories of bugs. so when a rewrite is needed I think it requires an assessment of the original code base, get in touch with the original developers, but having a log/diary of the decisions made would be a good thing to have, that explains the rationale behind the code, but we don't have this because we have these ideologies of "comments are evil, good code don't need comments" and lots of other nonsensical fanaticism about code. I am in favor of literate programming in the sense of writing with each commit the business requirement in plain English. But all this information is tracked separately and dis-jointly from the code base.

my knee jerk reaction to this question is "yes rewrite in rust" because despite my love for C, all the languages that have come after C, and imitating its syntax have been a gigantic pile of trash, C++, Java, PHP, PERL, JavaScript, etc

Very underrated talk.

42:21 this is when i realised it was an austrailia lmaooo

My search is over. This is exactly what I need and want! Yes, (Neo)Vim are the best ;-) The learning curve drastically declined with this talk!

The person on their phone during this lecture hurts my soul

Great video!

It was very engaging to follow through.

I would like to ask you if you can clarify what % of testing should be done using available tools in the market and what % should be tested manually for accessibility? I strongly believe we are not there yet where the entire testing can be relied on available tools. How these available tools and manual testing process should be combined to come up with a full proof accessible digital content?

Fantastic talk, really gives a great history of how interdevice I/O Also, busbars have their origin in eletrical power distribution; there are bars of solid copper that carry high current electricity where an equivalent sized wire(s) would be impractical. They are also used in modular cabinets to allow safe live disconnecting and reconnection to a live bus. The same action as racking in a hard drive or card. The similarity in that action to installing/removing early computer and electrical control systems componets is probably where the bus first got its name.

Great speech and excellent explanations of the topic! Will try some day later 😃

This has been the best task warrior tutorial ever. Explanations are crisp, all examples given do justice to the feature being discussed. This built a memory map of all the tits and bits, and I kept on practicing along. Only 2/3rd of the video was enough to get me started as a regular user. The later part some other time

Good talk! Was actually entertaining.

Thank you for this talk. It may be an unpopular topic in a field with so many cults of personality, but it's an important one.

Any chance you’d have a rainbow table of keys for the metro cards in aus ? I’m trying to crack the transperth cards but I’m not having much luck

Absolutely brilliant. Made so much sense, And so many useful resources. Going to have to watch it again! Thank you

reason ml is hawt!!!

I came across this just now. Great video. How do you access desktop apps or enterprise systems for accesability, please?

Thanks Nick, from India

thanks, a few people is speaking so clearly about automate hardware testing

Does anyone knows where to get the slide of this session ?

Wonderful content. Looking forward for the part 2. Please share the part 2

I think this talk needed to go in earlier discussing move semantics, as otherwise the difference between iterating over Vec<T> vs &Vec<T> is very confusing - the key observation being that IntoIterator *converts* a Vec<T> into an iterator over the T values, such that the original vector is moved out of and no longer available. Most Rust tutorials and books I have seen hand-wave over this stuff in the interests of presenting iteration as super ergonomic, which it is, but I was very confused by this until I worked out what was actually going on

Very useful for my daily work

HTTP 3 and quic is going to be the gold standard.

Thank you!!

Thanks a lot for sharing :) It is surprisingly hard to find this type of content on KZfaq. I mean, I understand that copyright law isn't a developer's first choice of casual content but it is incredibly useful to have a lawyer untangle some of the hearsay that is floating around the internet.

One thing I would have mentioned when covering `.and_then()` at 36:00 is that `and_then()` is just mbind (monadic bind), i.e. the `>>=` operator from Haskell. This becomes pretty obvious when you closely examine its signature, but it was less obvious for me when I first saw it, because of "strange" (but sensible) naming. So you can chain functions-which-may-fail with .and_then()s, the same way you can chain promises in js/ts, or the way `do` construct sugars monad bindings in Haskell.

principles of monitoring emphasizing Nagios as a product that you "should buy" besides the marketing is an interesting presentation.

05:10 is it still true that Google is still cheaper?

Having experience writing unit tests for C I may also add: avoid globals like the plague it is and if you do have globals, make the fixture of the code that uses it reset the entire thing every single unit test. I've had far too often that if the testing order changes, half the unit tests suddenly fail because some unit test was dependent on some other unit test being run first.

I've heard Jess loads of times on the "On The Metal" podcast......... fascinating to see her as a real human being, not just a disembodied voice. :)

9:26 troop ready

This is amazing. Thank you for the talk and posting it

This is amazing. It would be extraordinary to hear more from him about taskwarrior.