joewood1972

Sure, DBT (Data Build Tool) has been around for a while. It's a way to manage SQL (and also Python) data pipelines - the "T" in ELT. Home page for DBT Core is here https://docs.getdbt.com/ (there is also a hosted DBT cloud premium offering). There are some good books on Data Engineering with DBT - I particularly liked "Data Engineering with dbt: A practical guide to building a cloud-based, pragmatic, and dependable data platform with SQL" by Roberto Zagni.

Loving this list. One thing I would totally recommend though is to look at tools like DBT, as this supports a lot of these patterns out of the box (snapshots, materialized views, seeds for 'system tables' etc.). It also addresses the concerns with views and schema management.

One question that springs to mind is the in-browser "playground" and hosted coding use-case. I assume WASM will be used in that scenario. I'm wondering what the overhead is there.

For example, Apache Iceberg is exactly this. Complete with bitemporal query support.

Hi Slig, just wanted to say that my family has been obsessing over these puzzles since you posted these. Thanks for the putting this together.

I would suggest you add some sort of share button, for bragging and viral spreading. And maybe some sort of local state for tracking streaks.

In the intro, this post is referenced

https://francoisbest.com/posts/2021/hashvatars

This is great. Looks really nice on mobile.

One problem will be deciding on when tomorrow is. If your work day starts at 9pm, you have lunch at midnight, do you then go home the next day? We could lose lots of complexity of timezones, but swap in the complexity of dates. Financial transactions and trading sessions could get really complicated fast.

I think it depends on the type of application, and how much code you want to reuse. Assuming this a fairly large scale app and long term maintainability is a consideration:

* If some of the code is likely to be reused with an associated website I would go for Electron. Using ReactJS.

* If an associated mobile app is also possible, I would take a look at React-Native, which have some embryonic desktop technology counterparts. This option can be combined with a webview.

* Worth also looking at Xamarin, especially if there's existing investment and skills in .NET (e.g. existing Windows app being migrated).

Sure you can share files, it's works OK with some caveats. More in the overview under DriveFs: https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subs...

The best answer is to use a tool that saves in the format that the file was in originally. I think VSCode and some others do that. If the file only has 2-space indentation then TAB becomes 2-spaces. etc...

That said, assuming a greenfield the best case has to be to use tabs. This way if somebody has a preference to small indents then they can configure the TAB to render as 2-spaces - it becomes a render issue.

So, use a modern tool and it's a moot point.

P.S. not sure why Silicon Valley's Richard started talking about 8 space tabs. That would be crazy. The only time I've seen that is in a proportional font in a word processor.

JSX has zero community adoption? Or was there a missing comma in there? Of the React code I see, I would estimate that JSX adoption is high 90s.

I've used both Angular, played with Angular 2 and React. Plus many other MVC (and MVVM) libraries. I would say that the state managed React model is far more scalable than the traditional MVC 'observable' model. Sure, you can use immutability in Angular-2, but with React you have an architecture built around simplicity with the need to integrate different artifacts.

JSX helps React to scale because it extends type safety of TS or Flow into the UI DSL. JSX allows the developer to deal with the DOM as an object graph expression, right in the language. From a strongly typed perspective, this works much better than templates or embedding code into HTML.

Seems to be a confusing article and site. It lists AR as a disruptor, but mentions Google Glass and not Hololens. The link to "Augmented Reality" links to an article about VR. Then it says that cloud computing is a threat to the textbook, where most textbooks can happily sit on an SD drive. And then "multi-touch LCD" is a disruptor? Seriously?

No, de-duplication and conflict resolution is much harder if dependencies are in a bundle. There are many better solutions to this problem:

* Fix NPM and make it immutable. If there's a legal problem allow a package to be flagged with a warning and redirected to its new name.

* Use bundleDependencies in npm

* and maybe even back-up your entire code directory

Not sure I follow. For distributing apps for friends you can (and I do) distribute using HockeyApp or TestFlight or whatever. There's also a Development->Sideload app feature in Windows 10 already. It's hard to argue that the cost of doing this outweighs the security benefits. Just think how hard it would be to do a DDoS attack without robots installed via malware everywhere.

The problem with an open distribution system is that it easy to abuse, and that leads to security problems. Most of us all know non-IT literate family members that have clicked through a web advert advertising to "speed up your computer" to end up installing some bad spyware/malware or whatever. I'm happy for Windows to become a walled garden by default, as long there's an easy option to switch it off.

Agreed. I see the same result. The search results are as I would expect. I understand there is an issue with languages and regions, maybe the OP's region is not US English. It would be interesting to see what other users' searches show from different regions.

Neither, the cool kids are using Radium https://github.com/FormidableLabs/radium :-J

I think what was meant was that immutability solves cache synrhoncization issues. More accurately, state synchronization issues.

If you think about the DOM as the projected state of an application, immutable data structures allow you to very simply define a functions that perform the transformation from application state to the GUI data structures (e.g. the DOM). If the state mutates this can cause cascading state changes that make this function much harder to reason about.

Not to diminish the argument, but other than diskspace, I really don't understand the downsides described here. I'm wondering, given the author was an early adopter of Git, this is purely hipster syndrome. Everybody is using it, so it's not cool any more.

If everything is immutable then a reference check is all you need. They key is to avoid deep copies. Observables are problematic when changes can ripple through your model/view-model - resulting in multiple DOM changes. This equally applies to WPF.

React also has its own implementation of the Flex layout system. Implemented in JavaScript and C++ (for react native).

Unless I've misunderstood, and it may be semantics, but I don't see this as infinite scroll. If I had 10,000,000 rows the browser would still struggle with this grid as it needs to keep the React JS objects in memory. I would like to see server side paging integrated with the scrolling.

I haven't tried it yet, so I may be wrong.