i found assembly is easier to assemble from scratch (it's apple and orange but.). Most materials should exclude these tooling, mostly rust based tools. We should be able to write them by hands just like when assembly was taught. Compiler and assembly are separate classes. I think it's bad assumption that only compiler devs only care about wasm. It's compiling target, sure, but framing it this way will not broaden its knowledge.
These topic and mentioned tools always fail to demonstrate how sync engine works in multiple players modes. And mostly only for backend written in TS/JS, worse it's only for using with 3rd service (which you couldn't put your business logic in here). The first thing i scan in these tools' docs are how they handle write conflict whose conflict is semantic level, not data exchange format level.
Addendum (since quite many upvotes): for the latter, they break a team of 8 (this is already a small team apart from the whole org) into 2 teams each 4 and break a monolith app into 2 microservices. At the time I saw that, the company started to have more and more managers. Guess what, not even making a break-even yet!
I like to work with companies that make a lot of profit on their 5 digit customers where Single machine is enough. But we can make it 3 behind an LB. I absolute hate business whose infra is a bunch of message broker, lambda, queue .. yet make little money.
The problem of having multiple sources of data is Consistency, Availability, Partition tolerance. It also depends on IO characteristic of apps. Who are readers, who writers, how long stale data is acceptable. Basically all the distribute system problems. In web app, frontend + backend + db sit next to it is enough of problem (e.g. SPA vs MPA state problem)
Enlighten me, if it needs a host different network location than the app, what is the advantage over postgres, is it because it's easier to "setup" and "maintain?
$20 IEM is crazy good. I'm lazy to find out if $100 IEM is already above 97th percentile of human ears capability. A lot of illusion of great quality above p90.
I think it would have similar effect of reddit or youtube. 99% of the time I use reddit or youtube, it's started with search to jump straight to a topic.
And that is better because the demand side is an active, the knowledge side is the sort of passive. So mediocre knowledge wouldn't have the money backed ads power to outperform the better knowledge or solution.
Yeah it's called "miller columns" which I tried (as a implementer) once. The width constraint per column is not quite nice, and when it has more than 3 columns, the horizontal scroll ux makes it worse (I think it's ok on mobile). I haven't found a good ux on tree structure in general, it's just suck.
Is there anyone else's brain doesn't work well with canvas like mine? It looks unorganized to me with "group" and "arrow". Unlike structural design like we are used to on daily basis like "order" (left-to-right + top-to-bottom), "index" (several kind of nav). When I look at this type of canvas my brain is confused where to start, what's the order because it looks like a mesh. I guess this is for popular brains?
Solid. It will be a smooth transition DX-wise. And it's better in every angle. Except of course so called "big community", "lots of library", "easier to hire" .. poor excuse for technology advancement.