Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
allover
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
181.
▲
by
allover
9y ago
Can you suggest how the build processes would skew it? For all 3 projects I believe the recommended build method involves a cli tool that installs each package once.
182.
▲
by
allover
9y ago
Totally agree actually, I love all Rich's talks and agree with almost every word of Simple Made Easy but I don't necessarily agree with the conclusion he takes it to (Clojure). I've heard it suggested somewhere that possibly
183.
▲
by
allover
9y ago
> Simplicity makes picking up the unfamiliar easier. The talk I referenced talks about how the opposite is often true. Tools that result in objectively simpler systems can come with a initially steeper learning curve. > You can't
184.
▲
by
allover
9y ago
To all intents and purposes, when people say Sass, they mean Scss.
185.
▲
by
allover
9y ago
I don't mean to be an arse, but if you agree with my point, then maybe you can see why I disagree that your "that and" is a valid strike against React/in favour of Vue.
186.
▲
by
allover
9y ago
20 minutes vs an afternoon is probably not a great gauge for making technology choices. I highly recommend watching Rich Hickey's "Simple Made Easy" [1] talk which covers how the right ("simple") choice may not be t
187.
▲
by
allover
9y ago
I would argue 'integrates so easily into the imperative JS ecosystem' is not a differentiating factor over all the other JS frameworks, so its declarative programming style is far more likely to be the reason it is popular (and in
188.
▲
by
allover
9y ago
> pytest fixtures don't have that issue, as they're only run when you include the fixture for DI I don't see how that prevents any of the basic problems raised in the article.
189.
▲
by
allover
9y ago
Hmm I'm in the camp that believes setUp/tearDown and fixtures are not only equivalent, but both antipatterns. This article explains it better than I can [1] [1] https://robots.thoughtbot.com/lets-not
190.
▲
by
allover
9y ago
> extremely minimal and easy-to-use library. 'Extremely minimal' is hyperbole and 'easy-to-use' is subjective. I disagree with this as an absolute statement. I think there's a trade off, and it potentially harms
191.
▲
by
allover
9y ago
Not sure why you were downvoted, I agree. Redux brings a high 'concept count', for such a small amount of code. To talk the language of redux you have to understand: dispatch, actions, actions-types, actionCreators, reducers, mapS
192.
▲
by
allover
9y ago
> Seems like an interesting idea, but it's barely supported at the moment You can polyfill custom-elements to all evergreen browsers plus IE11 [1], but yeah that's not good enough for a lot of sites. [1] https://gith
193.
▲
by
allover
9y ago
Your comment is based on a pretty naive assumption that someone's making an either/or decision between pretty and functional. What team have you worked on where that is literally ever the case?
194.
▲
by
allover
9y ago
Can you give specifics other than this new thing and pricing? I feel like discovery engines making obvious recommendations is actually a non-trivial problem to solve, I remember Spotify used to recommend me a lot of 'well duh' stu
195.
▲
by
allover
9y ago
It's not funny at all. It's totally logical that you'd have competing clients.
196.
▲
by
allover
9y ago
> It's not, it's a package manager for a package registry. >> npm is not a package registry. Is a package manager with a package registry. Not sure what point you're trying to make. Yarn is a package manager for th
197.
▲
by
allover
9y ago
> A package manager for a package manager It's not, it's a package manager for a package registry. > that shows the overengineering of the JS ecosystem Nope. > Facebook could improve npm but they would not profit too muc
198.
▲
by
allover
9y ago
Several CSS-in-JS libs support all of CSS, and allow you to write actual CSS and not camelCase styles. styled-components [1] is prob the most popular example. Your complaint they are evaluating JS just to set styles is valid, tho some libs,
199.
▲
by
allover
9y ago
jQuery is more than the DOM api.
200.
▲
by
allover
9y ago
That's not great. Far worse and less usable than Premii's iOS app imo, subjective though obviously.
201.
▲
by
allover
9y ago
> We've got to move past that. No, we've got to move past lazy generalizations. You've boiled down multiple issues to 'people only know jQuery'. Meanwhile the rest of this thread is dealing with more interesting
202.
▲
by
allover
9y ago
I don't think anyone's really claiming that Vue is a 'next big thing' to switch to from React. Vue/React/Angular are all competitors of the same generation.
203.
▲
by
allover
9y ago
Zooming in and out and panning around a webpage is a terrible user experience in my opinion.
204.
▲
by
allover
9y ago
It loads fast and doesn't use web fonts, but that's not really a high bar, for essentially a forum. Apart from that it's not exactly a pleasant reading experience. Tiny text for modern displays. Poor typography (bad line-heig
205.
▲
by
allover
9y ago
Analytics is loaded asynchronously so it doesn't block rendering or interactivity. Yeah it'd be nice if they used server-side analytics instead, but cost/benefit.
206.
▲
by
allover
9y ago
Being able to do so is certainly a cool feature. But I've built a lot of apps prior to Redux and never felt like state replays were a must for debugging. There are various ways to debug state in a React app that uses setState. React de
207.
▲
by
allover
9y ago
Scripting, e.g an Alexa skill/IFTT thing/MacOS automation thing. Or just for one-offs for people who live in the terminal. Not sure I could be bothered to 'insert' from the terminal but 'gcal list tomorrow' see
208.
▲
by
allover
9y ago
That would be nice, but damn there are some entitled brats in that thread. Open source sadness.
209.
▲
by
allover
9y ago
> I trust that the people who provided whatever configuration it used knew what they were doing You should never trust that people know what they are doing in this industry.
210.
▲
by
allover
9y ago
RE the 2nd issue: Are you sure you even need `private: true`? Scoped modules are private by default right? I thought `private: true` was supposed to prevent publishing to npm altogether. It's odd they haven't at least triaged the
More ›