Tagged “javascript”

oh no

good feature checklist when starting #projects for phones

awesome idea. Keep original links, redirect to archive if not found

Audacity for browser

how to run JS snippets when you're on your phone

A good response to falling out of love with coding. There are times it feels like passion, times it feels like drudgery and work.
There's a balance somewhere there.

I had initially hoped this elimated choices by being a single set of things for local-first dev.

Upsides are you are tweaking an existing app, improving a familiar experience. And same-origin requests vs having to mess with public APIs.

With a bookmarklet!

a "streaming replication tool" for SQLite databases. Copies the log file continuously

Loading article...

Incredible project

Performance baseline has shifted quite far up (especially network) but targeted features are still quite far behind current

Have seen this a bit lately in logs. A lot of 3 or 4 year-old versions of Chrome out there

Hand tracking in the browser!

suggestions for config of different types of PWA

Sort of like a switch statement with type annotations

I wish people would only use this for good. A stupid arms race that just makes it harder to automatically download utility bills.

not p2p for files under 5gb, but they are deleted after a day.

This looks awesome

Good article, and some other good recs in the comments

Gross and too real.

I don't know if I am as blown away as Alex but this is very cool. Like machine pair programming with text.

Short story, inspired by a GitHub thread about semicolons.

Excellent writeup. The CORS example dot points are a great example of good clear security explanations.

Reading this made me feel a little more justified in my general distrust of browser extensions. They have so much potential power!

Some of these are getting quite outrageous. But I do love the level of depth and detail of this.

From hackernews.

GitLab security scanning has a similar issue of false positives (many Node security vulns in frontend-only code). But at least they can be marked as resolved!

Awesome concept. And a nice disclaimer on context menu:

Great summary of the deluge of tools being made (from 2015!). But with a positive take at the end:

Instead of telling people to stop creating new js frameworks. Instead of discouraging people from adding to the vast amount of available tools, I'm going to encourage people to build even more tools. Pick a problem and try to solve it better than anyone else has before. Having better tools will help us push the web forward. And it's okay if 90% of them are bad. The 10% will be worth it.

Cool write up, some interesting points:

• operational transforms are complicated (mainly used for text collab)
• last value written to server wins
• ignore incoming changes from server while writing, to avoid flicker
• fractional indexing for reordering
• for undo, if things were changed (by someone else), that history is updated to prevent conflicts with redo

I really like the original one, and this is a solid reply