jreck

4 ms·

1.
by jreck 3y ago
Most of that is being driven by the same people who worked on the original APIs. Being on a successful platform means all your rushed, good-enough APIs from years ago tend to now be load bearing regret.
2.
by jreck 8y ago
The stack pointer is just that, a pointer. It points to a region of the heap. It can point anywhere. It's a data structure the assembly knows how to navigate, but it's not some special thing. You can point it anywhere, and change
3.
by jreck 8y ago
> Your statement is equivalent to saying "there's no difference between pointers and integers" - technically, they are both just numbers that live in registers or somewhere in memory. In reality, that approach will not get
4.
by jreck 8y ago
You can also learn that difference in something like C#. You don't need C for that. And C pretends there's a distinction between the stack & heap that doesn't actually exist. There is no significant difference there.
5.
by jreck 8y ago
Except it isn't, not really. Even just the distinction between the stack & heap is wrong. They aren't different things, just different functions called on the otherwise identical memory. It's why things like Go work fine,
6.
by jreck 9y ago
Here, you can have your cake (electron) and eat it too (xi-core) https://github.com/acheronfail/xi-electron
7.
by jreck 9y ago
Depends heavily on the GPU and the scene being rendered. On Android I've seen low-end GPUs bottlenecked by the shader ALU of all things, even though the 2D renderer only produces trivial shaders. Turns out it's easier to whack off
8.
by jreck 9y ago
Quite a few of us run Android Studio on 16GB laptops as well and it works fine there, too. It doesn't seem to be particularly RAM hungry.
9.
by jreck 9y ago
I'm on the Android team and no, we don't. The current spec workstations are 128GB RAM, 1TB SSD, and 2x Xeon E5-2690 v4. But there's still a lot of the older 64GB & 96GB workstations in use as well. The low clock speed of