AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Hotel dusk room 215 electrical room11/20/2023 ![]() ![]() This can lead to surprising results like the battery lasting twice as long and with that giving new life to a tired old device. This is what I did on those few devices which I've used on the stock distribution - remove as much bloat as possible, remove all social media cruft, etc. Once you're over the first hurdle - unlocking - it should be easy enough.Īs an alternative you could root the device and disable (or remove) the bloat in the stock distribution, this often goes a long way towards getting a more usable device. Installing a distribution is no harder than installing Debian, keeping it up to date is easy as it supports OTA updates. If it is you'll need to unlock it which - again depending on the device - can be as easy as flipping a switch or as hard as trying to get some code from a vendor which doesn't really want to give that code or which might not even exist any more. I'm no computer scientist, just a developer.Īs to whether installing an AOSP-derived Android distribution is easy to install or not mostly depends on whether the device is locked in some way or other. I'm rambling a bit and speaking from memory here btw, take this comment with a grain of salt. Later on (with Swift) they managed to add an optimization that could omit this check if they detected the target could not change. But at the same time, I want to believe Interface Builder would be converted to obj-c code and compiled as normal.Īnyway Apple had years of head start in terms of performance and user experience (= perceived speed) to Android, their technology decisions was one of the reasons.Īnd yet, thinking about it, it wasn't even as fast as I could be because of how objective-C works, function calls are somewhat dynamic so every function call, the runtime has to look up what to call the function on. I want to believe I can imagine that the IB interface was just an XML file that had to be read, parsed and its layout built up, whereas handcoded layouts is very dumb code that would compile easily and execute quickly. One thing my colleague (who was a bit more hardcore than me) was convinced of is that hand-coding interface code was faster than using Interface Builder. I also believe Apple itself added more and more cruft to the system. But over time, on the one side the developers started adding more and more features, or switched to web tech or some hybrid technology, convinced that it would save them time and money (it didn't and the user experience is the worse for it). Not everything at least early on, iOS apps were great. can you tell it was from the team that made the PPU, rather than a modern GPU or even an SGI-derived one?), but that one is my favorite.Įdit: minor correction, the N64 supported AA, which is another reason jagged polygons are less common. There's some other fun facts about the DS (its 3D hardware is scan line based, not frame buffer based! Which means you can't do post processing on it without some hacky tricks. Extra fun when some official soundtrack releases contain the buzz :) Line rips recorded from the audio jack of the device don't have this distinctive buzz. Community tooling later allowed you to batch convert them to MP3, and the rest is history. Yes, it turns out that the people that designed the "2sf" format used for unofficial music rips simply used stripped down ROMs and code extracted from a version of DeSMuMe. Fun fact! The Nintendo DS audio chip has a distinctive buzz that's visible in all audio tips uploaded to YouTube, and you can even hear it on this page! It comes from. ![]()
0 Comments
Read More
Leave a Reply. |