Live data from Hacker News

Ask HN: Going low-level – what to learn next?

news.ycombinator.com

51–59 of 59 posts

Re: Ask HN: Going low-level – what to learn next?

#54
I'm surprised nobody has mentioned mobile yet. While native mobile works through the Android/iOS API, it's often quite close to the minimum abstraction level.

Here's a doc you can dig around with https://source.android.com/docs/core

You get a high level overview, then it explains how everything connects right down to the hardware. It's open source too, so you can go in there and poke around.

If you want something that can make money, I'd say look at camera and Bluetooth, because these are the things that need the most customization. Neural network API could see a lot of use in the future too.

But there's plenty of fascinating stuff, like how it renders fonts, how it handles hearing aids, and so on.

Edit: TIL Android has a category of 'rich haptics', where it gives tiny haptic feedback when you swipe your finger across a surface or to the beat of music. Very few app devs know this, so it's not integrates well into apps.

Re: Ask HN: Going low-level – what to learn next?

#55

Join the Handmade Network [0]. Much can be learned by hanging out with the right kind of competent/enthusiastic crowd. And if you allow the plug, I run the conferences [1]. [0] https://handmade.network [1] https://handmadecities.com

This is one of the coolest things ever.

Re: Ask HN: Going low-level – what to learn next?

#56
post #38

Earlier quoted context omitted.

Yes: +1, this. Learning Lua is a great way to get introduced to a lot of low-level concepts, from bytecode to VM's to language design and beyond.

Ironically, I've been avoiding learning Lua for quite some time for some reason. I guess it's finally time to give it a try!

Lua is one of the most amazing bits of programming tech you can use... I have done all sorts of crazy things with it, from applications-with-databases to realtime scientific analysis, games engines and games ahoy, simple automation tooling for devops, and more. I recently decided to sit down and organize a few hundred directories, each with more than 20,000+ files in them, and I've now built a system that my colleagues are asking about installing for themselves..

Its just such a great tool, please don't deny yourself this wonderful experience. Get the VM, put it in something - or find a VM somewhere in something already, and have a lot of fun. And don't forget to make sure you know what a sparse array is, and why pairs() and why ipairs() .. you'll be glad you did!

PS - don't fall for the hype, you can do someTable[0] = "first", someTable[1] = "second" all you like .. :)

Re: Ask HN: Going low-level – what to learn next?

#58

Low-level means different things to different people: 1. The best source of low-level information on things like operating systems (writing your own) etc is https://wiki.osdev.org/Expanded_Main_Page 2. Compiler related low-level should include a read through Crafting Interpreters ( https://craftinginterpreters.com/ ), even if all you're going to do is create compiled languages. 3. Hardware type low-level (where you b…

> with just as much low-level hooks as you might need

eBPF is great for some things and is "easier" for some things but kernel modules are able to do _way_ more by design.

Post reply on HN