allover

11 ms·

61.
by allover 7y ago
There's a huge difference. The parens in lisps are significantly detrimental to its first impression, and 3rd, 4th ... I have literally never met a developer I can show a lisp code sample to whose reaction isn't "what the hel
62.
by allover 7y ago
Then you can use `useHistory` (or `withRouter` if you're not hooks-ready). I somewhat agree that the <Redirect /> component is not actually that useful, it's only useful in very simple cases like "based on one rout
63.
by allover 7y ago
This Ryan Florence talk is a great talk that touches on this topic, especially in some of the more creative examples: https://www.youtube.com/watch?v=kp-NOggyz54
64.
by allover 7y ago
You can now use hooks for some things you might previously want a component for, e.g. useFetch instead of <Fetch />, but don't agree "this should definitely be the case". Dogma is never good.
65.
by allover 7y ago
Strongly disagree, and 'because the function is called that' is a very poor reason. You're not using React to its full potential if you think like this.
66.
by allover 7y ago
Disagree there's anything really low-mental-overhead about bringing redux into your project.
67.
by allover 7y ago
It's not really bananas when you actually start to think of everything 'as components', and consider that 'render' can neatly, declaratively describe behaviour, not just the DOM.
68.
by allover 7y ago
There are the features a company "tries" to innovate on, vs those they consider uninteresting and just try to find a quality/cost balance.
69.
by allover 7y ago
I was referring to the act of deployment itself. A single deployment of a monolith, without needing to ensure a dependent service whose pipeline is owned by another team is "deployed first", can be a lot easier to organise. As I
70.
by allover 7y ago
> Micro services don't only provide horizontal scaling but also operational scaling I think it's more accurate to say that they don't necessarily provide any horizontal scaling, but can provide operational scaling. This
71.
by allover 7y ago
Yep, see jwilk's comment re: history.replaceState() existing: https://news.ycombinator.com/item?id=21368314
72.
by allover 7y ago
> How do you even know all the permutations of personal data that came be stored in the logs. There are possibly infinite possible ways personal information can manifest in logs. Nonsense. You write the log statements. You know what data
73.
by allover 7y ago
> macOS is exactly where people expect native theme Who are 'people' here? The strawman here is that 'average users' do not expect native theme.
74.
by allover 7y ago
I did say "non-technical", which is open to interpretation, but I did not mean 'computer illiterate' (i.e. only uses apps given by OS). The discussion here is really about average users, and the baseline assumption here
75.
by allover 7y ago
I don't think this is very debatable. Consider the fact you might be in the vast minority of users. I'm a dev/technical user, in the key audience for native look & feel powertools, yet the main apps I use on Mac are st
76.
by allover 7y ago
Well it's the generalisation about a large community that is the problem, whether put arrogantly or not (the arrogance only makes it harder to scroll past and ignore). GP put it well: > I'm always confused when someone calls ou
77.
by allover 7y ago
Even imagining a world in which all the major browser vendors had agreed to constrain browsers to a pure HTML+CSS+flash-like-extension-free web, someone would've eventually come out with a heavily funded 'next gen' browser wi
78.
by allover 7y ago
> While this assessment is somewhat accurate No it isn't, and please stop perpetuating this nonsense.
79.
by allover 7y ago
1) As I said, it was not just JS in this situation at the time, it also applied to other major registries like PyPi. So your point does not reinforce the original attack on JS developers. Congrats to Maven for getting this right. 2) Namespa
80.
by allover 7y ago
1) Same applies for npm (granted, this was only fixed after the left-pad incident, and npm was not the only language's registry to have that issue). 2) As mentioned elsewhere in this thread, npm supports namespaced packages, but they a
81.
by allover 7y ago
> Even PHP gets this right. It's not hard. PHP had the luxury of coming out with a package manager (Composer) later, and learning from others before it. (2012 vs 2010 for npm). Npm similarly improved on a lot of package managers tha
82.
by allover 7y ago
> Mostly because the vast majority of JS developers don't seem to be aware of the rest of the software universe Do you have any evidence to back up this statement, compared to developers in other languages? Or is this just business-
83.
by allover 7y ago
To be fair, that looks like their site's footer (see blog), but agree it would make sense to remove it on that page, to not contradict the message :)
84.
by allover 7y ago
Well, not all lazy HN commentary, like criticisms of 'scrolljacking' should be taken seriously. ;)
85.
by allover 7y ago
I mean, just one big reason Fortnite doesn't feel like a pubg rip is because Fortnite's building/editing mechanic sets it completely apart. Watch one of the Fortnite world cup matches going on right now [1] and tell me that y
86.
by allover 7y ago
The console.log was only there to illustrate that the code in useEffect's callback is only being run on the client-side (see the codesandbox I linked to). I think it's clear from the parent I was responding to that they have bette
87.
by allover 7y ago
> and I still have no idea how I only do stuff on the client in a SSR environment (stuff that i did in componentDidMount) The 'useEffect' hook - it won't be executed if you use e.g. ReactDOMServer.renderToString() for SSR
88.
by allover 7y ago
In this case the author is suggesting a way to avoid it, for distributions to not theme and introduce the bugs in the first place.
89.
by allover 7y ago
> But when you have many similar repos (modules) with similar build steps you want to manage How many teams do you have? In all seriousness, if you aren't talking at least one team per repo, have you considered a monorepo setup? Are
90.
by allover 7y ago
So you're making the same change but taking longer to do so?

More ›