> HTTP also allows the DuckDB-Wasm distribution to speak Quack natively! So DuckDB running in a browser can e.g., directly connect to a DuckDB instance running in an EC2 server using Quack.
Although a maintainer answered you, watch the video from the blog. There's a WASM demo at the end, which is great. It also has a good explainer for those confused about the HTTP decision.
And I appreciate that the Hannes still appreciates the magic of the WASM. [And I keep hearing quark which makes me hungry for tangy creamy German yogurt]
Might have been mentioned here, but feed the comments into an AI and get it to prioritise and help implement the top feedback. Also use other AI tools like Claude, Cursor or Windsurf. Beyond that, take the points down at the same time as the red flash and make them flash too, animate the attack and it wasn't clear how I could power up the better weapons.
Great question! Being totally honest, the core idea was basically something along the lines of "What would you get if Unreal Engine Blueprints and Node Red (NR) had a baby, and then you made it available as a $5 SaaS app".
IMO it's a lot easier to use than NR (I've played around with NR quite a bit), which is the biggest difference in my opinion. Obviously you don't have to host it, which is a big plus. But the interface is also just a lot more user-friendly and intuitive.
Passing data from one node to another in NR is not super intuitive, and you can't easily visualise data flow coming from multiple sources and then converging into a single node.
As far as I'm aware, NR also doesn't have any kind of Type system - Types in G-Script help to lower the learning curve because it's a bit like building a PC... if the cable fits in the port, there's a pretty good chance it will atleast work and not explode.
NR does support "code reuse" too, but again it's just not super intuitive and user-friendly. To be clear, there's nothing G-Script does that hasn't been done before, but IMO it's packages in a very user-friendly format and priced very competitively.
I'm looking to add super simple Auth, Testing, and Data Persistence over the next few weeks, which I think will accentuate that usability gap even more.
Not sure how it all works, but I assume it's broken down for a purchase on something like Coinbase card - eg. they bundle a load of card transactions into a ETH to fiat conversion for Visa
Considering Typescript is a superset of javascript & the future of javascript - ie. they always plan to be implementing future javascript 'now', that is their whole reason for existence, and that their team sits on the javascript committee, then yes, I think it is around for the long haul.
https://www.techtalko.com/2018/03/17/typescript-the-future-o...
This is a tired argument. SCSS was supposed to take over CSS... still waiting. For a hot minute, CoffeeScript was supposed to take over javascript. In the end, CoffeeScript didn't have a chance, but at the time many thought it did.
Typescript may be different and may be better, but there is a lot of rightly justified hesitation to adopting it.
As far as i know this was really never aim of the project. But everybody uses it. I would even say it oppened doors for JS compilation.. because everybody already has build process for css so why not js.
