I’ve used Jupyter notebooks with deno decently. They seem much better than Python Jupyter notebooks because of the lack of pain around dependency management.
Deno in 2023
141–150 of 235 posts
Re: Deno in 2023
#142Earlier quoted context omitted.
JSR = JavaScript Registry (from the site). It seems fairly clear this is a package registry, i.e. an NPM alternative.
But they promoted they will not need one at any time, to extent they will never build one. There was only deno.land as a point to discover libraries or what community builds.
Yep, but it seems they learned something from the experience?
Hopefully it will be closer to how Go does it.
Re: Deno in 2023
#143I’ve used Jupyter notebooks with deno decently. They seem much better than Python Jupyter notebooks because of the lack of pain around dependency management.
Do you have a guide / link for more info about this ?
Re: Deno in 2023
#144I'd love to use Fresh but a framework for web development which calls itself v1.x and yet only supports Tailwind for styling purposes feels very immature. The fact that for the next iteration they are prioritizing view transitions and not CSS bundling is baffling.
Personally I'm happy with modern CSS using variables and nesting natively. The bundling step isn't necessary for the vast majority of usecase IMO.
Re: Deno in 2023
#145Earlier quoted context omitted.
sure but is that a bad thing? this regions probably see next to or zero use and cutting them frees up money to be used on other things.
They’re operating like a startup, which like you say should be perfectly fine. Can’t pretend like a giant when you don’t have the bank account for that. Though they’re also selling a developer ecosystem. A lock-in. Are you willing to bet your company’s own software tools on a vendor that could go bankrupt from their other (hosting) business? The question is if Deno hosting dies, will Deno as a platform still thrive?
I'm just writing hobbyist software, but I'm not too worried. My backup plan is to put my Deno app in a Docker file and deploy it somewhere.
(It's a bit trickier than that since the SQLite database holding the KV store would need to be backed up, but it seems doable with Litestream?)
Re: Deno in 2023
#146Is anyone a user of Deno KV? What's your experience been like?
I've been using it to build a dynamic blog/newsletter. Local DX with https://github.com/kitsonk/kview has been nice.
Re: Deno in 2023
#147I'm interrested in the WebGPU feature. With Slint [1] we're working on a framework which allow to make a desktop GUI in Javascript/Typescript, without bringing a browser/webview. Currently, we do it by using binaries through napi-rs so we can bring in a window using the platform native API. And then we do some hack to merge the event loops. But if Deno supports bringing up a window directly, this means we can just sh…
Have you talked to the Dioxus people recently? They're working on a project called Dioxus Blitz ; from what I'm told, they're trying to implement a minimal browser target, that provides some basic DOM-like features and renders with wgpu. It's not exactly what you're hoping for, but you might find common ground. https://github.com/DioxusLabs/blitz (Also, the Linebender project is working on Masonry, with FFI as a medi…
Our v2 of blitz is using firefox itself to resolve CSS and google's advanced WGPU renderer for high-speed text and vector graphics.
Re: Deno in 2023
#148I'm interrested in the WebGPU feature. With Slint [1] we're working on a framework which allow to make a desktop GUI in Javascript/Typescript, without bringing a browser/webview. Currently, we do it by using binaries through napi-rs so we can bring in a window using the platform native API. And then we do some hack to merge the event loops. But if Deno supports bringing up a window directly, this means we can just sh…
I totally get the idea of bringing JS into new environments because it is so ubiquitous. On the other hand, I hate the language and wish we could replace it in the browser, the opposite direction. I'd be much happier with ClojureScript or PureScript or something being the standard with the ecosystem to go with it.
So use WASM with the language of your choice and best of luck to you with that.
Re: Deno in 2023
#149Earlier quoted context omitted.
I'm not sure what your requirements are, but I've had a good amount of success with converting Node.js libraries to native libraries by embedding a CommonJS module into the binary, then running the actual code through QuickJS. Much smaller binaries. If you really are pressed for space, you could use upx, or store 7z compressed code and embed the 7z library to decompress before passing it along to QuickJS. Here's a pr…
Isn't QuickJS order(s) of magnitude slower than V8? That doesn't seem like a practical tradeoff to make outside of embedded.
Depends on what you are doing and what your needs are .. the gp comment was about the size.
Re: Deno in 2023
#150Is anyone a user of Deno KV? What's your experience been like?
Haven't deployed it yet, but the API seems decent when doing local development.
It's a bit low-level compared to a SQL database; you're building your own indexes and need to write transactions to update them atomically along with the main record. (But it does have transactions, so it's reasonable.) It reminds me of App Engine datastore, back in the day.
There are some fairly tight limits. (64k for records.) I wouldn't use it for storing images or larger files.
Not sure what I'm going to do for full-text search. But I've built simple search engines from scratch before.