To me it wasn't the time commitment, it was the deception. Felt like a sweepstakes eventually because they are not upfront, and you give very private information. They know what's up with how it was designed and marketed (headline) and if they don't I humerously question whether they should be doling out AI grants.
Personally my views are you have a right to ask for whatever you want. Don't lie about it and call it a 'grant in minutes'. Sure there is 525,600 minutes in a year. That many?!! Spell out everything you want upfront. This is a dark design pattern and it's unethical and especially coming from you all you should know better. With sensitive information don't lead people on.
I didn't care why, I cared because it was decietful. Eventually by the time they wanted an additional '20 minutes' AFTER already doing a ten question spatial awareness test I quit. Could go on forever. Very private stuff too. To not be upfront with things like that is wrong.
Pls consider changing the 'grant in minutes'. I am busy so I read the headline and jumped right to the page URL. It said nothing of the substantial requirements and commitments both data and time. That should be spelled out up front. This felt very un-comfortable, to keep being asked for more. If nothing else, spell out what you want upfront.
- Application form
- 100 question personality test
- 10 question spatial test prelim
- 20 min spatial test
- who knows
Entirely depends on what you're building. If it's crazy complex go native now. Super complex web apps are as the rarest of the rare, and damn near impossible. Like a handful ever, rare. That's not to be said that it cannot be done. If it's medium to basic, use a framework like Vue or Preact and a VDOM. Everything will stem from that. Node.JS is a given, maybe Go, but all other decisions depend on what you are building.
Thank you for your contributions and writing this. Just spent a week of development time 'fixing' Nomination reverse geo-code issues and creating a pay for RGC backup because we exceeded the 1per sec max and had NO idea when it would turn back on. To boot, no help whatsoever determining why when we used it successfully for over a year. All of a sudden NOPE, we're cut off with foggy reasoning and no explanation of why or when we'll be back up. I've spent several months on maps. All of them. I know them through and through. I could sleep speak API docs and pricing for mapping services. We need OSM. OSM needs many of these 'fixes'. ASAP. No idea who was running things there. You gotta work on your analogies ;), but yeah if a user doesn't know how much the total usage is and can only use a percentage of that unknown total, it's ridiculous. Let's get a premium account going at resonable rates. Same for reverse geocode. No more than a 1ps max. Ok so what if we have a surge. Error 3. Give me a break. And so brashly the docs state this almost warning deterring any user from ever wanting to integrate because there is a big ol' flag saying 'we DO NOT want to scale with you!' At a bare minimum how about you average per second rates over a 10min aggregate. Soooo much room for overhaul and improvement here. This is a big start. Number one on HN! Let's fix/upgrade the antiquated OSM tech, logic and direction. It's a new world and the world needs OSM.
Facebook exceeded all of our goodwill and patience as consumers as almost no other company ever has. Deceit is their goto. After all, Zuckerberg (while young at the time) did call his own users 'dumb fucks' if I recall when asked why they share things with Facebook. That says everything you need to know. I will also mention I have heard this same narrative for the past 7 years.
I'd like to see pro and cons for all the lower 'smaller' frameworks and methods. Maybe we can contribute? I have used many of them. Seems like the ones with pros and cons, React, Vue, Angular etc everyone already knows. I think there is opportunity here to give more depth to lesser known frameworks. The top 5 are pretty well discussed at this point.
Wire size. Your projects specific needs. Built out time (i.e making your own components). DOM requirements. Licensing. Community. etc. This is an enormous list of variables to determine. If you were not making a complex site or SPA, learning and using React could be huge overkill even though it could still get the job done. The best way to determine what framework or language to use, for me has always been to assemble my tree of needs first. That included things like, how complex are we talking here. Do we need state management? Do we do most of our rendering server side? Do I have to learn the framework? Are the docs good? Etc. Build a map of our own needs first, then spend a few hrs holding it up to the various options.
Please add pricing. And tip; to get startup founders, don't subscribe to the silly moniker that startup's price themselves too low. I look at the low, mid and high end price by volume to estimate any new costs now and 6 months down the line. Way too many overpriced services cause it's in vogue right now based on VC's saying it is. Certainly what you are doing is interesting. Nice work.
Very well put together. PR can also depend on a lot of other things, like news cycle, poliTECHal climate, season and the aurora borealis factor (a vast trove of other unknown influences). I think getting out there often meeting people and being happy with what you do, can help open untold doors.