HN user

cynicalreason

60 karma
Posts0
Comments35
View on HN
No posts found.

Reconstructing that archive from the records would be close to impossible. The documents they issue and banks/notaries and others have have 30 day expires. In theory most of these documents are issued on sale / mortgages / loans against these type of assets. Both notaries and banks have their own record system - I don't think there's a common system they all use, for notaries I'm not sure if they keep electronic records of these papers .. the system that was hacked was supposed to be it.

Amen ... I've started building a shed (10x10) 1.5 months ago with 0 woodworking experience.

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.

The system was absolutely flawed, still is, but still good enough to encourage the highly skilled.

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.

Cheap comment ..

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)

The problem with UI/DOM is the mental model of working with it. For me I think SPA frameworks need to provide an abstraction layer that makes it easy to work with.

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.

almost 4% mortality rate in Hubei is pretty scary, I imagine a lot has to do with China not reporting real infection numbers which are rumoured to be much higher

I love Scaleway, I constantly have at least 2 instances that I use for personal experimentation and learning ( I went up to 7 when playing around with mesos/consul/marathon ) and I helped a business massively reduce their costs ( by like 90%) by migrating from GoDaddy to self managed Scaleway.

so, after reading the article, yeah, think he explained it a little bad. basically what he's saying in a single node thread node's parallel model doesn't magically fix compute requirements. that graphic of fn1 and fn2 and compute is confusing.

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

you don't NEED to include the serialized state in the body of the HTML, this is the common practice, you can wait for the client to parse your js and then make a separate request for the state data.

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.

server-side react is absolutely slower than jade/pug for templating. there's a lot of work being done in the area in terms of caching but it is a bit more complex (not sure I grasp enough of it to explain it) than how jade/pug work.

I'll read the article and come back on your other points :)

I'm doing exactly this now ... the problem is multiple iterations of trying to set an architecture and a pattern to where things go. The architecture presented, if it was to be implemented that way would have been perfectly fine.

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

ahm .. you mean SELLING, that's what FB does, they have no other product besides their userbase ?

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.