Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mosdl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
211.
▲
by
mosdl
8y ago
It adds easier testability - you can test the logic outside of the framework.
212.
▲
by
mosdl
8y ago
React just does the rerendering and re-binding for you - and does it way less efficient than if you hand coded it. What you should be doing is just changing the parts that you know have changed. Letting react do the hard work will always l
213.
▲
by
mosdl
8y ago
I know the SAP HANA team got cut heavily.
214.
▲
by
mosdl
8y ago
There are plenty of java projects that change apis. Comparing a framework to a language is stupid.
215.
▲
by
mosdl
8y ago
I don't believe you are allowed to get a H1B without a college degree.
216.
▲
by
mosdl
8y ago
Which is why I expect massive layoffs at uber/lyft, they have too many employees for the simple things they do.
217.
▲
by
mosdl
8y ago
They hired a lot of engineers working on internal stuff. Probably will have a large layoff round to reduce costs.
218.
▲
by
mosdl
8y ago
So a manager!
219.
▲
by
mosdl
8y ago
shadowdom is actually the opposite - inflexible and a memory hog. It just allows people to be lazy
220.
▲
by
mosdl
8y ago
Redux means everything is global state which is terrible. A grid I render now has to have global state and most projects forget to do any cleanup - so you end up with all this junk in redux that isn't needed anymore, clogging up memory
221.
▲
by
mosdl
8y ago
nothing involving redux is ever awesome
222.
▲
by
mosdl
8y ago
don't listen to them, the FAANG pay thing is only for select few and is obviously a bubble waiting to pop
223.
▲
by
mosdl
8y ago
Dremio | https://www.dremio.com | Santa Clara, CA | ONSITE Full Stack Engineer | Front-end Engineer One of the biggest pain points when working with Big Data is that the data is stored across multiple sources and data warehousin
224.
▲
by
mosdl
8y ago
This is often because they use a bunch of third party software that adds a lot of bloat. For example Firefox devtools uses redux and you can notice the perf issues. Another issue is many js devs don't know how the Jit compilers work.
225.
▲
by
mosdl
8y ago
In fact inline styles came first!
226.
▲
by
mosdl
8y ago
Amazon was able to survive as they still making money (in fact they grew their income) - people never stopped buying books online.
227.
▲
by
mosdl
8y ago
Dremio | https://www.dremio.com | Santa Clara, CA | ONSITE Full Stack Engineer | Front-end Engineer One of the biggest pain points when working with Big Data is that the data is stored across multiple sources and data warehousin
228.
▲
by
mosdl
8y ago
Same thing happens in Austin/NY, nothing Bay Area specific
229.
▲
by
mosdl
8y ago
http://calmod.org/project-benefits/ more trains, faster travel times, cheaper to run and less pollution.
230.
▲
by
mosdl
8y ago
Except Vienna housing keeps getting more expensive as there isn't much stock available.
231.
▲
by
mosdl
8y ago
Just the hassle/cost of flying someone to do an on-site interview is a deterrent.
232.
▲
by
mosdl
8y ago
add gave us lots of devs who don't know how to use the DOM directly without jquery.
233.
▲
by
mosdl
8y ago
Actually not true - browsers already batch DOM change repaints.
234.
▲
by
mosdl
8y ago
React (or vdom in general) has high memory costs and won't be close to native performance anytime soon (or ever). As long as you are cognizant about the trade offs it can be the right choice, but never blind. People forget the old ap
235.
▲
by
mosdl
8y ago
Each solution has pros and cons, and engineering is really about making those choices and dealing with the repercussions.
236.
▲
by
mosdl
8y ago
And instead we have a 1 bloated codebase that is slow on 3 platforms and doesn't provide native features? The fascination with 1 codebase doing multiple things is funny.
237.
▲
by
mosdl
8y ago
You can achieve all of that with a singleton that is shared and some events (and do some of your own batching). No need for another dependency and you save bloat size.
238.
▲
by
mosdl
8y ago
The problem is that they run too often, not that they are slow. mapStateToProps is called too often, and that leads to a bunch of needless shallow compares and often renders. Its a weakness of the magic design, and if I need to optimize t
239.
▲
by
mosdl
8y ago
5 generations to make something that is less efficient (slow build times, caching not always possible) that straight up css processors. Its kinda sad really (but hey my css is in my js file now, so useful).
240.
▲
by
mosdl
8y ago
the 300k RSUs are very uncommon
More ›