Remy Sharp

Worse than taking up screen space, these bars often exhibit laggy scrolling behavior and cause other UI bugs. There are very few well working implementations of such fixed bars, partly due to difficulties like the position:fixed implementation in Mobile Safari[0] - unless that has been changed in iOS7. I highly recommend to refrain from using position:fixed on mobile devices. [0] http://remysharp.com/2012/05/24/issues-with-position-fixed-scrolling-o…

http://yeoman.io/ tries to solve it... (like it mostly for its live reload feature) Here is another great example - http://remysharp.com/2012/12/21/my-workflow-never-having-to-leave-devt… My two cents: find solutions... People who make tools are just like us, some empathy, accept what you cannot change :)

I've been using Twitter as part of my blog and have started replacing the href of links with the expanded link. So if you go to my blog or follow me on twitter the links look the same but if you hover on a link the status bar shows the end link. I do this on the server side, with Python code I mentioned http://news.ycombinator.com/item?id=406608 but it is possible to do it client side as well with something like http://remysharp.com/tinyurlapi

I love the look and feel that went into the design of Material here, but with respect to web components, we should be worried that Google is monopolizing the future of the web. See my comment below: https://news.ycombinator.com/item?id=7947119 It bugs me that Polymer is being marketed as "polyfills", since the term polyfill generally tends to connote something that fills in for an already agreed upon w3c standard that will appear in all user agents eventually. Whereas web components and shadow dom is still very much in the proposal/experimentation stage and has a ways to go before reaching standardization. There are still some disagreements to be resolved by all those that contribute code to the major user agents. Calling polymer a polyfills library is misleading and an abuse of the intent of the term polyfill [0]. Also related: "Apple Removes Shadow DOM from Safari"[1][2] [0] http://remysharp.com/2010/10/08/what-is-a-polyfill/ [1] http://trac.webkit.org/changeset/164131 [2] https://news.ycombinator.com/item?id=7243122

Hey there, I developed the site but we have our amazing head of design, Skyler, to thank for the beautiful layout. The First1000 site is entirely native javascript/html5/css3. No jQuery or frameworks. I believe that frameworks are fantastic but only if you are utilizing their full potential. In the past I've included jQuery for random bits and pieces but I found myself coding around it and I really don't like including a library where I only use a couple of its functions. Here are some of the cool things we included. Multiple background images in CSS3. This is a beautiful thing. We should rarely have to nest divs inside divs to achieve a layered background effect now. Transitions (Webkit, Mozilla, Opera etc have their own implementations) for most of the animations you see on the site. I found myself using the transiton-delay: property a fair bit too. This is really helpful as you can set a delay before the animation start point. Using delays is how we make the flip cards start from the top left and gradually flip over to the bottom right. Each group of flipcards (diagonally) are given a different transition-delay. We transition opacity, width/height, top/left positioned coords and background-colors. We use Transforms to achieve rotation. Each card has a slightly different angle ranging from -3deg to 3deg. If I had NOT been using transforms then I imagine each card would have been a nightmare to implement at an angle like that. It would have taken forever and I would…

see also : https://developer.mozilla.org/en-US/docs/Glossary/Polyfill What is a Polyfill? [2010] https://remysharp.com/2010/10/08/what-is-a-polyfill

> Your startup idea was to host large amounts of copyrighted material for profit, without checking who had the rights to distribute that material? of course not don't be silly. but so far liability was on the uploader, when the police comes knocking you gave out user data and that was it. see, for example, the jsfiddle constant issue with illegal content: https://remysharp.com/2015/09/18/jsbin-toxic-part-5 people miss here that any user generated content could be part of a copyright. even text if they are lyrics. there's NO user platform that's safe.

