<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bobcoin Söderqvist on Medium]]></title>
        <description><![CDATA[Stories by Bobcoin Söderqvist on Medium]]></description>
        <link>https://medium.com/@bjorn_js?source=rss-157aa737d5f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*4rdnPVzDLrh8_yit.jpg</url>
            <title>Stories by Bobcoin Söderqvist on Medium</title>
            <link>https://medium.com/@bjorn_js?source=rss-157aa737d5f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:03:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bjorn_js/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Was Correction Tape a waste of my time?]]></title>
            <link>https://medium.com/@bjorn_js/was-correction-tape-a-waste-of-my-time-7677692950d7?source=rss-157aa737d5f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7677692950d7</guid>
            <dc:creator><![CDATA[Bobcoin Söderqvist]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 21:13:09 GMT</pubDate>
            <atom:updated>2020-08-11T21:13:09.875Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*azKwRBSG9H4IS3cTSiTN0Q@2x.jpeg" /></figure><p>I did not enjoy typewriting class.</p><p>The idea with touch typing is to keep both hands’ fingers at a fixed home position, only to ever change the finger responsible for the key needing to be pressed. You should do this without peeking on the keys. Once you’ve mastered these techniques you’ll be able to transcribe texts from a sheet of paper without taking your eyes off the paper to look down at the keys. Our teacher, a short 40-something brunette lady in glasses, would cover my view of the typewriter with a sheet of paper. My friend had told me that she had a past as a stripper. I don’t know if this is true. Anyway. Unlike a computer, erasing on a typewriter was not for free. If I did use the eraser she’d remind me, ”you’re wasting correction tape!”</p><p>I can imagine, much like our teacher, some of the typewriters might have had higher hopes than being in this class room with us. The one in front of me had once, at least in my mind, wished itself being used by a young aspiring poet slowly pondering the next word of their newest haiku, then swiftly and softly keying it in. But even a cookbook would be a higher purpose than being stuck with me erasing multiple misspelled letters at a time from dull words in gibberish sentences.</p><p>As the months progressed I did learn how to touch type. I could in fact type without having to look down. My muscle memory knew the position of each key and which finger to use. When I thought of a word, I could type it without concentrating. But I could not think of any future scenario when I’d want to transcribe a sheet of paper.</p><p>On the last day of typewriting our teacher was late. A nasty surprise was waiting on her desk: A nude photo of our teacher cut out of a 20 year old porn magazine.</p><p>Even if I had no part in the prank, I felt terribly ashamed as she moved the photo away from her desk and into the bin. My best friend gave me his verdict on the entire year of typing:</p><p>”This was a waste of time. We’ll be using computers from now on.”</p><p>His prediction was correct. My age group was the last to attend typewriting class. After this year, all typewriters were out of duty in Nyvång school.</p><p>But however useless our skill of transcribing texts from one paper to another felt like when comparing to the copy / paste paradigm of desktop computing, being able to touch type without having to look down is something I’m still extremely thankful for throughout my 25+ years with computers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7677692950d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zepto made me a GIF nerd — from my “mistakes” series]]></title>
            <link>https://medium.com/@bjorn_js/zepto-made-me-a-gif-nerd-from-my-mistakes-series-65bcad78841e?source=rss-157aa737d5f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/65bcad78841e</guid>
            <category><![CDATA[webkit]]></category>
            <category><![CDATA[ipad]]></category>
            <category><![CDATA[touchscreen]]></category>
            <category><![CDATA[zeptojs]]></category>
            <category><![CDATA[frontend-development]]></category>
            <dc:creator><![CDATA[Bobcoin Söderqvist]]></dc:creator>
            <pubDate>Fri, 05 Jun 2020 20:00:44 GMT</pubDate>
            <atom:updated>2020-06-05T20:00:44.009Z</atom:updated>
            <content:encoded><![CDATA[<h3>The rise of touch devices</h3><p>When the iPhone arrived in 2007 it came with a touch screen which was revolutionary. Earlier screens required a stylus, this one supported all ten fingers at once and with an incredible accuracy and speed. It was the first time we could scroll a website using our fingers. It felt like you were moving the page as opposed to ordering a computer to do so.</p><p>When building web sites I’d always assumed your computer was hooked up to a keyboard, a mouse and a display. All of a sudden you couldn’t assume this anymore.</p><h3>Death to Flash</h3><p>In 2010 Adobe’s Flash was still the king of interactive experiences on the web. Flash sites worked well on desktops and on Android and people couldn’t understand what was taking so long, why couldn’t we just get Flash on iPhone yet? Just after the iPad was released in April 2010, Steve Jobs posted the famous <a href="https://www.apple.com/hotnews/thoughts-on-flash/">Thoughts on Flash</a> essentially saying: It’s not an open standard, unreliable, insecure, unperformant and drains the battery. It’s not designed for touch screens. But mainly: Apple doesn&#39;t want a layer between the OS and the apps if that layer is controlled by another actor than Apple.</p><p>Apple was most definitely aiming for the open web technologies to catch up with the user experience of Flash. With the rise of HTML5, CSS3 and ES5, web apps could finally begin to challenge Flash apps and native apps. Mobile Webkit was aspiring to be a great browser to develop rich interactive experiences for with many new ideas that later became standards; Canvas, the touch events and more. By using its <em>-webkit-</em> prefix it could adopt CSS3 proposals before they were finalized.</p><h3>My first attempts</h3><p>It was scary, weird and exciting at the same time. I saw that this device would be big enough to play board games on. I began sketching on various ideas for board games that I could implement for the iPad’s Mobile Webkit browser. Chess and Scrabble were the most interesting in the list and I decided to get an iPad as soon as possible.</p><figure><img alt="The first iPad" src="https://cdn-images-1.medium.com/max/1024/1*Jsy0kwmpWa3yvL_WOuklcg.jpeg" /></figure><p>Let’s say you were interviewing me for a job today. If I pulled out an iPad from my backpack and showed you a rough demo of a game where you could drag a few pieces around, with a click sound on drop that triggered around 200ms delayed, you’d be quite underwhelmed. But then and there, I was the only applicant to own an iPad, let alone having built something using HTML5 for it. I was hired on the spot.</p><p>I was thrilled.</p><h3>Too large to fit</h3><p>I faced several challenges when writing web apps for the iPad. One was that Mobile Safari had strict memory constraints because of the limited physical memory of the device. Any file larger than 50kB unzipped was deemed too large to fit in the cache. It meant jQuery was too large to fit — it weighed around 90kB at the time being.</p><figure><img alt="jQuery logo" src="https://cdn-images-1.medium.com/max/700/1*bisABuuGtSpy4V_KvPQUFg.jpeg" /></figure><p>Any website using jQuery had to re-read the file from the network at every refresh and after each restart or crash of the app. Furthermore jQuery hadn’t gotten support for the <em>touch</em> events yet so you had to use the onClick event which, for various reasons, added a 200ms delay before actuating. These problems annoyed me and I knew that I wanted something smaller, but similar.</p><h3>Choosing something new</h3><p>Voices in the JavaScript community were talking about something called JavaScript MVC. I wasn’t prepared to begin learning an entirely new paradigm; I thought that all I needed was a jQuery with a smaller file size and some touch events. My prayers were heard; <a href="https://zeptojs.com/">ZeptoJS</a> promised to have the same interface as jQuery while not needing any code for the DOM queries (in jQuery called Sizzle) and simply using native DOM queries. Because I knew my target browser was only Mobile Safari, I was willing to accept this constraint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0593nVdQaIqwRTwAsx62LQ.png" /></figure><h3>Getting to know the new kid on the block</h3><p>I went with Zepto! It felt good to go with an up and coming library instead of the dinosaur built for older browsers.<br>It had its share of problems. To my surprise, memory would leak when images were removed from the DOM. I found out when my slideshow application would crash the browser after a few full screen images had been shown. I could see that the JavaScript workaround to fix Mobile Safari’s garbage collection was there, and yet it didn’t work. To solve it I had to learn a lot about GIFs.</p><p>Firstly, the fix for allowing the browser to drop its reference to an image was to change its src to the smallest image possible. This sounds crazy now but there was no better fix at the time. A smart way to do that from JavaScript is to base64 inline an image of a 1x1 transparent pixel. I was happy to see this image again as I had used it <a href="http://www.devx.com/projectcool/Article/19937">before CSS to do pixel pushing</a>. invis.gif, where have you been all these years?</p><p>And yet, when the tried to view this image, it wasn’t there. Not only was it not visible (as intended), the browser displayed a broken image icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*Xvi-zz5p6_orWH-nKbnxZw.jpeg" /></figure><p>The developers of Zepto were all into golfing, and would often make <em>leet</em> changes to the code, for example</p><blockquote>typeof a === function</blockquote><p>into</p><blockquote>(typeof a)[0] == “f”</blockquote><p>Why did they optimize the code manually and not using a minifier? YUI compressor and Google Closure Compiler were both available. I’m not certain of the answer, but I know that the minifiers either produced unreliable output or didn’t manage to minify that much.</p><p>A <a href="https://en.wikipedia.org/wiki/Code_golf">golfing developer</a> had found the base64 inlined image and thought, what if I just replace it with an empty string? Said and done.</p><blockquote>element.src = ‘data:image/gif;base64,R0lGODlhAQABAAAAADs=’</blockquote><p>into</p><blockquote>element.src = “data:image/gif,”</blockquote><p>As a result, the browser would not consider this a valid URL and not replace the image. All I needed to do was to get some Zepto developer to add back the image from before! But I first needed to prove that this was broken, and which solution would be the best.<br>Trying to gather a good material I assembled some of the smallest GIFs that I knew of. You can make smaller ones than the 43b that is in use normally? Yes, there’s <a href="https://stackoverflow.com/questions/2570633/smallest-filesize-for-transparent-single-pixel-image">several hacks out there to create even smaller GIFs</a> than the smallest one when following the standard. I think 14b must be the smallest one for real world use. We’re golfing for smaller filesize after all.</p><p>I then proceeded to try them in all of the supported browsers. It turned in that the one they had previously used was the only one that worked in all four major browsers. After that, <a href="https://github.com/madrobby/zepto/issues/118">the maintainer reverted</a> and the memory bug was fixed.</p><h3>What did I learn?</h3><p>Choosing an indie library comes with a cost. I saved a few bytes and the application loaded a little faster. At the same time I got bit by a memory bug which took a long time to debug and some convincing before the library would adopt the fix. And I got to learn “useless” details about the GIF standard.</p><p>How did it change me? I think twice about choosing a cool new library. Often times, the most popular one will have less bugs and better documentation. I also learned that for single page apps, a term that didn’t exist yet, jQuery and its siblings were just not a good fit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65bcad78841e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Web, then and now]]></title>
            <link>https://medium.com/@bjorn_js/the-web-then-and-now-922aa241d469?source=rss-157aa737d5f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/922aa241d469</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vintage-web]]></category>
            <dc:creator><![CDATA[Bobcoin Söderqvist]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 21:29:54 GMT</pubDate>
            <atom:updated>2019-11-05T21:29:54.650Z</atom:updated>
            <content:encoded><![CDATA[<h3>When I first tried surfing on the Web</h3><p>A high school teacher of mine had bought and setup a modem, installed Netscape and <a href="https://en.wikipedia.org/wiki/Winsock">Trumpet Winsock</a> on the Windows 3.11 computer. He was on a mission to teach the kids about computing, programming and the Internet, all of which he believed to be the future. Two of my then friends invited me to computer class and that’s how we got to try out the Internet for the first time. He’d pick three students each lesson to visit the Internet Room — a tiny room that contained the school’s only Internet connected computer. And this time it was us.</p><figure><img alt="An early 3D rendering of a woman and a man gesturing to each other, standing in front of two web pages" src="https://cdn-images-1.medium.com/max/1024/1*VfsIyCQy2mpDj4vefmuxiQ.jpeg" /><figcaption>This was a common portrayal of the Web</figcaption></figure><p>On the desk was, aside from the expected mouse, keyboard and modem, a paper with instructions on how to <em>get online</em> and a computer magazine which then featured a big section of tips about web pages to visit. The Web was a big deal in the magazines at the time. For instance, one magazine I used to buy came with a 1.44MB floppy disk of downloaded websites so that people like myself, who didn’t own a modem, could try out a random selection of sites offline. You can’t fit that many websites on one floppy, but my computer didn’t have a CD-ROM device. I had just upgraded from a hand-me-down 286 with a black and white display to a 486 with 8MB of RAM, which is all to say that I could finally type “win” and use a graphical user interface for most of the programs that I was using. I was fine and didn’t really need an optical drive that badly. Besides, you’d be surprised at how many websites you could fit into 1.44MB back then.</p><p>I and my friends followed the instructions on the paper, until we heard an alarming noise from the modem. We were certain that we had broken it. If you have never heard a modem connecting, it gives a lot of high-pitched random beeps and boops with additional noises. After it stopped whining we were connected. The connection timer starts counting from 0:00 so that you can keep track of how long you’ve been connected — since the phone line owner paid by the minute.</p><p>We opened Netscape. Now what? We tried some random URL:s from the magazine. Amazingly they worked. A co-student had already made his own <em>homepage</em> (what we used to call personal websites) and jotted down his URL at the bottom of the instruction sheet. It also worked. Like any good webmaster at the time, he had provided some contact information. If the visitors had any questions about his website they could just phone him.<br>He had added a website counter image to his site. This way you could tell how many visits his homepage had gotten. We were visitors number 17.<br>He had a few hyperlinks to other websites. This was good practice. That way, the user could continue <em>surfing</em>. Perhaps in the future you could keep clicking for hours, finding more relevant and interesting content with each website. Related, we had also heard of Moore’s law, that (roughly translated) states that computer capacity will double every two years. Even though we had seen it working it was difficult to believe that this could continue for more than a few years from now.</p><p>After this we tried something wild. Someone had said that there were already quite a lot of registered domains and suggested we’d simply try making up a few ourselves and checking whether they existed. Some of them did. Being fourteen and curious of sex I tried playboy.com. It worked. The teacher came back into the room and my face turned very red. He did not punish me.</p><h3>The rise of homepages</h3><p>I got into building my own homepage soon after this. Because of my limited amount of RAM I couldn’t use any of the cool HTML editors of the time such as HotDog or HoTMetaL (many products used this naming pun with uppercased H, T, M and L; most famously HoTMaiL). I would edit the files in DOS, then type “win” to start Windows and finally open Netscape to preview the results. I realised soon that Notepad fit my memory constraints and saved a few minutes for each iteration of <strong>edit</strong> — <strong>save</strong> — <strong>refresh browser</strong>. Despite being quite simple by today’s standards, Notepad was then a popular editor for HTML. Several homepages had a badge with something like <a href="http://www.notepad.org/logo.htm">“made with Notepad”</a> or “proudly hand coded in Notepad”.</p><p>With enthusiasts creating homepages and hyperlinks the Web grew. Its usefulness increased. We started using search engines (then called web crawlers) just to find the content we were looking for. We didn’t make homepages to make money. We made them because we were fascinated with this new gigantic medium and where it could take us. If I could put something up there that someone else found useful, that’s great.</p><p>Most web servers ran Linux and most had Perl. You could visit Matt’s Script Archive and download a script for your own counter, or guest book. Forums became a thing. Users didn’t need to learn HTML and create their own homepage just to add content to the web. Together we built a forever growing database. I put up the lyrics of some songs that I liked. There were many good guitar tabs pages. Just a few years later there were even pages where you could download MP3:s of a few famous songs. My computer was too weak to play them at the time, let alone would most of them fit a floppy.</p><p>When I visited a homepage, I knew that the author wanted for me to have the best experience. One example is that they would add a disclaimer to the front page: Best viewed in 640x480 (later 800x600, and some disrespectful occasions of 1024x768: I mean most people’s hardware couldn’t produce that resolution in 1994). They never wanted to get to know my shopping history, my friend graph, or to obstruct the content by showing ads, cookie consent and GDPR information. Even annoying pop-ups came later.</p><h3>The disappointing Web of today</h3><p>Fast forward to 2017 I was trying to remember the lyrics of a lullaby I wanted to sing for my kids. I started searching the Web and got increasingly frustrated. The first result was a slow page. It was showing lots of ads. It obstructed the content. I couldn’t scroll down to read the entire text. It crashed my phone’s browser. <br>But it wasn’t just that one page. All of the pages I found were annoying at best, and useless at worst.</p><h3>A dream</h3><p>I miss the days where an international community of enthusiasts would create content for the Web just for fun. That’s why I created <a href="https://vaggvisor.org/">a website that simply contains a set of Swedish lullaby lyrics</a>. It’s ad free. It’s fast. It has almost no Javascript. The <a href="https://github.com/cybear/vaggvisor.org">hosting of the source code</a> and the <a href="https://www.netlify.com/">web hosting</a> is for free. <br>The pages can be edited in plain text with no knowledge of HTML.</p><p>It’s my little fantasy of how we, the enthusiasts and users of the web, could take back some control of producing and owning valuable content on the Web.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=922aa241d469" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>