We don't know if it's Gandalf. It's only speculation. He mimics Gandalf-isms from the movies (cupping a bug and talking to it), and generally looks like him. It could easily be misdirection for someone else like Sauron or maybe even a blue wizard?
I'm talking about running week or month long tests with control and multi test cells containing new functionality, configuration, or code to determine the viability of a single or combination of changes by analyzing statistical output driven by p-value and pre-determined target metrics.
These types of experiments are extremely valuable in uncovering hard-to-find bugs, assuming you have sufficient logging and confidence around your metrics. They let you know a problem exists and roughly where it is in the product. From there you can drill down and investigate your source code until the discrepancy is found.
Have to disagree. I've found plenty of issues that affect real production users through the use of AB testing. Problems that were small enough to escape review, testing, and reporting, but large enough to be stat-sig. They always lead to a bug, or issue with test vs control.
I will always use AB testing for uncertain code in the future. I was skeptical when I first started writing AB tests, but they have proven their worth over and over again.
Our product is used by all sorts of devices and resources. Many use it on super old hardware in different countries. 32kb isn't much, but when you're analyzing Time To Render metrics, you might be surprised how little is necessary to move the needle.
That said I don't expect a massive impact from this change, but removing unused code is going in the right direction.
We found it to be about 32kb gzip+minified in our builds. I just dropped it from one of our apps, where it wasn't even used except in a legacy logging module. We replaced the ajax call with XHR. The other app we maintain has it as well, again only for the ajax method.
While it may be nice, for large production apps we'll take the filesize gains where we can find them.
Totally agreed for mobile websites, with the exception for PWAs and mobile sites that rely on specific view ports being unchanged, like games for instance.
With no scrollbars it's hard to tell if something is zoomed in or not and you might be missing parts of the UI without noticing. Native apps don't zoom and neither should mobile sites pretending to be apps. Build accessibility into the UI.
Do you think Douglass Crockford didn't know that? He was being cheeky and doesn't care. This was also a huge pain point for JSHint and a lot of work went into undoing that by finding a single commit that didn't have the clause iirc.
Wearing a Pebble Time right now. Works and looks great, but not 100% even with Rebble. Shame the company failed, the product was perfect for Android users.
Open to how you'd solve it. Fill up the overfilled jails and hospitals? Can't force people unless it's a 5150. You literally cannot stop what is happening without going full militarized police and how is that better?
Best thing you can do as a tourist is know where you are. It's no different than unsafe areas of Mexico and LA? You gonna stay near skid row?
SF weather and wealth is going to attract homeless and drugs, and unless you want to break the law to stop it, adapting is the next best thing.
Actually NVM it's just easier to shit on SF and act like everyone there is an idiot and the solution is simple.
Maybe you didn't venture out much, but you should realize that is _mostly_ exclusive to market street. One street of a thousand. Yes it occasionally happens elsewhere like any city, but Market and especially the tenderloin are infamous for the drug use and depravity.
Why people keep staying there instead of the hundreds of other and safer hotel locations? Maybe hotels need better regulated ratings to take into account the surrounding area.
Good features for the price, decent pickup speed, gears are smooth, heated leather seats, interesting features like headlight wipers and night panel. Fun to drive and look great.
They are quirky and aesthetically distinguishing, especially all the orange and green.
Love my '95 Saab 900 SE turbo and will most likely never part with it if I can avoid it.
This is a virtual domain implementation, like React, not interacting with the actual DOM like the demo in the OP. WASM is awesome, but seems like folks don't really understand it and the limitations.
I bet DOM access in WASM is totally doable, just gonna be a lot harder than how this project implemented it.
Hi floodfx, we should chat at some point if you're on slack/discord/etc. I'm building something extremely similar and there's potential opportunity to share some code/learnings. Personally I feel this design paradigm is the real web 3.0.
My project is https://diffhtml.org/ and I have started experimenting with middleware to bridge to server and client workers: https://github.com/tbranyen/diffhtml/pull/251. For the server worker, it uses a WebSocket to ferry the VDOM diff patches, custom events, and property access/function calls. A big goal is to allow synchronous "main thread" access from workers, including on the server-side. This would allow you to write your UI code as if you were a client side app. It does this the same way as partytown using a SharedArrayBuffer and Atomics. You can see demo source code here: https://gist.github.com/tbranyen/2f5be81cfb7b3aa1bb443c8ef13....
I've also toyed around with hot reloading components without the need for a pre-processor like Babel, and the results are hugely promising. Stateful live UI updates from saving a component file to seeing in the browser without all the fuss with complex build steps is liberating.
I'm probably a few months out from having a usable beta, but I'm going to follow your project closely. Thanks for sharing!
2) Been to plenty of restaraunts that tout house-made ketchup. Sure Heinz has natural recipe variations out now, but the dijon of ketchup would be small batch sourced from garden fresh tomatoes and high end vinegar.
I've seen plenty of brands in specialty markets that are more expensive than Heinz for that reason.
Definitely, HTML has several tags to help work with external types. You can interface with java, vbscript, flash, pdf, etc. You could absolutely expose top level methods and invoke them in JS.
That makes no sense. Roku was born out of Netflix. Why would they buy them now after making the decision years ago not to entire the consumer hardware market?