Just use http functions in a Velo by Wix project - you will get 50ms cold start out of the box.
240 karma · joined April 17, 2013
For webapp, the figure should be 100ms. The only platform that meets that figure (that I know of) is Velo by Wix with around 50ms cold start for node.js
It only means that we, as the JS community, are continuing to fail with presenting an alternative to PHP and JS.
I find the statement that OO is obsolete. Maybe that is the intention of the React team, but it is not reflected in their main documentation yet.
As for the style of the React example - I have taken the React example from todoMVC "as is".
I invite you to write any other React implementation of TodoMVC, and will do my best to create the equivalent with Stencil.
In the react docs - here specifically, https://reactjs.org/docs/state-and-lifecycle.html
The first action item when talking about state is to concert a function to a class.
Are you saying that the official react docs, when introducing state, promote using an obsolete API?
Given a Todo mvc functional component example, will try to use the stencil functional component syntax to build an equivalent
If you believe it is obsolete, please do a Todo mvc React example with functional components and I commit to try and use stencil functional component syntax to create a valid comparison.
1. a lot of companies use it - we as well and not planning to move anywhere.
2. if you know React, moving to Stencil is super simple.
We at Wix are a huge React shop. We know all the best and worst of React, both OO and Functional styles.
For us, while Stencil is super interesting and is better compared to React, we will not move to Stencil.
Had we started now, it would have been a hard choice React or Stencil
I think the main message here is that
From a point of view of API design, it looks great.
I am sure it has some drawbacks, like distance on the rgb space may not be the best option, or that it does not ignore background color of it is not transparent, still, I like the way of thinking
So I guess there is a place for a professional business for building websites
You will not need to write the whole thing from scratch specific to the customer. Instead, just code the extra bits.
Having said that, I think there is a large market for websites designers and coders, and we see an active community on Wix of people who build websites for customers
But to use Wix Code, you will need to know some level of coding, hence value to sell for your clients.
And I agree, there is a huge market for people to build websites for customers, you need to focus on the value you deliver to your customers, from design all the way to coding, SEO, content and social.
We see people looking to hire programmers to help them build websites using the platform.
There is a demand for programmers among the Wix Experts community.
(I am working for Wix)
Website design is not a uniform business. A lot depends on what your client needs.
For simple needs, solutions such as our Wix ADI are a great self service tool.
When you want pixel perfect design, the Wix Editor is the tool for you. Most people are able to use the Wix editor, but creating a great design is a challenge, simply because not everyone have the training and talent of a designer. We do see a lot of designers working on wix and making money that way.
When you want more, Wix Code comes into play. With it, you get a serverless platform and a database as a service, and you are able to code whatever solutions you need for the customer.
While in theory your customer can do the coding and design, in practice they are more then likely to hire a professional to do so for them.
Looking like a great project, simple and fun.
Keep in mind that other similar projects tried the same approach before, namely firebase and parse.com. both for only so much traction because at the end, real world applications need more features - business logic, backend that uses other APIs, etc.
Still, looks like a fun project
It is the observation that all software is built of 3 layers -
Inbound IO, what you call imperative shell Business logic core, what you call functional core Outbound IO, what you call again imperative shell.
The problem with the terms in functional programming is that when they say side effects, in most cases they mean IO.
The functional core does not have to be functional for you to get the benefits - easy testing, easy to reason about, easy to develop. In fact, in some cases, functional programing is the wrong tool while having a business logic core that is separated from IO is still a very valid architecture.
Which brings me to my point - what the author fails to talk about is why spanner has taken the design decision they have made. He does claim scalability, but that is a very general word.
I believe the spanner decision is to avoid making a global voting, as in global across the entire world, from North America, to Asia, Europe and even as far as Australia. Such a global voting will take a lot of time - impose seconds of later on any write.
I think the author, when he talks about having a single global vote with a small window, thinks in terms of a single database, maybe two regions on the Continental USA, as apposed to spanner trying to be Geo distributed.
Come on, this is not about database design. This is about making the wrong technical choice, the definition of "I have a hammer, so everything looks like a nail".
What about export of the addresses, and using a second service on the export?
Even with the best of clouds (more then one of the big names) we faced downtimes caused by multiple cloud failures.
Just imagine, a store that is Geo distributed, resilient and just works.
This is super exciting for the web and for customers of websites!!!
Big thumb up.
The only legit case to use == is if you are
1. Insane
2. The kind of person who changes Java 1 object to equal 2
Our response - https://vimeo.com/138432267