HN user

longlho

24 karma

[ my public key: https://keybase.io/lh; my proof: https://keybase.io/lh/sigs/3a_8LQg-7vTWK4PkQqLRB0R5a1jFKX5tpVdgrkQX2sE ]

Posts5
Comments17
View on HN

yup, so why bloat up the spec? Introducing a 3rd option that represents a non-deterministic remote state isn't entirely helpful IMO. Having the ability to abort the connection should be enough (which is a rejection).

canceling GET is the simplest use case, XMLHttpRequest/fetch is already able to abort. POST/PUT/DELETE, however, modifies remote resources which cannot be easily "canceled" (it might corrupt server state and/or transaction might even have to extend to client being able to fully "resolve" the Promise?)

Not sure if this is needed. A Promise is basically an async representation of a transaction where "cancel" can mean a slew of things. Even w/ `fetch`, what's supposed to happen when you cancel? (connection abort? resource modification reverse?) Cancel should just be a `rejection`, because the Promise's purpose (update a remote resource) wasn't fulfilled

[dead] 11 years ago

This is not surprising at all. "sudo"-ing as other users is extremely useful for debugging.

Agreed w/ honestfeedback.

- Overall project structure seems a bit unorganized IMO (no centralized build process, gulpfile inside subfolder). Overall this makes it fairly hard to dive right into the project. It might be my lack of experience in PHP project structure.

- I think pulling in a server & a db might be an overkill. Local storage will do the job perfectly.

- Mix of tabs & spaces is also very messy.

- Styling is pretty sloppy too I believe. No clear organization/reusability in the stylesheets.

- Vendor scripts/generated scripts should not be committed to the repo IMO. There're already bower & CDNjs & a bunch of other services.

- Your JS is also very module/singleton-based although some of them are clearly object-oriented. Also seems to be a mix of jQuery usage & DOM directly, why not 1?

I think what they're looking for is a couple of simple JS that's easily tested, maintained & expanded which IMO is more important for senior candidates. Less senior ones can always bang this out quickly but senior ones care way more about other attributes of a project than just getting it done asap.

iHeartRadio -- New York, NY -- Full Time

We're looking for a full-stack engineer to work on our high visibility music products. This is not your average "jQuery monkey" position, you'll be working on cutting-edge high traffic Javascript/Python applications, where reliability and high performance are key. The person should be responsible for architectural software decisions, as well as software implementation in a team environment. The environment is dynamic with focus on creative thinking and usage of open source to solve complex problems and business needs.

Our stack: - Python Django - Gunicorn - memcached - Chef - HTML/CSS/JS and the latest greatest stuff Web can offer.

If you're interested, shoot my your resume AND github at longho@clearchannel.com