Vue has electrolytes and it is gluten free. Seriously though I think Vue is the latest shiny example of everything that is wrong with the javascript community.
Javascripts huge problem is the lack of a standard library or better yet a standard way of doing anything. To fill that void alone came NPM. With a million tiny fragmented micro libraries. Then it became a common to start reinventing the wheel and selling your idea to build up your community by claiming the trivial syntax changes make it so much easier to use. I like you have no clue why people are getting so excited about rewriting their apps all the time.
I think of Vue like attempting to reinvent the calculus of react with a clever syntax and more simplified form but results in a Riemann approximation.
I think Vue is more frontend focused where react is achieving far more like react fiber. I do not doubt the power of js community to keep cloning things into forms they are more familiar with and claim a smaller payload is best metric of success.
Who would have thought so much open source collaboration would lead to so much fragmentation?
I wonder what machine learning algos will come up with when they design their own programming language, because I think programming languages are being held back by discussing what syntax makes me feel good to type out.
The problem is that people assume that old = bad.
As soon as one technology is starting to have a nice big community and enough ressources to be usable, the hype for something new destroys it.
People could use Angular 2 Years ago just fine, what on earth happened that it suddenly became so terrible?
Also those are just frontend frameworks! Why is everyone glorifying those??? Is Backend an after thought nowadays? "We got nodeJS... The frontend guy know JS. He will code something, don't worry."
I don't know how you define a Metaverse, but I assume it comes with high expectations of sensory inputs. Check out
https://highfidelity.io/ I think this project will grow to meet the high expectations of a metaverse.
I have yet to find the time to do this myself, but my research concluded that Michael Halls-Moore's @mhallsmoore blog project qsforex[0] is the best place to start. I have used Oanda as a broker and found their service to be great. Plus, As far as I know Oanda is the first to the retail market with an open API. Although, I haven't yet used Oanda's API[1] as mentioned in the setup.
Check out quantstart's write ups[2] for the best info on getting started with algo trading.
Interactive Brokers can be used as well (I have heard Oanda's fills are not as good as Interactive Brokers). I am looking to see if anyone has actually setup a profitable system.
Furthermore, the creator of Elm has a fun explanation too.
Evan Czaplicki - Let's be mainstream! User focused design in Elm - Curry On
https://youtu.be/oYk8CKH7OhE?t=1454
repmgr is an open-source tool suite to manage replication and failover in a cluster of PostgreSQL servers. It enhances PostgreSQL's built-in hot-standby capabilities with tools to set up standby servers, monitor replication, and perform administrative tasks such as failover or manual switchover operations.
repmgr has provided advanced support for PostgreSQL's built-in replication mechanisms since they were introduced in 9.0, and repmgr 2.0 supports all PostgreSQL versions from 9.0 to 9.4.
One of the risks here is that it's very hard to ascertain the support situation around some of these third party products.
If you design your application to communicate to your database through a certain sharding solution, and the you find that sharding product becomes abandoned, you can be in a very difficult position.
That wiki lists at least one product as "stalled".
If I run into a Postgresql bug, am I going to get told "we have no way of debugging that with your third party clustering extension in place"?
These are all obstacles that can be overcome, but just jumping on a random clustering project should be done with caution.
As a related part of clustering, I'd love to be able to do downtime free version upgrades like in Oracle - it would remove one of the major reasons for clustering.
PostgreSQL is a pretty solid platform for, and you can reason about it much like any piece of complex-but-coherent software. In practice, we debug and diagnose it right along with 3rd party extensions. Think about it like debugging a kernel with apps running. You don't get a "clean" case, you have to make it work for all cases cleanly.
Javascripts huge problem is the lack of a standard library or better yet a standard way of doing anything. To fill that void alone came NPM. With a million tiny fragmented micro libraries. Then it became a common to start reinventing the wheel and selling your idea to build up your community by claiming the trivial syntax changes make it so much easier to use. I like you have no clue why people are getting so excited about rewriting their apps all the time.
I think of Vue like attempting to reinvent the calculus of react with a clever syntax and more simplified form but results in a Riemann approximation.
I think Vue is more frontend focused where react is achieving far more like react fiber. I do not doubt the power of js community to keep cloning things into forms they are more familiar with and claim a smaller payload is best metric of success.
Who would have thought so much open source collaboration would lead to so much fragmentation?
I wonder what machine learning algos will come up with when they design their own programming language, because I think programming languages are being held back by discussing what syntax makes me feel good to type out.