krirken
Joined 10 years ago
Karma
43
Submissions
12
Member since
Apr 28
Recent submissions
Comment · 9 years ago
Comment · 9 years ago
https://Nodeschool.io has free open source tutorials on a range of Node topics.
Comment · 9 years ago
> That's an intense app rebuild
That is not even close to an excuse. A remote code execution vulnerability has the potential to destroy your whole company.
Comment · 9 years ago
> it's not unethical to engage in unethical behavior
OK.
Comment · 9 years ago
Some key points:
1. Preact eliminated white/black lists and uses regexes instead [1]. These lists take up huge amounts of space in React/ReactDOM [2].
2. No synthetic events, just native `addEventListener` [3].
3. Only target the DOM for rendering, no React Native to worry about.
4. Less invariants, error handling, and error messages
[1] https://github.com/developit/preact/blob/master/src/constant...
[2] https://github.com/facebook/react/blob/master/src/renderers/...
[3] https://github.com/developit/preact/blob/master/src/dom/inde...
Comment · 9 years ago
I agree, there are many competitors to React for targeting the DOM, but there is much less competition for targeting Native. I hope to see more JSX-to-Native engines pop up soon to solve that problem.
Comment · 9 years ago
Indeed, preact [1] and and inferno [2] are both MIT Licensed.
[1] https://github.com/developit/preact/blob/master/LICENSE
[2] https://github.com/infernojs/inferno/blob/master/LICENSE.md
Comment · 10 years ago
Preact Issue #417 - Do virtual DOM diffing on web worker? [1]
Comment · 10 years ago
This is correct. I once had a series of customer service reps deny me access to my account to the point where they told me my account was irretrievable. Irretrievable? I called back the next day and the new rep told me those other people were totally incorrect, and he resolved my issue in 15 minutes.
With high turnover rate and minimal training, most service reps are reading from a script and attempting to appease you into hanging up the phone anyway.
Comment · 10 years ago
I see, and I agree that the accountability of cyclists (and slightly less so for motorists) in NYC is almost zero. I also agree that electric powered bicycles should be held to a higher standard than normal bikes, particularly in that their use is entirely illegal so it should be much easier to spot and ticket them. I mostly posted these facts because most non-NYCers don't even realize that these uses of a bike are actually against the law.
EDIT: I just read your edit,
> I find electric bikes even more destabilizing and most objectionable, because they are faster and quieter, and I think because they are favored by a statistical sample that skews toward more selfish/self-interested.
This is a good summary of my thoughts about electrical bicycles as well.
Comment · 10 years ago
> most electric bikes I see are ridden dangerously to pedestrians; by NYC deliverymen (doubt I've ever seen a woman on one), swiftly and silently sneaking up to run you down on sidewalks or the wrong way on one way streets.
Both of those uses of a bicycle - operation on a sidewalk and riding against traffic on a one-way street - are a violation of NYC traffic law [1]. The operator is the one causing danger, not the bicycle.
[1] http://www.nyc.gov/html/dot/downloads/pdf/bicyclerules_engli...
Comment · 10 years ago
If not derogatory, I have never found the "This is how ... was done in the 90s/80s/70s" sentiment to contribute much to a conversation.
> The company's internal review of the incident continued. Upon discovering a vulnerability in the Apache Struts web application framework as the initial attack vector, Equifax patched the affected web application before bringing it back online.
That bullet point lies between the "July 30th" and "August 2nd" bullet points. Based on that timeline, the vulnerability took days to patch.