Відео

Don’t waste your time watching this! I seldom am this harsh. There is minimal value in the information covered. At best, it is a time waste with a shill for CoPilot at the end. There are errors in it. The worst is that defer is scope by a code block where it is actually scoped at the function level. He absolutely states to not use global variables and subsequently states to reuse variables to minimize allocations without realizing that these two statements have conflicts in cases. Furthermore, he never references sync.Pool as an alternative means. There much better content available. much better

I dont understand people that waste the whole screen and put the content in a tiny box in the middle that's unreadable. we don't fancy syntax higlighter we just need to see the plain code.

Instead of watching this look for even freeman's 2018 presentation.

Sadly but "Golang manages memory with with memory management mechanisms, go and learn them somewhere else" is all you will get from this video

great talk.

well it's really really high level stuff. Almost a quote from the talk: "Wonderful GC would come and clean all your memory for you, don't worry!"

I thought this talk will go deep dive into GC. This video only touches the high level concepts.

great video with a clean and clear explanation of LSPs. Shame about the volume, but I was able to crank it up to 11 and squint (squinting helps you hear)

Gemini: This video is about the Language Server Protocol (LSP) which is a protocol that defines communication between a text editor and a programming language. The speaker, Adrian Hesketh, goes over the details of the protocol and how to implement it to build a language server. Here are the key points covered in the video: What is LSP: LSP defines the communication protocol between a text editor and a programming language. It enables features like autocompletion, goto definition, jump to diagnostics, and formatting. Messages: Communication between the client (text editor) and server (language server) happens through messages. These messages are formatted according to the JSON RPC specification and include headers, content length, and the message body. Requests and Responses: The client can send requests to the server to get information or perform actions. The server responds back with a response message. Notifications: The server can send notifications to the client to inform about changes or errors. For example, the server might send a notification to the client about diagnostics errors found in the code. Initialization: When the client and server start communication, they go through an initialization handshake. During the handshake, the client informs the server about what capabilities it has and the server informs the client about its capabilities. Building a language server: The speaker walks through the steps involved in building a language server. This includes handling requests and responses, handling notifications, and building parsers to understand the structure of the code. Libraries and tools: The speaker also mentions some libraries and tools that can be helpful when building a language server. These include libraries for parsing code, implementing the LSP protocol, and building language extensions for editors.

08:00 isn't a leak/bug. thats the end of the program, the memory is about to be automatically de-allocated.

white theme vscode surprisingly looks really comfortable

Where can we download the presentation slides?

Nice talk though I am much more interested in your `templ` package than Go LSP. (I appreciate the segue of extending the Go LSP for templ. :) BTW Just a small thing near the start: the mention of `ls` is confusing (more so for Windows Gophers :). `ls` does not use stdin, but *does* write to stdout. Though I guess when you type `ls` it is going to stdin of the shell you are using.

fish_head.000004 0:19

Incredible you covered so much so clearly in an hour. Thank you

This is the stuff I'm here for. Very good talk.

As a first timer well delivered... Keep it up.

Please, next time increase the font size of the slides to use all available space!

Great talk. Production fail. 😌

The talk is probably good; if you could actually read the slides. Who thought slapping wide bars of static content was a good idea?

👉 TEMPL @40:43

This is interesting material. I'm surprised at the incredible waste of space on the screen, in the lower right and upper left, that result in most of the important text being unreadable. I would like to see 50 minutes of the material, and I would be fine with 1 minute of the Gophercon UK /jetbrains ad in the top left, and the author's name and picture in the lower right. But I doubt you need 50m of that static content, especially when it makes the actual presentation almost unreadable 😞

Super cool 🎉

Fresh From THE Oven

Great talk, shame that the audio is so low.

Hmm I actually hoped for some GC internals in Go; this presentation gives a high level overview and only touches multiple topics.

Thank you 🙏🏻 🌹

Thank you 🙏🏻

presentation is not readable (

Great talk! Thanks!

I couldn't deduce it from the presentation or read it quickly from the source code. Can I apply a group containing a group?

Please fix the sound 🙏

Nice talk! I learned somethings.... Thanks! :)

like everyone said. the audio needs addressing.

Improve sound please

Also SPEAK LOUDER, I can barely understand anything

I just want to know how I can integrate templ with Jetbrains products. The video doesn't have sections

Grains was mentioned. 😅 Awesome project.

You're not supposed to LOL when whatching alone, yet I did ... a lot. 👏 Might actually use this when stuck with low hopes.

A fabulous, fabulous talk. I'll be rewatching this and experimenting with the examples.

Nice talk. But the audio is so low without headsets

Great one Sayani! Loved it.

😍😍😍 Super proud of you Sayani!

জুই জুই 🔥🔥🔥

Great talk Sayani 👏

Arnav sent me here to drop a comment :)

No audio😥

I have received a comment in other place about the talk and about the accuracy of the content, so I want to expose it here. This talk was prepare for 1.19 and then migrated to 1.20. During that process I miss the fact that the IR generation is no longer done through irgen by default, the default has changed to unified IR in 1.20. That is an interesting detail to take into account, but in my opinion the value of the talk is the general overview of the go compiler itself. But if anybody was specially interested on the IR generation, my talk can be misleading in that point.

Amazing talk!

Definetly one of the highlights, great talk!