flatbush
phero
Our great sponsors
flatbush | phero | |
---|---|---|
5 | 21 | |
1,374 | 311 | |
- | 1.0% | |
0.0 | 6.5 | |
3 months ago | 3 months ago | |
JavaScript | TypeScript | |
ISC License | Apache License 2.0 |
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.
flatbush
-
Databases are the endgame for data-oriented design
> (There are ECS frameworks in JavaScript, which gives you absolutely no control over memory layout and thus completely defeats one of the primary purposes of the pattern.)
While JS does not provide great support for bit packing complex structs, typed arrays give you quite a bit of control over memory layout for simple numeric types, which is what you usually want for optimal data-oriented code anyway. This is a common technique used in fast JS libs for data visualization, ie:
https://github.com/mourner/flatbush
There are also basic operators required for bitarrays, which are useful for ECS and memory-efficient code generally.
-
React Virtualisation from scratch
using flatbush library instead of rbush which optimise the statically placed element, from the benchmark in the repository it could boost up to 5x the performance of rbush.
-
Load GeoHash data in RAM for querying for Proximity Searches
But for 500 k points, it's not many. I'd put it in the database tech I was using and hit an API for it. Or like you say, load it into memory and use Mourner's flatbush for a super simple and super fast solution..
- Flatbush: A fast static spatial index for 2D points and rectangles in JavaScript
-
Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
> At pbf speeds, decoding is usually no longer a bottleneck, but bandwidth might be when comparing with gzipped JSON.
we were streaming a few hundred datapoints in a dozen flat arrays over websocket at 20-40hz and needed to decode the payload eagerly. plain JSON was a multi-factor speedup over pbf for this case. but it's fully possible i was holding it wrong, too!
even if your "bottleneck" is rendering/rasterization (10ms), but your data pipe takes 5ms instead of 1ms, it's a real effect on framerate, battery, thermals, etc.
i'm a big fan of your work! while i have you here, would you mind reviewing this sometime soon? ;)
https://github.com/mourner/flatbush/pull/44
phero
-
Node.js 20 is now available
That's one of the reasons that drove me to create Phero: https://phero.dev
-
Full-Stack TypeScript with tRPC and React
Iโm one of the authors of Phero. Itโs goal is similar to tRPC: fullstack typesafety between servers and clients.
One difference is syntax: Phero leverages the TS compiler api to generate parsers for your backend functions. It will parse input and output or your api, automatically, based on the types you define for your functions. It will generate a declaration file of your api and generate an RPC style client SDK for your frontend. Another difference is that it aims to be more batteries includes.
[1] https://github.com/phero-hq/phero
Comparison: https://phero.dev/docs/comparisons/tRPC
- Framework for REST API that builds a complete-ish API given a model?
-
Using API routes for large projects
Shameless plug: you could also use https://phero.dev
-
No errors when fetched data is a 'string' even though interface property type should be a number.
Long story short: when fetching data, you should be validating the data, before casting it to a type youโre expecting it to be. There are a lot of different approaches for this, but being the go-author my favorite would be Phero (https://phero.dev). With this, you can build your API in typescript as well, automatically generate a client for your frontend to call the API. Phero will make sure all data is correct in runtime, automatically.
-
Best schema validator for intellisense performance?
For those looking for an alternative: Definitely check out https://phero.dev. As the co-creator Iโm totally biased of course, but thanks to its build-step IDE-performance is great ๐๐
-
I've made a big comparison table of nodejs RPC frameworks. Hope you like it ;)
What about Phero? https://phero.dev
- How you make typesafe front/backend API
-
KitaJs Survey - No runtime code, fast as bare metal and top level framework.
Can we add Phero to the list? :) https://github.com/phero-hq/phero
-
If you haven't worked with TypeScript yet it's a good time to get started now. I prepared an intro that covers the most important points to React with TS. Including a few embedded exercises for you to practice.
You can use Phero. You can use it on your backend and frontend. It basically created a typed API from your backend afaik
What are some alternatives?
virtualised-whiteboard
protoc-gen-validate - Protocol Buffer Validation - Being replaced by github.com/bufbuild/protovalidate
liwords - A site that allows people to play a crossword board game against each other
telefunc - Remote Functions. Instead of API.
withtyped - ๐คน Type-safe RESTful framework for fullstack with all native implementation.
react-virtualized - React components for efficiently rendering large lists and tabular data
bash - Unofficial mirror of bash repository. Updated daily.
ts-proto - An idiomatic protobuf generator for TypeScript
jest-extended - Additional Jest matchers ๐๐ช
rbush - RBush โ a high-performance JavaScript R-tree-based 2D spatial index for points and rectangles
garph - Fullstack GraphQL Framework for TypeScript