Spyke

Replies

rust

Comment on

How long does it take you guys to complete the book?

I never went through it "end to end". I think it's important to cover the essentials up to ownership, lifetimes, generics, etc, but most of the topics after chapter 10 you can pick and choose as you come across them in real life. The most important is to just start any kind of project and see what questions you come across as you build.

Comment on

x86 reigns supreme as Snapdragon X Elite chips captured just 0.8% of the market with 720,000 units sold in Q3 2024 — Qualcomm misses out on rising AI PC sales with Intel and AMD taking charge

They're still playing catch-up... X Elite is okay but the M4 chips blow it and everything else out of the water. Personally, I don't want an "AI Laptop" or a "CoPilot Laptop"... I don't need even more AI generated slop. I just want what Apple is sellling: a reasonably powerful laptop with crazy good energy efficiency and quality hardware.

neovim

Comment on

New Neovim user (student)

In addition to the others mentioned, I highly recommend trying out AstroNvim! It's got a great set of defaults, based on lazy.nvim, and it's easy to modify and extend.

I also do recommend taking the time to write your own config from scratch... even if you end up scrapping it just to use one of the pre-made configs, it's worth it to learn how vim works. And you'll quickly discover you have a new hobby in life... configuring your text editor.

rust

Comment on

Speeding up the Rust edit-build-run cycle

Reply in thread

This is always one of the first things I setup on a project and teach or encourage my teams to do… I’m always surprised how many devs would rather use print statements all the time (not just in Rust, but especially JS/TS) when it only takes like 5 minutes to configure the debugger. Maybe 10 minutes if you need to search how to open the debugging port in Chrome/FF.

You reached the end