Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
spion
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
29 ms
·
271.
▲
by
spion
4y ago
> There are languages / runtimes where there could not be two different versions of the same thing in one binary But I'm not talking about one binary here. I'm talking about multiple, separate services.
272.
▲
by
spion
4y ago
I don't think that's quite true. In my experience multi-repos have the edge here. If you have one key dependency update with a feature you need, but you need substantial code updates and 80 services depend on it, that may be impos
273.
▲
by
spion
4y ago
In a multi-repo setup you can upgrade gradually though, tackling the services that need the upgrade the most first. Can you do that in a monorepo setup?
274.
▲
by
spion
4y ago
But with a multi-repo, its possible to e.g. upgrade the dependency just for a single service that has an immediate need for the upgrade, isn't it?
275.
▲
by
spion
4y ago
> any breaking changes should be dealt with in the same change as the version bump Does this mean that some things will never get updated, as the effort required is impossibly high?
276.
▲
by
spion
4y ago
Using bazel is nontrivial amount of effort (most of the open-source rules don't really work in a standard way due to the fact that google doesn't work in a standard way). I guess with a 1K engineering company you can afford a subs
277.
▲
by
spion
4y ago
A while ago I picked up PureScript again, and it has a new life. The tooling (both cli and editor) has matured, the number of code examples has grown a lot. Its quite pleasant to use! All the tools and other goodies are listed here https:
278.
▲
by
spion
4y ago
Agreed, deploying the lighter model seems like the quickest way to leave a bad impression. Wonder if doing a slow "exclusive" rollout with invites (like with gmail) would be better from a marketing perspective
279.
▲
by
spion
4y ago
Title should probably be changed to: "Twitter has a rate limiting bug"
280.
▲
by
spion
4y ago
The main problem is that the worst consequence of not following this rule is still perfectly usable, while the worst consequence of overdoing it is the font-weight: 300, color: #555 nightmare that we see everywhere on the modern web
281.
▲
by
spion
4y ago
> Use near-black and near-white instead of pure black and white This is not safe. During the past few years this became a trend, legibility has suffered greatly and eyestrain has increased significantly for me. It gets even worse when co
282.
▲
by
spion
4y ago
ChatGPT is capable of reasoning but it has only one tool: "thinking out loud". If you'd like it to solve more complex problems, ask it to do it step by step, writing down the results of each step and only at the end stating t
283.
▲
by
spion
4y ago
Used by: - OpenAPI/Swagger (1), which is the industry standard for REST API. Used by Kubernetes among others for resource descriptions - OpenRPC (json-rpc standard) - Most YAML based configuration files. GraphQL doesn't quite supe
284.
▲
by
spion
4y ago
Can we do projects that we know will stay at $0 but we still hope might gain traction? OSS: typed-graphql-builder https://typed-graphql-builder.spion.dev/ is a TypeScript based graphql query builder. No more writing untyped
285.
▲
by
spion
4y ago
This is a speculation based on a few longer chats I've had but I think ChatGPT does some text summarization (similar to the method used to name your chats) to fit more into the token window.
286.
▲
by
spion
4y ago
I understand your point. But discussing these issues in a public forum has an additional benefit in that it also raises general awareness that they're a problem. Also, it is an interesting question. Why do we keep seeing blog designs
287.
▲
by
spion
4y ago
I do that but I'm tired of chasing down the variety of places which cascade to the main text. With a little bit of search, looks like the reader mode extension does what I want (in fewer step)
288.
▲
by
spion
4y ago
Accessibility and usability issues can and should be reported. I'm not sure if the guideline applies in this case, as the issue has significant impact and the article author might want to be aware of it.
289.
▲
by
spion
4y ago
Observables didn't properly integrate with promises at the right time - if they did they'd be accepted way more easily (e.g. `.first()` returning a Promise rather than an observable or `using` accepting promise return values and&#
290.
▲
by
spion
4y ago
Why is this specific behavioral addiction recognized by the DSM-5?
291.
▲
by
spion
4y ago
Nice. `Promise.iterateSettled` would be cool.
292.
▲
by
spion
4y ago
Async iterables are bare-bones, and WHATWG Streams are not much better. I removed Dart from the comparison.
293.
▲
by
spion
4y ago
This is why we need proper, rich stream abstractions in JS that integrate well with promises. Promises by themselves are not enough. Note that a real world implementation of this would also limit the number of concurrent requests - another
294.
▲
by
spion
4y ago
This is not always in your control - especially if you're using libraries and frameworks. But also there are sometimes complex functions that (need to) combine lots complex data (say from multiple APIs) together to produce results, and
295.
▲
by
spion
4y ago
It can also be unit tests. You can take any function that has contracts defined and run a fuzzer (or a property testing generator) on its inputs, and its an isolated unit test. Or you could generate input actions for the entire system to ex
296.
▲
by
spion
4y ago
Most of the non-joyful experience of writing tests lies in the context preparation, not so much in the expected outputs. I think we need a modern version of design by contract instead. Its one of the most powerful techniques of testing soft
297.
▲
by
spion
4y ago
I can't second this strongly enough. You will be asked for SSO, SCIM and so on very quickly by any sizable business. Using a mature auth solution will save you a lot of work. (If on AWS, you might also want to look at AWS Cognito.
298.
▲
by
spion
4y ago
I have about 13 years of experience in the JS ecosystem which I think is long enough to formulate some decent theories :D > Oh, and the current LTS version is 18, so good luck with security. NodeJS 16 EOL is September 11th, 2023 - https
299.
▲
by
spion
4y ago
Compiling to JS doesn't solve the problem because the language (JS) isn't the problem. The problem is the browser and its inadequacy for building applications in many areas - lots of APIs that are not fit for purpose as well as si
300.
▲
by
spion
4y ago
I've found the greatest success with ChatGPT when I use it as a learning / exploration tool. If there is a topic I don't know much about, I can state the question in a fairly stupid way and ChatGPT will give me vocabulary opt
More ›