Видео

Good presentation thank you for sharing Rabieh Fashwall +1

I just learned delve and feel the endless stream of print statements that I produced in my life will finally diminish ;-)

FWIW, I've since nuanced my stance on the functional-options pattern. If you're dead set on implementing it, I remain convinced that the tricks I presented in this talk still stand. However, I ended up re-implementing my CORS library with a more traditional config-struct approach, and I'm quite happy with the result; see jub0bs/cors.

Great talk! Easy to follow examples with proper explanation.

Very insightful talk - thank you. 🙏

Really good talk. Thank you Robert

Link to slides: docs.google.com/presentation/d/1rnCYgT41quuSKk-p9o7WOfzI5xoUAgEG4MTlZljjenQ/edit#slide=id.g1e07bf1996f_3_1588

woah thanks for this!

Nice one Agniva! Great presentation!

This is a fantastic talk and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

if Go users are stakeholders, then why there is no donation page like zig does for external users? Does it look unprofessional in an enterprise setting if they asked for donations?

He had me at "I was able to find this really scientific graph on the internet" 🤣 Thanks for a great talk, really enjoyed it.

I can vouch for that, he's very friendly and approachable🙌

Woo!

Making additional layer for database is hard way. You can avoid a lot of problems put repositories near domain entities.

Love it! Can't wait for LanggraphGo 🙂

Great talk, thank you so much!!

Hate to be pedantic but putting a dep in your server is literally global state. Not saying you should t do it btw. Great talk

Putting text in floating boxes does not make it visual language.

Nice talk :)

really cool talk

Really instructive for me, I'll try in my project.

archmage! . love it! :)

This was such a concise and engaging talk. I love discovering talks that aren't thrown around everywhere and this is definitely one of those gems!

Great talk. Thanks for sharing

You ready 2 connect yo nuts to yo brain if u get me. Stop thinking dirty mkkay 😂 🔩🔩

Why was Ken Thompson written out of the history at the beginning of this talk? Otherwise great talk.

This was very informative. Thanks!

One of the best session on OTEL. Thanks a lot. Very detailed 👏

In my opinion, functional options add so much complexity and hurt performance just to make your code more "expressive" and "clear at call-site", that they are not worth using in the majority of cases.

This makes me appreciate slog even more.

I think the unit and integration tests are not comparable, it's like apple vs pear case. Each testing level has own advantages and disadvantages. Unit test is good, when you write new unit or new code for a unit, and you need a quick feedback. This can work even if the feature is not implemented fully since it's about testing the unit. In addition, from security perspective unit tests can test the "impossible" paths within the code. And yes, the unit tests are relatively simple compared to the higher levels of testing. Integration is good, when you want test the feature itself. So, units can work together to serve in a proper way. Testing deeply the feature most probably will require more complex code. Both of them are important and they cannot replace each other. I also think based on my experience in SW development that for a good product at least two different levels of testing are needed.

Great talk! Learned so much :)

The example for “structs not being expressive enough” (~7:00) artificially limits itself. They are easily expressive enough if you relax the arbitrary imposed constraints of requiring the value of MaxAge to be the only thing affecting the actual MaxAge header by adding an additional property that controls the caching part and determines whether to include a zero MaxAge or omit it.

Great talk, and great delivery! I particularly enjoyed the explanation of the singleflight package (starting at 10:40).

The purists must be furious when she says golang instead of go 😂

I _knew_ that this guy was a man... based just on his website. What's up with the weird furry chat avatars, multiple personality disorder larp?

Nice presentation, context canceling in errgrouops is what I definitely would use

Excellent talk. I've been using this pattern for a while, and you've given me a few new ideas to add to my toolset!

That was a brilliant talk (not too deep and not too shallow) and with go examples, thank you!

Great Talk.

That’s a roll, not loop, Ron 🤦‍♂️😂 Great energetic talk!

Very interesting talk Maciej, great work here and there! 😉

Conferences that post videos without the questions are lame.

Webassembly is here to stay. 🙋‍♂8:08 𝗗𝗶𝗱 𝗮𝗻𝘆𝗼𝗻𝗲 𝗻𝗼𝘁𝗶𝗰𝗲 𝘄𝗵𝗮𝘁'𝘀 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝗶𝗻 𝘁𝗵𝗲 𝗨𝗻𝗶𝘅 𝗽𝗶𝗽𝗲 𝘀𝘆𝘀𝘁𝗲𝗺? That's right, 𝚜𝚝𝚍𝚞𝚒 for user interactions. Neither stdout nor stderr is suitable for interacting with the end-user during an interactive session (print a question and read the answer, etc). If you are using stdout instead of stdui then the output can't be piped, same with stderr.

This was so much fun to watch! Thanks for sharing it!

There's a reason file operations are reminiscent of tapes........

I always enjoyed your blog and I'm positively surprised by how enjoyable this presentation is

*Summary* *Introduction* - Speaker: Xe Iaso - Topic: Integrating WebAssembly with Unix Philosophy - Goal: To simplify programming by compiling third-party libraries to WebAssembly. *Unix Philosophy* - Core principle: "Everything is a file." - File handles in Unix are arbitrary integers, indices in an array in kernel memory. - Basic model: Open, Close, Read, Write, Seek - Network sockets and processes are also treated as files. *WebAssembly (Wasm)* - A compiler target for an imaginary CPU. - Intended to be a level below JavaScript. - Initially lacks capabilities like file systems or internet connectivity. *WebAssembly System Interface (WASI)* - Provides semantics for IO, files, file systems, and basic network operations. - Makes WebAssembly more like an OS. - Allows for cross-platform compatibility. *Crabto Espionage Technique* - Embedding Rust programs into Go programs using WebAssembly. - Uses the Go library Wazero for WebAssembly VM and WASI hooks. - Allows for the use of C libraries without needing a C compiler. *Practical Example* - Markdown parser written in Rust, compiled to WebAssembly, and embedded in a Go program. - Demonstrated a live demo involving an echo server and client. *Advantages* - No need for multiple compilers or cross-compiling. - Isolation and security through WebAssembly. - Enables plugin architectures. *Conclusion* - By understanding and leveraging the Unix philosophy, one can simplify and extend programming paradigms. - Encourages the audience to think about how they can apply these ideas in their own projects.

🤚I even possessed and used QIC tapes in a Wangtec QIC drive for backup; even restore.