tylerchurch
Joined 11 years ago
Joined 11 years ago
Poke through MDN and see what you find.
Do you know about dialog? https://developer.mozilla.org/en-US/docs/Web/HTML/Element/di...
MutationObserver? https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...
URL? https://developer.mozilla.org/en-US/docs/Web/API/URL_API
I can’t tell if there’s just no stock, or huge demand, but either way it seems like a great product. If only you could buy it.
Reviewed against what? Who is writing the specs?
How could the LLM help?
Given that it is missing the critical context and knowledge described in the article, wouldn’t it be (at best) on par with a new developer making guesses about a codebase?
I've worked on plenty of teams with relatively small apps, and the difference between:
1. Cloud: "open up the cloud console and start a VM"
2. Owned hardware: "price out a server, order it, find a suitable datacenter, sign a contract, get it racked, etc."
Is quite large.
#1 is 15 minutes for a single team lead.
#2 requires the team to agree on hardware specs, get management approval, finance approval, executives signing contracts. And through all this you don't have anything online yet for... weeks?
If your team or your app is large, this probably all averages out in favor of #2. But small teams often don't have the bandwidth or the budget.
It's my favorite way to slowly add some order to legacy apps that have been overcome by jQuery soup.
It sounds like user input is the _only_ input, so why not just use a POST request with a body?
import {vector} from 'std';
Which I think is a reasonable compromise, you're only bringing vector into scope rather than all of the standard library.
So probably a different pool than the 10+ year people.
If you've unfollowed everyone what do you expect to see?
No kidding. I'm 2 or 3 years into working on a SaaS app started in ~2013 and I still get bug reports from users that make me say "what!? we have that feature!?"