kwhinnery

5 ms·

1.
SDK code mode shows SotA accuracy for operating APIs via MCP(stainless.com)
5 points by kwhinnery 7mo ago|0 comments
2.
Stainless Docs Early Access(stainless.com)
15 points by kwhinnery 11mo ago|1 comments
3.
by kwhinnery 11mo ago
Hey all! Kevin from Stainless here to answer any questions you have. tl;dr overview of what we built: - SDK, REST, and narrative docs in one - Lots of nice docs features and UI components out-of-the-box - Built on Astro, so you can hack any
4.
Sentry AI Autofix(techcrunch.com)
5 points by kwhinnery 2y ago|0 comments
5.
by kwhinnery 3y ago
Looks awesome, will keep this in mind - every so often you need to create complex documents in code, and it's always a pain. Doing it with a familiar modern programming interface would be nice.
6.
by kwhinnery 3y ago
In terms of "when you would use it" - it doesn't necessarily solve a different problem than npm. I think it arguably solves the same problem more effectively (though it is certainly early days and npm still does a lot of thin
7.
by kwhinnery 3y ago
HTTPS imports will continue to work and be supported in Deno. However, as we observed their usage in the wild, a couple problems became clear: 1.) Duplicated dependencies - projects would often download multiple versions of the same depende
8.
by kwhinnery 3y ago
Thankfully JSR won't be capable of a left-pad situation where packages can be unpublished - published packages are immutable[1]. As for the potential for disagreements over whether or not a scope should be transferred, that is a big re
9.
by kwhinnery 3y ago
The new scope owner would be able to update "@cocacola/foo" and publish new versions (previous versions would be unaffected).
10.
by kwhinnery 3y ago
This is probably a marketing bug on our part. While we did want to design for TypeScript from the outset, you can definitely happily write and publish plain JavaScript code on JSR. We probably need to do a better job explaining and featurin
11.
by kwhinnery 3y ago
I think this is mostly right - "superset" in that JSR modules can depend on npm modules, and projects using npm can use the npm registry and JSR together. The bottom line we'd want to communicate is that JSR is additive to np
12.
by kwhinnery 3y ago
That does get to be a mouthful! But if you wanted, you can of course do: yarn global add jsr so that subsequent installs could just be: jsr add @oak/oak
13.
by kwhinnery 3y ago
We do intend to take a more editorial approach to scopes, and assign scopes to users in a way we think is more intuitive for end users of JSR. We have reserved some obvious scope names already, but in the future, we'd likely entertain
14.
by kwhinnery 3y ago
Not yet, but esm.sh mentions they have experimental support now to check out: https://twitter.com/jexia_/status/1762516242626416750
15.
by kwhinnery 3y ago
As JSR develops, you can expect to see more features like those of dnt start to show up in the npm compatibility layer. We've also been exploring how to create a good DX around simultaneously publishing JSR modules to npm, so publisher
16.
by kwhinnery 3y ago
Kevin from the Deno team here - happy to answer any questions you have today!
17.
by kwhinnery 3y ago
I know it's hard to know this since not everyone has access to JSR yet - but it's incorrect to say that adopting JSR (as a module author or consumer) will result in breaking changes. JSR is additive to npm, and can be used alongsi
18.
by kwhinnery 3y ago
Hi there - Kevin from the Deno team here. Thanks for starting this conversation - the recent reduction in regions is part of an ongoing effort to drive down the cost of the platform for customers. We are still learning and iterating as we f
19.
by kwhinnery 3y ago
I think the ecosystem is inching in this direction. There are already some interesting PoCs out there using Tauri (Rust based) and the deno_core Rust crate.
20.
by kwhinnery 3y ago
The usage of the word "ideal" in the 2021 post was probably not ideal :) The accessibility and diverse ecosystem of JavaScript, owing to its status as the lingua franca of software development, would probably be the basis for it b
21.
by kwhinnery 3y ago
User-level access control (like ACLs for authenticated users) or something else? Feel free to share longer form thoughts here and I can make sure we keep this concern in mind.
22.
by kwhinnery 3y ago
ngl this is a little cursed, but awesome
23.
by kwhinnery 3y ago
Just jumping in here to applaud the usage of "luddite numpties" in a sentence.
24.
by kwhinnery 3y ago
I was surprised by the quality of the results from Claude, I hadn't used it until recently. I asked it for strategic advice about playing a game of Magic: The Gathering and it gave what felt like pretty nuanced advice (talked about &qu
25.
Show HN: LLM Playground, compare results side by side(retool.com)
14 points by kwhinnery 3y ago|4 comments
26.
React or Retool?(retool.com)
2 points by kwhinnery 3y ago|0 comments
27.
by kwhinnery 3y ago
Sorry to hear this has been challenging - were you trying to do something like this, where you select a row in the table, and then make another API request with data from that row? https://retoolhacks.retool.com/embedded&#x2
28.
by kwhinnery 3y ago
Absolutely agree, and something we were discussing today as it happens on the docs crew. We have some ideas we'll try in the next few months to bring more docs directly into the product, and beef up coverage and examples in the compone
29.
by kwhinnery 3y ago
Hey there! We are actually working on a video course for Retool that covers more of the breadth of the platform. Definitely more to come. One more substantial example we released recently is this bookstore application, which uses about ever
30.
by kwhinnery 4y ago
It's true that a lot of adjacent tools in this space are built for non-developers. But if you try Retool, I think you'll notice that it's definitely not "no code" - any interesting application will require a signifi

More ›