Tbh how is the one concern not the Fact they use 'let'. Gross.
Fun fact: types, line numbers, and BS keywords like 'let' 'var' and * *&uint32, are only constructs of the language authors mind... a visualization of how he thinks. And are completely optional to a language (given a slightly more flexible parsercompiler)
There's lots of tests you can do. You can do each one multiple times And mix and match tests too.
Ebay. Put product on ebay and see if you get orders, cancel before auction ends, or after and apologise for being out of stock
Craigslist same thing
Fake sales site - write a "long copy" single page sales site and just have your buy now button email you a sale notice and display 'sorry not available yet'
Landing page/preorder site- super simple landing page with buy now btn, optionally fulfill the orders for sales
(or just collect emails for a Guage interest ) - Landing page email
google ads - buy 50 or so dollars of Google ads and see if you get clicks
Email campaign - sample email marketing ... same as goog ads
Bar test - agree to buy someone a beer in the bar if they try your app and give you feedback on it. Repeat 3-4x
Kickstarter- try for funding or preorders
Etsy/Shopify store and cancel orders ( etsy shopify has more natural traffic, so your not testing your marketing/adwords skills)
Most can be done for 25 bucks, in 30min. Do it again after you have an mvp if you want. also google idea validation
Fun fact, even though it's downloaded as compressed format, the windows drawing api bitblt requires bmp format, so it's probably saved in memory as bmp. A 1024x768x24bpp bmp is multiple megabytes, even though the jpeg is 100kb.
Not just the Windows drawing API, but essentially any drawing API requires that images be decompressed. Some sprite sheets are particularly egregious. I've seen sprite sheets with dozens of 32x32 sprites stacked above each other, and a single wide (let's say 1024x32) sprite at the bottom. This can give you a sprite sheet which is 1024x2048, decompressing to 8 MB, with literally 97% of the data being blank pixels. Fixing this on the browser side is very hard - it's a content problem.
The solution is to lay out sprite sheets to minimize blank space. Rearranging the sprites can easily get the number of blank pixels down to ~5-10%, thus saving ~7 MB, in essentially all browsers.
YEs, but images 2,336 x 3,504 = 8,185,344 pixels @ 24bit color roughly equals to 24MB. That is lots of images even if you are on native resolution retina display. And doubling that gives you 48MB only. ( And someone has pointed out they are compressed differently within memory, so likely only consuming 1/2 to 1/3 memory size )
That leaves with 200MB memory gods knows what they are.
I could use another brogrammer to verify some of what I'm seeing. I expected I could just mention this to a researcher and be done, but I'm being attacked for mentioning possibilities.
There was a catalyst in 1975 when vaxx rates doubled and kept doubling every 5 years, the graphs reflect that, imho. Other countries data should confirm or deny.
Goto considered harmful
Jquery .show ()/.hide () is now biggest performance drain in some SPAS
Node callbacks now harmful, async/await or promises could be next... possibly
React is so slow it cannot render > 10 fps for some SPA
Fun fact: types, line numbers, and BS keywords like 'let' 'var' and * *&uint32, are only constructs of the language authors mind... a visualization of how he thinks. And are completely optional to a language (given a slightly more flexible parsercompiler)