17+ years in engineering (staff/principal) with 17+ years in JavaScript, Node since Ryan Dahl was working on it, React before it had a major version. Check resume for full list, which includes using lots of TypeScript, .Net, minor Elm, minor Ruby, minor Python, minor Elixir) with interest and willing to learn other languages like Rust.
17+ years in engineering (staff/principal) with 17+ years in JavaScript, Node since Ryan Dahl was working on it, React before it had a major version. Check resume for full list, which includes using lots of TypeScript, .Net, minor Elm, minor Ruby, minor Python, minor Elixir) with interest and willing to learn other languages like Rust.
This is my first time using it and I've been very pleased with it so far. It keeps it simple, has solid typing & schema building, and reminds me of LINQ. I'm also a thin models kind of person and the fact this is just an object without needing to build ORM classes is even better.
Thanks for the insight, I greatly appreciate it! This definitely is a reasonable idea for many things and I'm looking forward to seeing something similar to the sharding mechanism in the future.
I've only started to think about this and I'm thinking the hardest part will be dealing with cross-cutting concerns (in a non-auto sharded world manually creating multiple database) and trying to find a way to keep each database isolated without extra burden compared to using a hosted Postgres.
As an aside, that lan optimized house was a gaming dream. Hope your new house is as awesome.
The costs as a whole has me worried. I'm not sure it'll be better than just using https://turso.tech/pricing as that is already a free tier of 8GB and it might cost less overall the paid tier.
Is it a non-goal to be long term usable for larger databases? That would force the usage of something like turso your closest direct comparison as a possible migration strategy or relying on "Smart Placement" (which from my point of view reduces the benefit of global edge) for other serverless non-global dbs.
Willing to relocate: If you make selling my house painless perhaps or pay enough to justify it
Technologies: 15+ years in engineering with 15+ years in JavaScript, Node since Ryan Dahl was working on it, React before it had a major version. Check resume for full list (includes using lots of TypeScript, .Net, minor Elm, minor Ruby, minor Python, minor Elixir) with interest and willing to learn other languages like Rust.
Resume/CV: JS for my linkedin atob('aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL2dyZWctY2FuLXRoaW5rLw==')
Email: JS for my email atob('Z3JlZ29yeXdheG1hbitobkBnbWFpbC5jb20=')
I'm currently a Staff Engineer who has and can work the entire stack (architected most of the current frontend I work on, write APIs, can work with databases, have created CI pipelines, etc.), but I've been wanting to become some form of Engineering Manager. I've found mentoring and helping others extremely rewarding and I've been told my passion about technology inspires others. I'd be interested in a purely IC job only at a place that really proves it is worth changing from my current company and job. I'm more interested in either a pure manager position or a "50/50 position (the 50/50 cannot be a paid for one job, doing two jobs 100% & 100%).
Clean room design is about wholesale copying of code. If you copied the APIs and architecture and wrote the code differently there would be nothing wrong as SCOTUS just ruled.
Willing to relocate: If you make selling my house painless perhaps or pay enough to justify it
Technologies: 13+ years in JavaScript, Node, React, check resume for full list (includes using TypeScript, .Net, Elm, Ruby, Python, Elixir) with strong interest in FP and other languages like Rust
I'm not here to agree with the who you responded to, but Google smuggling unblockable ads does 100% harm Brave. If part of Brave's selling point is the built-in ad blocking and in a hypothetical dystopian scenario the web were overrun with unblockable ads from WebBundles Brave would inevitably be harmed to some degree. I say that as someone who runs Brave on my phone primarily. I know I'd probably switch browsers if one of the primary reasons to use it were largely killed off.
People used to look at me like I was crazy when I told them that React is nice, but you can actually write faster code with alternative methodologies. It seems like other engineers are coming around to this and creating these faster alternatives.
React made writing frontends generally better, but often slower and as rich_harris points out that it entails a lot of developer work to build and use optimizations to speed it up.
But that's what languages that compile to JavaScript support already today. The binary JS shouldn't prevent this behaviour if it is just a binary representation of a text version.
Sure, why not? The difference is that WASM is aiming for near native performance of code, while the binary JS would still be limited to JS performance.
Remote: Yes (only)
Willing to relocate: If you make selling my house painless perhaps or pay enough to justify it
Technologies: JavaScript, Node, TypeScript, React, Solid, Bun, AWS, CI/CD
Resume/CV: https://akkuma.github.io/resume
Email: JS for my email atob('Z3JlZ29yeXdheG1hbitobkBnbWFpbC5jb20=')
My personal site: https://akkuma.github.io
17+ years in engineering (staff/principal) with 17+ years in JavaScript, Node since Ryan Dahl was working on it, React before it had a major version. Check resume for full list, which includes using lots of TypeScript, .Net, minor Elm, minor Ruby, minor Python, minor Elixir) with interest and willing to learn other languages like Rust.