To understand a framework, you need a mental model of it. Good documentation is helpful, but it seldom walks through why specific design choices were necessary.
181 karma · joined January 9, 2017
https://ananis.in
To understand a framework, you need a mental model of it. Good documentation is helpful, but it seldom walks through why specific design choices were necessary.
When I first got access to the internet, MIT seemed awfully productive in producing code. Before I found out that MIT License doesn't imply the work was done by a person at MIT!
Can I ask, what were the benefits of writing a new workflow engine instead of building around Temporal?
Would that not imply they aren't a good fit for the OP's workplace? And presumably, a lot of larger tech companies, since communication must be a large part of your job.
I am admittedly not good at talking on the fly if I haven't prepped for it. I try to make up for it by trying to focus on writing well.
With the comparisons to calcite, I was curious if you've considered implementing sqlglot in a native language too? Something compiling down to a small wasm extension would make it accessible to web apps.
* run a full blown browser in the cloud and stream back pixels
* emulate a native application in the browser (like, github.dev)
Both are okay but per user backends feel like a nicer primitive to build applications with. Apps that run locally in the browser but can access cloud compute/storage on demand.
SolidJs shows you can get most of the functionality of hooks using signals. Who knows, if someday most Preact users converge to using signals for state management, maybe they will throw out hooks altogether. But in their current context, supporting both hooks and signals feels a reasonable choice to me.
* Hooks - `setState` reruns the full code for your component.
* Signals - only the dependent effects/computed/JSX is run.
This isn't derived from principled reasoning, but I think of it as similar to community norms. Not the best example, but you wouldn't mind someone subletting their homes to Airbnb, but if all of your apartment complex does it, it invites regulation. A product like copilot enables copying code (even if inspired, and not verbatim) at a scale that individual developers can't. So respecting software licenses needs to be codified (legally?) while previously it was left unmonitored.
That is just not true.
1 - This helps parallelize regular python code too, like the kind that goes into writing web services.
2 - While you'd still write native extensions to get optimum performance for single threaded code, having the thread dispatch layer in python makes parallelizing execution convenient and robust. For example, see the comment from people who maintain scikit-learn below. I'd love to see python get composable task parallelism like Julia where you can freely spawn threads within threads without worrying about their lifetimes.
link: https://github.com/colesbury/nogil/issues/36#issuecomment-10...
1. https://github.com/suborbital/reactr 2. https://wasmedge.org/
This was a really interesting bit to me, could you give detail on how the memory usage gets split up across these? Thank you.
@supabase developers, is this a reasonable way to do things or am I missing something?
Isn't this similar to the point this article is trying to make? Looking at statistics as a collection of algorithmic recipes shifts attention to how those procedures are designed, and when do they yield us useful summaries. When you want a "representative mean" rather than the population average, you'd just tweak your algorithm.
As others point out, Coinbase must know the current legality of the lending offering. The likely objective of this piece is to gain support of those invested in the industry, and for them to push their legislators to reformulate laws.
I'd think the project idea is that differential dataflow is too useful a technology to only be understood by a few people. By writing it a second time around, it might be feasible to trade off some of its power for a more lean and accessible implementation.
I recall seeing another project HN which created dashboards out of a yaml description. This seems like a fantastic idea, given that a lot of business panels and dashboard apps can be implemented with a limited set of UI interactions.
The harshest way to interpret unavailability of regular JS tutorials should be that the primary authors don't have enough bandwidth or the inclination to work on it, and the community hasn't picked up the slack to make it more accessible to beginners. The authors deserve nothing other than gratitude.