It’s the most useful way to abstract things. With digital computers, we’re used to thinking of hardware and software separately. Thinking about this some more, another aspect of the brain that I find fascinating is the low-level language used to transmit and store data. ? This is follow-up to what I wrote in edition #197 about how our brains perceive 3D space visually and are able to mesh complex data and compress all that info into just a “feeling” that we have that something is close or far, big or small. I already have a couple carbon monoxide (CO) detectors because we have a gas furnace, but this would be more about air quality than safety.Īfter a quick look, I found a few on Amazon that aren’t too expensive, but I wonder if consumer-grade models are sensitive enough to be used to optimize/modulate airflow somewhere (like my office), or if they’re more about warning you of very abnormal situations, but are otherwise not really useful purely to tweak things at the margin.Īnother rabbit hole for another time… ¯\_(ツ)_/¯ ? I recently made a note to research buying a CO2 detector for my home. is similarly counterintuitive, to say the least.Ĭomparatively, I'm much more excited about Automerge, which promises much friendlier developer ergonomics as simple as:ĭoc1 = Automerge.In theory, theory and practice are the same. (People writing documentation: please do not make one of the most prominent code examples in your Getting Started an example of what not to do!). but show that to a junior React developer and they're likely to be fundamentally confused, or worse assume that the only code example shown is a valid code example. An experienced Windows developer or game dev might feel entirely at home with the tradeoffs/footguns implied by. I haven't used it, only read through documentation, but IMO Fluid's problem is not so much lock-in as an embrace of old-school columnar storage and handle-based object manipulation. In the end this wasn't a great outcome for the acquired team, but is typical of the aqui-hiring Google does.ĭoc and sheets later added comments and realtime collaborative editing, but it was all reimplemented and never directly lifted from Wave's implementation. This made sense to management as appjet had been pioneering the concept since before Node was a thing. While one would think they were acquired for the similarities between Wave and Etherpad, they were instead tasked with "fixing" the javascript server-side performance situation. The Appjet/Etherpad team was then aqui-hired and quickly relocated to Australia. While the initial launch of Wave went ~okay, the product itself had massive scalability issues. This was seen as very odd to many inside Google, as javascript on the server was a new concept back then, and a far cry from the "officially supported" languages for development at Google. The tech for appjet was primarily Javascript server-side, and I believe it used GWT for Java->Javascript client-side. Wave was built as a secret project in Australia, so when it did launch, internally there was understandably some rife / confusion as to what the strategy was. Wave launched internally at Google to much fanfare at TGIF, and the whole company was somewhat amazed at the time by its realtime collaborative editing. Learn from the past and make brand new mistakes that the next team gets to learn from. This is how progress happens, one step at a time. So were the million other attempts to do this over the years, but hopefully the experience will get incrementally better with each go at it our industry tries. > Google Wave was clearly ahead of its time. OLE! But for the web! Seriously anyone else remember when OLE was a thing and you could drop a print shop pro banner in Word, click it, and print shop pro toolbars would appear? (I think it was print shop pro, if not some similar bit of software, its been 25 years so my memory isn't perfect on this exact point!) > Loop components, “atomic units of productivity” IIRC wasn't it only "doomed" because it was such a resource hog people could barely use it? From what I remember the people who could get it working loved it. Microsoft is bringing back Google Wave, the doomed real-time messaging and collaboration platform Google launched in 2009 and prematurely shuttered in 2010.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |