deno_std | sqlite | |
---|---|---|
17 | 5 | |
1,038 | 116 | |
- | - | |
0.0 | 10.0 | |
over 4 years ago | over 13 years ago | |
TypeScript | C | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
deno_std
- Ask HN: Where do I find good code to read?
-
[Showcase] My first project in Deno and an early perspective
For reference (for the issues you mentioned): 1. This issue was opened almost immediately to solve the weird .only function not working https://github.com/denoland/deno_std/issues/2979 2. That looks weird to me, will get back to you on this one since it should work I think 3. Generally polluting the global namespace isn't great, but because we're only polluting the namespace of a module (and we choose what parts to import), I personally find it quite freeing. I entirely understand how that might feel awkward. 4. you CAN specifying only writing to certain directories! --allow-write=/path/to/dir would allow that!
-
Deno v1.27
At least for the ones related to trees, it's just a renaming. Below is a link to the PR. When I initially implemented these trees, I chose the names BSTree and RBTree to keep the names short. I'm guessing the person that proposed renaming them did so to make it more obvious what they are.
https://github.com/denoland/deno_std/pull/2400
The standard library is separate from the runtime. It wouldn't break backward compatibility if you were to update. For example, if you were importing RBTree and upgraded Deno to the latest release, it would keep working just fine. You would only really need to switch to using RedBlackTree instead if there was a change made to it that you wanted.
I think the only time you would need to update your standard module imports to be able to use newer versions of the Deno runtime if the standard module were depending on runtime APIs that have a breaking change.
-
No Safe Efficient Ways to Do Three-Way String Comparisons in Go
It is like Demo deprecating fs.exists().[1]
[1]https://github.com/denoland/deno_std/discussions/2102
-
Programming language comparison by reimplementing the same transit data app
This was fun to read through.
I would need to profile the code, but the startup time being bad for Deno seems like maybe a combination of the code in here being unoptimized:
https://github.com/denoland/deno_std/blob/0ce558fec1a1beeda3...
(Ex. Lots of temporaries)
And usage of the readFileSync+TextDecoder API instead of readTextFile (which is also a docs issue since it's suggests the first one). It seems the code loads the 100MB into memory, then converts to another 100MB of utf8, then parses with that inefficient csv decoder. The rust and go versions look to be doing stream/incremental processing instead.
-
How do I check if a file doesn’t exist?
But it there's some talk to reconsider it
- JSWorld Conference 2022 Summary - 1 June 2022 - Part I
-
Testing frameworks
Sorry to hear that. I want to provide expect API in deno_std in the future: https://github.com/denoland/deno_std/issues/1779
-
Just migrated my first module from Node to Deno: Froebel - a strictly typed TypeScript utility library.
I just migrated the module to Deno and rewrote the test cases using the Deno test runner. Also contributed a bug fix to the test runner that I encountered during the migration. An npm version is still available and automatically generated from the Deno code via a small bash script (rewriting imports, adding an index.ts, etc.).
-
Deno.js in Production. Key Takeaways.
Much of Node.js is written in C, yet it's still called Node.js.
Deno has some JavaScript/TypeScript in it. On GitHub https://github.com/denoland/deno is 22.8% JavaScript and 13.2% TypeScript, and https://github.com/denoland/deno_std is 68.2% JavaScript and 31.6% TypeScript.
So to me it's misleading about the name, but not about what Deno is written in.
sqlite
-
Understanding SQL vs. NoSQL Databases: A Beginner's Guide
SQL (Structured Query Language) databases are relational databases. They organize data into tables with rows and columns, and they use SQL for querying and managing data. Examples include MySQL, PostgreSQL, and SQLite.
- Ask HN: Tips to get started on my own server
-
How to choose the right type of database
SQLite: A lightweight, self-contained SQL database, best for standalone applications, embedded systems, or small-scale applications not requiring a client/server DBMS.
-
NoSQL Postgres: Add MongoDB compatibility to your Supabase projects with FerretDB
FerretDB is an open source document database that adds MongoDB compatibility to other database backends, such as Postgres and SQLite. By using FerretDB, developers can access familiar MongoDB features and tools using the same syntax and commands for many of their use cases.
-
Ask HN: Where do I find good code to read?
Rust stdlib code is quite high quality although not particularly dense due to large amount of comments. Start from the docs, and click any source link: https://doc.rust-lang.org/std/vec/struct.Vec.html
Sqlite is supposedly high quality C code: https://github.com/smparkes/sqlite
For videos of someone (Casey Muratori) writing video game code and debugging it, Handmade Hero: https://handmadehero.org/
A blog post about how to write code by the same author: https://caseymuratori.com/blog_0015
For how to implement a fairly advanced type system, Typing Haskell in Haskell: https://gist.github.com/chrisdone/0075a16b32bfd4f62b7b
But, honestly, you're probably better off writing code yourself and learning by doing.
What are some alternatives?
fp-ts - Functional programming in TypeScript
Refactoring-Summary - Summary of "Refactoring: Improving the Design of Existing Code" by Martin Fowler
froebel - A strictly typed utility library.
clara-rules - Forward-chaining rules in Clojure(Script)
clean-code - Book review: A Handbook of Agile Software Craftsmanship
The-Simpsons-Hit-and-Run - Stolen (and slightly cleaned up) version of The Simpsons: Hit & Run original source code from 2003
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
pytudes - Python programs, usually short, of considerable difficulty, to perfect particular skills.
LavaMoat - tools for sandboxing your dependency graph
kakoune - mawww's experiment for a better code editor