this is definitely not true - there's a huge depth of complexity in these multi-dimensional databases. It's relatively easy to make a proof of concept - it's "just" an array of arrays after all, but building something production quality is a multi-year endeavour
hmm, sounds like it, please could you open a github issue with some more info?
edit: I've just fixed an issue that looks similar to this, please run with `npx [email protected] ./path/to/folder` and let me know if you're still having problems
Cool. That was it. Works now. Hats of to you. This has more uses than just typescripting. Actually you can spot in React apps, probably in other apps, too, the dependencies which break your code splitting.
I just want to say that this looks fantastic, especially the runtime types stuff - the idea that types are values hasn't caught on yet but it's great to see movement in this area. A long time ago I did something very similar to this for Flow (https://gajus.github.io/flow-runtime/#/try) but typescript is a much more suitable target. Congratulations on an amazing job, I really hope you have plans to sustain this project for a long time, because it's very ambitious but very compelling.
Great to see a new option in the TypeScript ecosystem. A fully featured framework. Brilliant. Could be a great alternative to Adonis.js which is one of my favourite nowadays: https://adonisjs.com/
TypeScript's type system can be very powerful and flexible - creating types at build time in a manner of speaking. Here's an article I wrote on an aspect of this called mapped types. You can see how types can be composed of other types.
To make this work there would need to be a big social push towards eating in line with the seasons again (which was obviously the norm for 99.99% of the history of humanity). I think this might be a hard sell, people are now very used to being able to buy whatever they want whenever they want, e.g. strawberries in january
Seasonal eating of farm-fresh foods would certainly make free public healthcare a more reasonable proposal in the US. It would surely cut into the bottom line of the pharma industry
(I didn't know of this company's existence until their non-existence today)
I don't think the idea is really that bad, and a form-filling browser extension would not be comparable to what they were trying to do here. The idea is pretty compelling in isolation - your random mom n pop ecommerce site can compete with Amazon on price for a lot of things, but it can't compete with convenience.
If I go to Amazon I can buy something with one or two clicks and be pretty certain that my card details aren't going to get stolen and the thing I ordered will probably arrive when they say it will just about.
If I go to a random ecommerce site I probably have to register, have to enter my card details and confront the possibility of getting ripped off. It's so much less convenient, so for most purchases I just go to Amazon, which is bad for a bunch of reasons.
What Fast was promising to do was to bring that convenience and trust to ecommerce sites, so that they could become more competitive with the Amazons of this world, get more sales, make more money, consumers save money, everyone wins.
Of course the problem is that they're only compelling when they're ubiquitous, and when everyone already has an account and everyone already trusts them. It's a bootstrapping problem, one that only really works if you burn a whole bunch of capital to get both consumers and suppliers signed up, or if you can piggyback off someone else's market penetration, e.g. Stripe, and even with that leg-up they weren't able to survive. All of this also ignores the existence of paypal, apple pay, google pay etc which do offer most of the convenience already.
I agree that the idea is good, but I feel like it can be achieved just fine with a local-only form-filler, if it isn't already (all browsers and password managers now offer to save credit cards, and Apple & Google Pay even handle actual payment processing with better fraud protection).
The bootstrapping problem seems like something of their own doing, both because it's a server-side solution as opposed to client-side, but also because there's most likely rent-seeking and extra fees involved. Every merchant wants to make more money so they should've had near-complete coverage very quickly unless there's a significant downside for the merchant for participating in said system.
Approximately 0% of consumers install browser extensions, it's a non-starter and also a totally different proposition. Every merchant wants more money but no one wants to mess up their payment flow, no one reasonable wants to add yet another option, yet another decision when it comes to the most critical part of their sales process - the thing that actually gets them paid. Fast's only shot was with merchants who already did a lot of sales via Stripe and they'd have to make integration utterly frictionless.
My face when I realized that a combover, power tie, fake tan, and trophy wife is really all it takes to sell a median person on it (oh, and millions of dollars).
I'm surprised too (or was in the past). Nice looking clothes and saying that one's work is going great, wow. I didn't try this but I know others who do
