nox101

Awesome! I hope you'll post some write up or something on how you did it!

I really wish they'd repurpose public libraries for this.

It only takes one student to lose an arm, face, life and their parents will sue the school into oblivion and start PAPT (parents against power tools) or something "for the kids!"

I'm on your side that I'd rather see the tools at the school. At the same time, I took an auto-shop class in high school and the majority of students in the class were dipshits and were lucky not to get more hurt. The teacher managed to stop them just in time from trying to turn over an engine on a rack that would have crushed them if the teach had been 5 second later.

MUJI used to have lots of that (20-25yrs ago). Shelves made from cardboard tubes, etc... You could tell, one bump and it would be destroyed. I think they got rid of most of them.

> #1 Understand the system: Read the manual, read everything in depth, know the fundamentals, know the road map, understand your tools, and look up the details.

Maybe I'm mis-understand but "Read the manual, read everything in depth" sounds like. Oh, I have bug in my code, first read the entire manual of the library I'm using, all 700 pages, then read 7 books on the library details, now that a month or two has passed, go look at the bug.

I'd be curious if there's a single programmer that follows this advice.

Mario has "slot machines" in, even today

I've been on the internet as long as you and from my POV it changed a ton. The biggest changes to me are

(1) social media via smartphones - letting everyone trivially post to everyone else on the planet.

This use to be nerd activity (blogs) and the audience was other nerds. First social media sites, then the smart phone completely changed this.

(2) follows from 1, influencer culture, by which I mean, Instagram, TikTok, X, Youtube all incentivize people performing to try to get as many viewers/followers as possible. Thinking back to the 70s/80s, even the top movie stars just got some fan mail. They didn't have 400-600 MILLION FOLLOWERS to whom they could say anything they wanted. A celebrity had a most a TV show with a crew and editors and a strong chance of getting fired/banned if they got to crazy. Now, any high school kid can have 100+ million followers

It's not just people with followers, 20% of my youtube feed is people trying desperately to have something to talk about. Some news happens, thousands of people "report it" on their "channel". The scale of it is insane to me.

> Easy way to use libraries

This is both a blessing and a curse. Seeing the rust docs require 561 crates makes it clear that rust/cargo is headed down the same path as node/npm

     Downloaded 561 crates (50.7 MB) in 5.21s (largest was `libsqlite3-sys` at 5.1 MB)

I agree there hasn't been a super strong reason to upgrade in the last 10 years. I just disagree with "I will never need to buy a new computer again".

I suspect at some point the new "Youtube" (3d volumetric video, holodeck, or something) will come out, it will be as popular as youtube and as "must have feature" such that 95% of the population will want a computer that can do this new thing and todays computers won't be able to do that new thing.

"640k is all you need!"

There is always new tech. Local LLMs and other high processing intensive things might be a thing people want. Not directly, but it may enable things they want. More viral TikTok videos. Maybe some kind of health monitoring. Maybe AR will finally get a compelling use case if it can identify everything in your field of view but it requires serious computing power. Maybe AR 3D movies where the characters show up in your house and adapt to your living room. Siri might suck, but lots of people want a "Star Trek" computer that actually understands them.

The point is not any specific example. Rather, it's that there's always something around the corner that needs more computing power. I have no idea what it will be, but I'm confident something will appear.

Sounds like COM/DCOM from ~1995. Every API had a public interface including a description. You could open the DCOM Inspector, browse all the APIs, and see the type signature of every function and its docs.