Top all-time · #1000
Evert Pot
Personal blog · evertpot.com · on HN as trevewebprogramming
Evert Pot's personal blog at evertpot.com covers web and programming. Since 2013, 69 different Hacker News readers have linked it 147 times, most often “ECMAScript 4: The Missing Version”. It is still writing: the last post was on 2026-07-21, and you can follow it by feed.
Most-linked posts?
- ECMAScript 4: The Missing Version9 people · 10 mentions · first linked 2020-05-28
- HTTP/2 Push is dead6 people · 8 mentions · first linked 2020-11-12
- JWT should not be your default for sessions5 people · 5 mentions · first linked 2021-05-10
- Discovering features and information via HTTP OPTIONS3 people · 3 mentions · first linked 2024-10-16
- I wish JSON5 was more popular3 people · 3 mentions · first linked 2023-01-09
- Building multi-step login forms that work well with password managers3 people · 3 mentions · first linked 2025-04-13
- Firefox removes RSS support3 people · 3 mentions · first linked 2018-08-03
- Package managers should be immutable, distributed and decentralized3 people · 3 mentions · first linked 2016-03-23
- Does OAuth2 have a usability problem? (yes!)2 people · 3 mentions · first linked 2023-04-27
- Dropbox starts using POST, and why this is poor API design2 people · 2 mentions · first linked 2015-03-02
What Hacker News says?
When typescript came out, you were seen as weird for wanting such a thing. I once had a VP of engineering dm me to tell me to stop discussing typescript in the company dev channel around 2015 (if you're reading this, that was a dick move). Nowadays you're kinda odd man out if you don't want types. So the idea of adding types even optional ones probably wouldn't have gone down well. The closest we ever came was es4 w…
Comment linking /ecmascript-4-the-missing-version/
on “TypeScript types can run DOOM [video]”Submitted HTTP/2 Push is dead as a story · 354 points
HN discussionHTTP/2 push is super dead: https://evertpot.com/http-2-push-is-dead/
Comment linking /http-2-push-is-dead/
on “Engineering for Slow Internet”Submitted Ten years on LinkedIn as a story · 336 points
HN discussionIf you view an RSS or Atom feed in chrome today you just get a screen of xml eg. https://developer.wordpress.org/news/feed/ In the golden old days of 2018, browsers at least applied some styling https://evertpot.com/firefox-rss/ You can still manually apply styling using xslt https://www.cedricbonhomme.org/blog/index.xml
Comment linking /firefox-rss/
on “XSLT RIP”Submitted JWT should not be your default for sessions as a story · 335 points
HN discussionIt was an extension to ES4 called E4X - it allowed inline xml along with a new xml data type. More info here: https://evertpot.com/ecmascript-4-the-missing-version/
Comment linking /ecmascript-4-the-missing-version/
on “VanillaJSX.com”Submitted Firefox removes RSS support as a story · 265 points
HN discussionYe Firefox had a reasonable viewer too. https://evertpot.com/firefox-rss/
Comment linking /firefox-rss/
on ““Wherever you get your podcasts” is a radical statement”Submitted PHP Sucks as a story · 253 points
HN discussionThe blog post links to another one of their blog posts with a real world example for push: https://evertpot.com/h2-push-for-apis/
Comment linking /h2-push-for-apis/
on “HTTP/2 Push is dead”Submitted HTTP/1.1 just got a major update as a story · 248 points
HN discussionYeah this works well for specifically this case. There's other cases that I feel we haven't had a good chance to explore, specifically as it pertains to APIs. I wanted to kill many compound HTTP request within a single one. Many API formats pack many logical entities in a single response, and that doesn't work well with caches. Wouldn't it be nice if the next paradigm shift in API development goes towards every enti…
Comment linking /h2-parallelism/
on “HTTP/2 Push is dead”Submitted Google's CardDAV server isn't standards compliant (2014) as a story · 240 points
HN discussionI hope browsers implement 103 early hints. I’d like to tell the browser to preload assets while the server is still working on the response, which may take a significant amount of time to determine if the response is 200, 401, or 404. https://evertpot.com/http/103-early-hints
Comment linking /http/103-early-hints
on “HTTP/2 Push is dead”Submitted One Year in San Francisco as a Software Engineer as a story · 220 points
HN discussionhttps://evertpot.com/dropbox-post-api/ This discuss some option for the GET vs POST. In Kibana, everything is done over GET as get parameters, and I find that extremely annoying and a poor design. A lot of public APIs also don't honor or have any intentions in supporting or using PATCH. Most APIs I have worked with only use PUT for modification. Anything resembles "creation" is automatically a POST.
Comment linking /dropbox-post-api/
on “Microsoft REST API Guidelines”Submitted Request bodies in GET requests as a story · 219 points
HN discussionhttps://evertpot.com/resume/
Comment linking /resume/
on “Ten years on LinkedIn”Submitted Performance Testing HTTP/1.1 vs. HTTP/2 vs. HTTP/2 and Server Push for REST APIs as a story · 198 points
HN discussionProbably the main reason why the poster should better continue using LinkedIn: https://evertpot.com/resume.html 404 File not found
Comment linking /resume.html
on “Ten years on LinkedIn”Submitted Dropbox starts using POST, and why this is poor API design as a story · 154 points
HN discussionNot at all. AS1 was plain ES3. movieclip._x or movieclip._alpha (as in position and alpha blending) were accessed by properties with underscore to denote that you were using accessors (getters/setters). Internally properties like Object.prototype.__proto__ had two underscores to denote they were private. In AS2 you had: class Foo extends Bar implements Xyz { private foo public function set x (value : Number) : void…
Comment linking /ecmascript-4-the-missing-version/
on “Why does target="_blank" have an underscore in front? (2024)”Submitted Package managers should be immutable, distributed and decentralized as a story · 137 points
HN discussionThe reason I'm a little disappointing about this, is because I was really hoping for a future where we improve sending collections of items from APIs. One issue with the typical API formats is that all the data for each resource is shipped with the collection, which means that client caches are unaware of the 'transcluded'/'embedded' resources. Server push, if implemented well could have allowed us to just push ever…
Comment linking /http-2-push-is-dead/
on “Removing HTTP/2 Server Push from Chrome”Submitted Taking a Look at Mastodon as a story · 131 points
HN discussionFascinating work, thank you! Possible issue: have I misread it, or is the explanation of HTTP/3's advantages entirely missing from this section[1]? It's in the section header, but HTTP/3 isn't mentioned again until "The perfect world"[2] and that section doesn't clarify how HTTP/3 matters to the discussion. [1] https://evertpot.com/h2-parallelism/#http2-and-http3 [2] https://evertpot.com/h2-parallelism/#the-perfect-…
Comment linking /h2-parallelism/
on “Performance Testing HTTP/1.1 vs. HTTP/2 vs. HTTP/2 and Server Push for REST APIs”Submitted ECMAScript 4: The Missing Version as a story · 117 points
HN discussionDebian policy is very sane (no network access during build), but it does seem like modern software just assumes that the Internet is always available, and all dependencies (including transitive) are out there. The assumption is a bit fragile, as proven by the the left-pad incident ([1]). I hope that whatever the outcome of the discussion in Debian will be, it would keep the basic policy in place: not relying on thin…
Comment linking /npm-revoke-breaks-the-build/
on “Debian discusses vendoring again”Submitted Browser tabs are probably the wrong metaphor as a story · 117 points
HN discussion
