Wow, JavaScript's new array.toSpliced() makes it super easy to move an element to a different location in an array with the others elements filling the vacant positions.
One feature I've always missed from all the databases I've used so far, is immutable columns.
Would be great to be able to specify that a field can only be set during creation but not after.
Does this exist in any main stream database?
Welcome to Vike's new company sponsor: https://t.co/kfrtGj3VYv.
I like such down-to-earth businesses and I'm glad Vike is providing them an architecture that is both rock-solid and flexible.
@chrisvanderloo Thank you - this makes a big difference 💚
This video explains it a bit better.
I think the fact that they're a NodeJS drop-in replacement that simplifies tooling and reduces CJS/ESM pain sounds good.
They should lead with that more. To me that's a much stronger argument for using it than "Bun is fast"
I'm not getting the recent hype about Bun tbh.
Yes, it seems like a cool project and the supposed speed is impressive. But wouldn't you rather use C, Go or Rust if performance was your main concern? And besides speed, what does bun do that Node or Deno don't do? #javascript
@rtfeldman I'm also using `tsup` at work and I think it's solves my problems the better than other tools I've tried (vite, parcel, etc). But I haven't been able to properly solve the jest thing as well.
Question I would ask is: Have you tried Jest transforms instead of building for jest?