60 karma · joined October 12, 2016
It's the most fun I've had in a decade .. my joints are swollen, I've got bruises and scrapes on my hands and feet, skin on my hand is actually rough.
I work from home nine-to-five, software. I can't wait to finish work to actually go outside and work on the shed.
I've actually considered quitting my job and doing this full time .. but it won't pay nearly enough as I'm making in software and my financial commitments won't let me.
Our (Romania's) education system was (is) the same, if you were GOOD at something there were plenty of paths that teachers would generally push you towards, special clubs for maths, languages, art (less common). Or schools who would try to group together highly skilled students.
System (after communism) has the same flaw, most rural areas have worse access to education, or better said, much worse quality of education.
I see them as options, not steps, options within the same ecosystem
A lot changed, but the limitation is still the same - the delivery platform - browser (dom + js)
Thus React. I can think of it in a functional pattern and let it abstract the DOM/UI for me, ofc I understand there's a cost to it but that cost will greatly be overshadowed development & maintenance costs.
If I land on some page where annoying adds still get past ABP I close and never visit the page again.
personally never used clustering and the cluster module (we did that at haproxy lvl with containerised individual node processes), but I think that's exactly what he's saying, that the cluster module is the limitation (https://nodejs.org/api/cluster.html). not sure how they use it but it seems to imply requests being fully read in the cluster PID than passed to the workers
I don't get point 2, if they are to 'hydrate' the react renders in node with data, they have to have a 'fetching' logic in there, the fact that it connects to an 'API' instance makes no difference, the client could use the same connection with same logic client side.
I'll read the article and come back on your other points :)
Now there are 3 iterations .. with 3 different patterns of what would be a state container, UI business flows split across 3 layers (data access/api, business/decision , view models) and view models (NOT VIEWS) sharing state.
What also doesn't help is the tooling is close to non existent .. I got so used to webpack / lib(framework) dev tools / hot reloading / all in 1 dependency management / intellisense
google has been scrutinized in the past, one big difference is google doesn't offer this data to private companies (yeah yeah .. NSA ) and their model never really allowed someone like CA to get their data.
google's original product was search, from that they were able to extrapolate insane amounts of user data that they then used in their biggest product: ADS. but they never provided the USER data, they provided an interface for their ad customers to better target their ads. so in a way google uses the data to create products around it while for facebook users and their data ARE the product.