alexhayes

Here's the second part of a two part blog series I wrote about Atomic - the Server Driven UI framework I've been leading at REA Group.

Atomic is a second generation architecture that features hot-reloading native clients with a generic actions system that allows the entire UI to be defined on the server while maintaining a super dynamic, native UI.

You can build very simple things or you can also build very complex things like native, realtime messaging (which we've done and exists in production).

There's an accompanying video (down the bottom) which hopefully gives you a fairly good idea of the features :)

Looking forward to the R2 chip and then pairing that with the D2.

Google Home Mini connected to YouTube Music also suffers similar problems and I swear it's ability to determine the voice commands given has gotten far worse than it was a few years ago.

For example, asking for specific albums and it will play someone's playlist of the album - in terrible quality because someone uploaded it as a video to YouTube I think part of the problem is that the music catalogue is so poorly maintained/governed on YouTube Music. For example there are many songs that state they are by Little Richard that are actually other artists' songs

I feel kinda bad - I'm pretty sure I broke Google as I was uploading quite a few large files via Google Drive and it was chugging pretty hard.

And now because of that it seems HN is also hurting.

I'm sorry internet.

Does anyone have any thoughts on the security (or other) implications of all your email for services in which you sign up using Apple SignIn now being relayed through Apple's mail servers?

It seems like a great way for Apple to hoover up a heap information they probably don't need.

I also wonder how they are going to combat bounces and send back a usable error message. While they can perhaps do useful things with say a mailbox full bounce they are probably going to have to hide or at least obfuscate some other kinds of bounces.

Another thing I'd point out is that the flutter widgets themself have perhaps the most extensive, and useful, documentation in code I've come across. If you're using an editor that let's you "click through" into the thing you're calling then it's almost all the documentation you need!

> Debugging is not at its best.

I don't think the author correctly represents this functionality in flutter.

I've found the debugging of flutter apps inside Android Studio to be excellent! You add a break point (by clicking on the lane to the left of your code or hitting some keyboard shortcut) and execution will be stopped and you can step through etc etc..

Using print statements to debug is slow and cumbersome, debugging in flutter is not.

Totally agree - and from a tech point I imagine they probably don't require a new OS (perhaps in most cases).

However I imagine it's probably a good way to get people to stay up to date with the latest OS: "Oh, I want that shiny new app, I must update"

As someone who contributed to a very small part of this I know how hard the core maintainers worked and how patient they were, at least with my very long lived PR.

Thank you for staying the course and believing! What an EPIC effort!!!

I'm unsure why most folks seem to get into a pickle over git submodules but I think it's essentially due to the mental model of how they think about the structure of the "root" project and it's relation to the submodules. This in turn seems to govern how they work with the root project and it's submodules.

I kind of think of the relationship as a pointer into what should be a entirely separately managed project. Changes to that project should happen in that project and only then should the "pointer" be modified. I usually go as far as checking out the submodule separately (to my "projects" directory) when I need to work on it, which of course entirely unnecessary, but for me helps keep that separation.

Another approach I've found that helps to combat issues some people have with them is to not have them littered throughout a project but have a very clear delineation between what are submodule and "root" project git managed files - ie. an appropriately named, usually top level, directory.

In practice I find them an extremely useful way of getting stuff done effectively and efficiently!

As does DO