cheeaun

Many years ago, IE requires `document.createElement`.

HTML5 Shiv was needed, with added history https://www.paulirish.com/2011/the-history-of-the-html5-shiv... (2011)

Found a polyfill here https://github.com/mozilla/sanitizer-polyfill

Kinda reminds me of Flipboard https://engineering.flipboard.com/2015/02/mobile-web (2015)

Great to see this again. Amazing how this tool expanded so much over the years!

Honestly first time see a 95 cents app on the App Store

Very curious to know more about this, regarding PMTiles:

Unfortunately, making range requests in 80 GB files just doesn't work in production. It is fine for files smaller than 500 MB, but it has terrible latency and caching issues for full planet datasets.

Wondering which part incurs the latency here.

Location: Singapore

Remote: No, negotiable

Willing to relocate: No

Technologies: JavaScript/TypeScript, HTML, CSS, React, React Native, Node.js, Deno

Résumé/CV: https://docs.google.com/document/d/1kdfbN02qEBhfzSTJWmkn_JMD...

Email: cheeaun(at)gmail.com

…and I maintain a whole list of them :D https://cheeaun.github.io/repokemon/

No, it uses Mastodon's API. Can't log in with Threads, but you can follow some Threads account from Mastodon; "Known Limitations" section here https://www.augment.ink/threads-on-mastodon/

Some, but not just Discord. It's a mix of all the good parts from many apps.

Hello all, creator here. Some of you might know me as creator of HackerWeb.

Happy to answer questions and hear feedback.

There are pros/cons :) The official firebase API is generally not very straightforward, but it allows realtime calls.

Disclaimer: I maintain node-hnapi since 2011.

Interesting to see that you built your own API "wrapper" https://github.com/ddxv/hackernews-api and storing them into a SQLite db. Seems that you run it once an hour so the stories are not updated that fast, especially /newest

Found a typo: s/Accessability/Accessibility

https://cheeaun.com/blog/

Okay, turns out it's the "3D Tiles root requests per day" that's exceeded. Max 300.

For those wondering how it looks like, I have a thread here with lots of screenshots https://twitter.com/cheeaun/status/1657727482492235777

Wow that’s really fast

Limit applies per project if I’m not mistaken. More info here https://developers.google.com/maps/documentation/tile/usage_...

I’m not really sure if there’s a limit per user. It’s still beta and I can’t or don’t dare to increase the quota for now.

Looks insanely cool! I also made a simple web-based demo with Deck.GL + shadow lighting + post-processing effects here: https://cheeaun.github.io/photorealistic-3d-deckgl/

There's a limit of 250K "3D Tiles renderer requests per day" so it'll stop serving tiles if exceeded.

https://css-tricks.com/using-css-without-html/ (2010)

Hmm, how do you create this "page rule" in Cloudflare? I can't seem to figure it out.

A minimalistic Mastodon web client https://phanpy.social

Thanks! I guess I'm using Raycast (instead of Spotlight), so it actually need a reindex.

Just wondering, there's no way to launch Fleet directly without launching it from Toolbox or using CLI?

Yeah, "full-stack" does front-end too. Though from my observation it's more like 80% BE, 20% FE. Generally they spend more time working on FE tasks than specialised ones as FE becomes so, so complicated.

I've personally seen many (junior) FE engineers decide to switch to BE, "full-stack", data or devops (or even design) because of how messy FE can get.

I know it's a lot of things (organization, management, people issues, expectations, etc) and this is basically just what I observe in Singapore. Could be different in other cities/countries.

I'm a senior FE engineer in Singapore, been doing FE since 2000, here's what I think:

1. Job descriptions and interviews now are skewed towards "full-stack" or backend. Most interviews are lacking or outdated due to the fast and volatile nature of FE.

2. Literally no career progression if you're specialised in FE. Most BE or "full-stack" devs will be given a chance to become principal engineers, tech leads, engineering managers, CTOs, etc. I've seen folks with "FE Team Lead" titles but never goes beyond that.

3. FE is a subconsciously looked-down field. Neither a designer nor an engineer. Product/design team won't involve you in meetings (but will treat you like a code monkey). BE/"full-stack"/API engineers will think your job is easy and keep throwing business logic stuff to FE.

Really awesome to see this evolving to this stage :)

Thanks! Nice to know that it's still useful :D

https://cheeaun.com

List of blog posts and my side projects. Metalsmith, GitHub Pages.