nbomb, 8 months ago

@eniko wait till you find out about copy/paste!

kspaziani, 8 months ago

@eniko it was a feature. Had to serialize on closing the app. I miss the old days

eniko, 8 months ago

@kspaziani oh? >_> how was not having multitasking better?

kspaziani, 8 months ago

@eniko making the most of limited ram i think was the biggest thing.

vfig, 8 months ago

@eniko it had os-level multitasking of course, but yeah, end-user apps were "you can run one at a time".

main motivator for that decision was probably just that the phones had pretty small ram and no paging to disk.

Atridas, 8 months ago

@eniko iirc old Android also had pretty serious limitations (laughs in 1.6)

eniko, 8 months ago

@Atridas oh? care to elaborate?

Atridas, 8 months ago

@eniko I don't really remember other than developing for anything older than 4.0 was really painful. Luckily the place I was working on pivoted to video games 😅

alice, 8 months ago

@eniko @Atridas Here’s one you’ll appreciate. It took Android forever to use hardware graphics composition. It was all CPU-bound for the longest time. CoreGraphics inherited from Mac OS X, OpenGL-optimised, allowed for much faster rendering and smoother scrolling. (E.g. momentum scrolling.)

eniko, 8 months ago

@alice @Atridas wait do you mean they used software rendering for opengl or am I misunderstanding

alice, 8 months ago

@eniko @Atridas Software layer composition/masked blitting. Made the animations terribly choppy. Like running OS X using pure EFI graphics fallback.

TTimo, 8 months ago

@eniko wait till you learn it only allowed web apps initially :)