Interesting to read about those fraudsters. Really annoying when you're a small business. I remember reading something similar from Gittip[0], and also mentioned on the linked blog post, jsbin[1]. I wonder what other small startups are using to detect / prevent this kind of fraud? Are there any good services in this space? and why won't recurly/stripe et al bundle this in? (or maybe they do, and I just don't know about it...?) [0] http://blog.gittip.com/post/35057426257/stolen-money-on-gittip-part-1/ [1] https://remysharp.com/2015/09/17/jsbin-toxic-part-4

Possibly Remy Sharp's "The Toxic Side of Free" series about running JSBin - https://remysharp.com/2015/09/14/jsbin-toxic-part-1

He did (stripe): https://remysharp.com/images/jsbin-stripe-fraud.png

This is a really good question. It's funny, a little digging led me back to the same blog. https://remysharp.com/2014/12/30/vatmoss-proof I could see the location information being supplied using a Bitcoin service provider (Coinbase?), but whether it is accepted as "proof," is questionable.

Why not, instead, show an ellipsis in place of the majority of the subdomain leading up to the domain and increase opacity of the domain compared to subdomains and the pathname. This is similar to what happens when the path is too long for the omnibox, but simply the effect of putting the domain as far left (in the omnibox) as possible. i.e. instead of seeing: [ www.mybank.com.credicards.wt3_segment_secure.login.html.evil-site.com ] You see: [ ...html.evil-site.com/ ] (where "...html." are semi-opaque). I mocked up what I'm suggesting here: http://remysharp.com/2014/05/04/on-chrome-hiding-urls-to-protect-users…

Add the misuse of the term "polyfill" to that list... some passionate debate here: http://remysharp.com/2010/10/08/what-is-a-polyfill/

http://remysharp.com/2010/10/08/what-is-a-polyfill/ "Shim, to me, meant a piece of code that you could add that would fix some functionality, but it would most often have it’s own API. I wanted something you could drop in and it would silently work (remember the old shim.gif? that required you actually inserted the image to fix empty td cells – I wanted something that did that for me automatically). I knew what I was after wasn’t progressive enhancement because the baseline that I was working to required JavaScript and the latest technology. So that existing term didn’t work for me."

Remy's block post about the idea and development: http://remysharp.com/2013/03/18/quick-dirty-forking/

Whoa, I had to look up the word "polyfill", since I had never seen in in this context before. Extra confusing since the topic was close to the filling of polygons (a common operation in vector graphics rendering). Turns out the word was coined by Remy Sharp, and means "replicate an API using JavaScript (or Flash or whatever) if the browser doesn’t have it natively" (quote from http://remysharp.com/2010/10/08/what-is-a-polyfill/). Interesting, but depressing to be so "out of touch". Cue shouting about lawn, et cetera.

Something like this, but for all (standard) source files, not just JS. http://remysharp.com/2012/12/21/my-workflow-never-having-to-leave-devt…

position: fixed is quite broken on IOS[1] [1] http://remysharp.com/2012/05/24/issues-with-position-fixed-scrolling-o…

I hadn't heard of the term polyfill before (despite having used them) ... just means providing browser specific code to patch the renderer for the lack of an otherwise supported feature. It was the first thing I searched for on-site, didn't leave me any the wiser. eg http://remysharp.com/2010/10/08/what-is-a-polyfill/

It works on Android, yes. However, sound is not supported on iOS or Android devices yet. The <audio> implementation on those platforms is unbelievably broken and there's not much I can do about it other than wait for Apple and Google to fix it. This blog post does a good job at mentioning the problems with sound on iOS and how to work around a few of them. Android has basically the same problems: http://remysharp.com/2010/12/23/audio-sprites/ Still, even with all those workarounds, you have a lot of lag (>0.5s) before a sound plays and you can only play one sound at a time. That's hardly suited for games :/

Remy Sharp's Storage pollyfiller[1]. (What's a pollyfill? Good question[2]!) ----- [1]: http://gist.github.com/350433 [2]: http://remysharp.com/2010/10/08/what-is-a-polyfill/

Look, I'll say this as an admitted domain hoarder myself, but: The thing that sucks about namespaces is that there's no way to win. If people can own them without an ongoing cost, they'll go unused (think of people squatting really good social media usernames without activity on the account). If people have to pay an ongoing cost, there will be a lot of stuff where the cost-benefit to them of maintaining the domain part of those [Cool URIs] they picked doesn't make sense... so a lot of cool stuff has disappeared from the internet, especially the personal or non-commercial freely shared resources, leaving an ad-ridden wasteland behind. So yeah, I do kinda think that people should have their own domains if they have enough internet presence to want to set up a Linktree, but way too many techie people take the drawbacks for granted. [Cool URIs]: https://www.w3.org/Provider/Style/URI.html is the link everyone knows, but https://remysharp.com/2016/12/22/cool-uris-dont-change is the better one

This one is good too: http://remysharp.com/jquery-api/