Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lopatin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
541.
▲
by
lopatin
10y ago
Agreed, because the problem domain/system dynamics needs to be encoded into Scheme before synthesis can be useful for high level specs. If this kind of programming style takes off, it could possibly be useful for communities to supply
542.
▲
by
lopatin
10y ago
I started here http://worrydream.com/AlligatorEggs/ . Great intro article and my favorite visual explanation. The alligator system helped me visualize the dynamics of the system. However, about 3/4 of the way down,
543.
▲
by
lopatin
10y ago
Thinking about hard problems in terms of lambda calculus. I took a day to read about all that stuff and at some point so many things fell into place. I learned CS theory in school, learned ML, but it's not the same as being confronted
544.
▲
by
lopatin
10y ago
Data declarations via decorators for use by some data fetching layer sounds like exactly what I want. > creates a level of indirection that is intransparent to the component user, and I imagine stacking several of these decorators on top
545.
▲
by
lopatin
10y ago
How did you finish the list? I'm still processing the last two items.
546.
▲
by
lopatin
10y ago
I totally agree. Docker feels really tidy conceptually. I ended up somehow convincing myself that adding this extra layer of technology into my (relatively tiny) infrastructure will decrease it's complexity. Unsurprisingly, the effect
547.
▲
by
lopatin
10y ago
Do these ads really seem like they would perform worse than typical banner ads? You're right that accidental clicks may happen more often, but you don't pay per click. You said that "nobody wants them, everybody ignores them&
548.
▲
by
lopatin
10y ago
For basic forms, where you're not doing something weird, why would intermediate form state need to live in Redux? Local React state seems best for that.
549.
▲
by
lopatin
10y ago
Must be prepared for rust...y dance moves
550.
▲
by
lopatin
10y ago
Vacuum React is all you need for a small scale, real world app. Ok, granted at some point you might want to pass your build through Browserify and Babel. No worries, both of those things are one liners in bash. On the other hand, if you spe
551.
▲
by
lopatin
10y ago
React is simple, not complex. Simplicity is like the main benefit of using React if your intention is to build a single page app. If that's not what you need, then yeah, use Rails.
552.
▲
by
lopatin
10y ago
If anyone is planning on building a semi-ambitious web system soon, you should evaluate Go. It's kind of scary how productive it allows me to be now. All of the following benefits, of course, may not apply to your project but I wanted
553.
▲
by
lopatin
11y ago
Looks like a lot of schema migration talk here. Out of curiosity does anyone have production experience with lazy migrations for serialized data? Where your model migrations exist as code: an array of functions that convert one version of t
554.
▲
by
lopatin
11y ago
I started out with simple flex, then moved to a flex based grid library because it solves subtle gutter/margin alignment issues that appear with out of the box flex rows.
555.
▲
by
lopatin
11y ago
The way I like to put it is that stateless components are great because they don't have a mind of their own. Stateless components have one responsibility, and that is to encapsulate all of the UI details of a component, but not the fun
556.
▲
by
lopatin
11y ago
Sorry if I missed it, are there links to any kind of further reading or discussion regarding what Ben Alpert (spicyj) mentioned about implementing layouts in React? I do a lot of render -> dom-measure -> re-render and it's not th
557.
▲
by
lopatin
11y ago
I agree that it's necessary to pin dependency versions down somehow. So I commit my Go dependencies into my project's version control. I heard Google does this internally too, but I can't confirm that. But I can say that I&#x
558.
▲
by
lopatin
11y ago
I dunno about checking in the build directory. Having a working version of the build in the repo isn't necessary when your dependency versions are locked in shinkwrap.json. Therefore your build is completely reproducible. As for elimin
559.
▲
by
lopatin
11y ago
Uh ok let's say "a thorough understanding of the rest of the function" instead. Does my question make more sense? The reviewer (human or computer) needs to follow the logic of the function, understand the true purpose of the
560.
▲
by
lopatin
11y ago
I read it and it's a great overview of the different kinds of bugs that happen in the real world. Certainly more examples than the article provided. But your comment seems to be focused more about how a good language with a proper type
561.
▲
by
lopatin
11y ago
One thing that I don't get from the article is if it can really catch my logical bugs. And I'm not trying to bring this research down because I don't doubt the results, but I am curious, and a bit skeptical, if this is a true
562.
▲
by
lopatin
11y ago
Exactly. I'm only able to write such powerful React components by having a full programming language (JS) in my view (the React render method). The logic-less template approach would have been crippling for me.
563.
▲
by
lopatin
11y ago
Depends on what kind of component just updated. If it's a low level text field, it probably shouldn't broadcast the change to anywhere else in the program. Instead it would invoke it's 'onChange' callback. This way,
564.
▲
by
lopatin
11y ago
Eh, people build what they're gonna build. Pay it no mind, if it fatigues you. I do agree with your point about building more APIs btw. Just not necessarily less dashboards.
565.
▲
by
lopatin
11y ago
It's less of a language issue and more of a framework/ecosystem issue, which is what I think the original commenter meant. The Node.js community is much more fragmented than Python. At least when it comes to web frameworks. Everyo
566.
▲
by
lopatin
11y ago
It looks like all the comments by VeilEm are deleted now, which is unfortunate. No matter how controversial or indelicately phrased, you expressed frustrations with an open source project that no doubt also have and I think you should stand
567.
▲
by
lopatin
11y ago
Got it, thanks. Would it have been easier for you as a dev if they made this a minor version bump rather than a major version? Given that the code and documentation changes would have been the same.
568.
▲
by
lopatin
11y ago
Could you elaborate, for a layman, on why their decision to make 2.x backwards compatible with 1.x doesn't follow semantic versioning rules?
569.
▲
by
lopatin
11y ago
I put my components into app/components. This is the one, true directory structure. All other directory structures are wrong. \s
570.
▲
by
lopatin
11y ago
You say it's about maintainability. Well, that's the whole point of frameworks. Your team grows, your app gets bigger, time to add some more structure to your code. Extract the common patterns into re-usable modules. Enforce conve
More ›