back-to-webos.html 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  2. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  4. <head>
  5. <title>Back to WebOS - Kevin "The Nuclear" Bloom's Personal Website</title>
  6. <link rel="shortcut icon" type="image/png" href="/img/guy-in-space.png"/>
  7. <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
  8. <meta name="generator" content="Org mode" />
  9. <meta name="author" content="Kevin &quot;The Nuclear&quot; Bloom" />
  10. <meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, pre-check=0" />
  11. <meta http-equiv="cache-control" content="max-age=0" />
  12. <meta http-equiv="expires" content="0" />
  13. <meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
  14. <meta http-equiv="pragma" content="no-cache" />
  15. <link rel='stylesheet' href='/styles/main.2.css' />
  16. </head>
  17. <body>
  18. <div id="preamble" class="status">
  19. <div id="banner">
  20. <h1><a href="/home.html">Kevin "The Nuclear" Bloom</a></h1>
  21. <hr />
  22. <div id="navit">
  23. <a href="/contact.html">Contact</a>
  24. &nbsp;
  25. <a href="/blog.html">Blog</a>
  26. &nbsp;
  27. <a href="/projects.html">Projects</a>
  28. &nbsp;
  29. <a href="/about-me.html">About Me</a>
  30. </div>
  31. </div>
  32. </div>
  33. <div id="content">
  34. <div id="outline-container-org72e428f" class="outline-2">
  35. <h2 id="org72e428f">Back To WebOS</h2>
  36. <div class="outline-text-2" id="text-org72e428f">
  37. <div class="PREVIEW">
  38. <p>
  39. Recently my iPhone SE has been having some problems - <i>big problems</i>. The phone
  40. itself runs fine and has no issues handling iOS in general or any apps I wish to
  41. run. It's practically still brand new in that sense. However, somewhere within
  42. the power/lock circuity there seems to be a malfunction causing the screen to
  43. lock and unlock at random. Although very annoying, it was still usable for few
  44. months.
  45. </p>
  46. <p>
  47. Enter the curse of 2018! The is practically useless now. It locks/unlocks so
  48. much that I can't even accept a phone call. Due to this tragedy, I was forced to
  49. find another cellular device.
  50. </p>
  51. <p>
  52. <a href="https://www.replicant.us/">Replicant</a> was my first choice. I plugged in my SIM card and &#x2026; nothing
  53. happened. Turns out either Replicant 6 has a bug or the phone's SIM reader is
  54. broken. Either way, I had to ditch the idea because I didn't to get a working
  55. phone quickly.
  56. </p>
  57. <p>
  58. Then it hit me&#x2026; Palm/HP Pre 3!
  59. </p>
  60. </div>
  61. <p>
  62. Back in 2013, I purchased a "rare" <a href="https://en.wikipedia.org/wiki/HP_Pre_3">Palm/HP Pre 3</a> just for hacking around with. I
  63. had used the phone before and installed some custom things on it to bypass the
  64. "first time using" screens. I didn't really do too much with the device since
  65. then, however.
  66. </p>
  67. <p>
  68. I knew that there was a hidden underground community of legacy webOS hackers
  69. that kept the OS alive, so I knew that they would be able to guide me into using
  70. it in modern times.
  71. </p>
  72. <p>
  73. So I hopped onto the <a href="https://www.webosnation.com/">webOS forums</a> and started searching.
  74. </p>
  75. <p>
  76. I found a ton of information about what apps to get, what patches are helpful,
  77. and what I need to do to get the device working. Things like SSL certifications
  78. are really important. If you want to sync up email, calendar, and contacts, you
  79. need to get those figured out! Luckily, the community was excellent at laying
  80. out the foundation for this stuff.
  81. </p>
  82. <p>
  83. Once I got that stuff all installed - it didn't work. Literally. I flat out had
  84. the same problems as before. Old certs! I don't know what was wrong.
  85. </p>
  86. <p>
  87. It took me nearly a week to get it all sorted. For some reason, once I installed
  88. the OAuth2 patch everything started working! The floodgates were opened! I
  89. synced my emails, my calendars, and my contacts! It was great. Now I'm using
  90. webOS on my Palm/HP Pre 3 full time.
  91. </p>
  92. <hr />
  93. <p>
  94. People keep asking me: "Are you gonna buy a new iPhone?" My response is usually
  95. something like this: "Yes, but not until around September because I heard rumors
  96. that they [Apple] plan on making a new SE model. I like the smaller size." This
  97. is mostly true! I do plan on using this device until then, <b>if</b> they make a new
  98. SE model. Otherwise, we'll see.
  99. </p>
  100. <p>
  101. There is something else that I've been keeping on my radar too. A company called
  102. TCL<sup><a id="fnr.1" class="footref" href="#fn.1">1</a></sup> that bought the Palm name. They've been teasing us with hints that
  103. they plan to make phones in a palm-like manner. If they do make a phone like
  104. that, I might be very tempted to switch to that. It will probably be an Android
  105. phone by default, which makes sense. However, the rest of the webOS community
  106. and myself don't want to run Android! We want webOS! We hope that us bothering
  107. them will convince them to free<sup><a id="fnr.2" class="footref" href="#fn.2">2</a></sup> the device - allowing us to install
  108. <a href="https://en.wikipedia.org/wiki/LuneOS">LuneOS</a>, a cousin of webOS.
  109. </p>
  110. <p>
  111. Another question I get asked a lot is: "What's so great about webOS?" My answer
  112. for this could be a book trilogy, if I wanted, but I'll keep it short for now.
  113. </p>
  114. <p>
  115. WebOS shipped with a ton of very unique concepts that shaped the way smartphones
  116. work nowadays. Most notably is the <i>card view</i>. This was a brilliant way to
  117. multitask on a touch device - allowing the user to just swipe in either
  118. direction to go to the next app. This originally came out in 2009 and just
  119. recently have seen this concept come up in iOS and Android. However, their
  120. versions of this concept suck compared to webOS<sup><a id="fnr.3" class="footref" href="#fn.3">3</a></sup>.
  121. </p>
  122. <p>
  123. Another great feature was <i>gestures</i>. These were swiping motions that you'd
  124. preform on the <i>gesture area</i> on the device. The gesture area was location under
  125. the screen and above the keyboard on Pre devices, the pixi, and the veer. There
  126. was a really line that would illuminate here as well. Using gestures to swipe
  127. into the next app, or go back, or view the card view was extremely
  128. productive. In fact, once you get used to them you never wanna go back to the
  129. boring-ness of iOS or Android navigation.
  130. </p>
  131. <p>
  132. iOS did learn about gestures from webOS though. They added in the
  133. swipe-to-go-back feature, although it is nothing compared to webOS.
  134. </p>
  135. <p>
  136. <i>Just Type</i> is another amazing feature from webOS that we see in modern mobile
  137. OS's now. iOS has spotlight<sup><a id="fnr.4" class="footref" href="#fn.4">4</a></sup> which does pretty much the same thing as just
  138. type. However, who actually uses spotlight? I know that the only time I use
  139. spotlight is when I'm on someone else's phone and I don't know where the app
  140. is. That it. But why? Why is spotlight so useless on iOS? Let me explain.
  141. </p>
  142. <p>
  143. Just type is extremely useful because you literally <i>just type</i>. On iOS and
  144. Android (or any phone with no physical keyboard), you had to invoke the
  145. searching (spotlight, etc.) before you can use it. This is because you don't
  146. always have the on-screen keyboard open. Thus, it's almost out of the way to use
  147. it. With just type, you just type. This is why it's such a great feature!
  148. </p>
  149. <p>
  150. There are a ton more features that I could go through and explain but I don't
  151. wanna make this post too long.<sup><a id="fnr.5" class="footref" href="#fn.5">5</a></sup> So I'll just list a few others without
  152. explaining:
  153. </p>
  154. <ul class="org-ul">
  155. <li>Touchstone</li>
  156. <li>Exhibition</li>
  157. <li>Card Stacks</li>
  158. <li>Always accessible launcher/main menu</li>
  159. <li>Swipe up to close</li>
  160. <li>Physical keyboard</li>
  161. <li>Slider Phone</li>
  162. <li>The mirror on the back</li>
  163. <li>The device's unique it-belongs-in-my-hand ergonomics</li>
  164. <li>Patchable/hackable</li>
  165. <li>Third party apps</li>
  166. <li>It's just GNU/Linux! (You can use the terminal)</li>
  167. </ul>
  168. <p>
  169. So that's it! That's why I plan to use this phone until I see something better
  170. on the market. I hope that LuneOS turns out good and brings use the modern webOS
  171. experience that we've all been waiting for.
  172. </p>
  173. </div>
  174. </div>
  175. <div id="footnotes">
  176. <h2 class="footnotes">Footnotes: </h2>
  177. <div id="text-footnotes">
  178. <div class="footdef"><sup><a id="fn.1" class="footnum" href="#fnr.1">1</a></sup> <div class="footpara"><p class="footpara">
  179. I don't know their website's URL.
  180. </p></div></div>
  181. <div class="footdef"><sup><a id="fn.2" class="footnum" href="#fnr.2">2</a></sup> <div class="footpara"><p class="footpara">
  182. as in freedom
  183. </p></div></div>
  184. <div class="footdef"><sup><a id="fn.3" class="footnum" href="#fnr.3">3</a></sup> <div class="footpara"><p class="footpara">
  185. This is because iOS and Android don't revolve around the concept of
  186. multitasking. It was an afterthought, therefore, we don't see it's power in
  187. those OS's.
  188. </p></div></div>
  189. <div class="footdef"><sup><a id="fn.4" class="footnum" href="#fnr.4">4</a></sup> <div class="footpara"><p class="footpara">
  190. Yes, I know iOS has had that for a while. But it's very similar to just
  191. type now.
  192. </p></div></div>
  193. <div class="footdef"><sup><a id="fn.5" class="footnum" href="#fnr.5">5</a></sup> <div class="footpara"><p class="footpara">
  194. It already is.
  195. </p></div></div>
  196. </div>
  197. </div></div>
  198. <div id="postamble" class="status">
  199. <p class="author">Author: Kevin "The Nuclear" Bloom</p>
  200. </div>
  201. <div id="footer">
  202. <hr />
  203. <p>
  204. <a href="https://anybrowser.org/campaign/">
  205. <img src="/img/any-browser.png" alt="Viewable with any browser! No JS, no cookies, no bullshit!"/></a>
  206. &nbsp;
  207. <a href="http://validator.w3.org/check?uri=nuclearkev.org"><img
  208. src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0 Strict" height="31" width="88" /></a>
  209. &nbsp;
  210. <a href="http://NetBSD.org/"><img
  211. src="https://www.netbsd.org/images/powered-by-NetBSD.png" alt="NetBSD" width="88" /></a>
  212. </p>
  213. <p>
  214. Copyright © 2017-2022 Kevin "The Nuclear" Bloom
  215. </p>
  216. </div>
  217. </body>
  218. </html>