Recent submissions

Comment · 1 year ago
Comment · 9 years ago
Comment · 10 years ago
Comment · 11 years ago
Hi! I'm having trouble with both of these.

https://github.com/Microsoft/vscode/issues/95 https://github.com/Microsoft/vscode/issues/81

Also can you comment on why a jsconfig.json file is needed, as opposed to some in-editor setting, or reading from the config files the user already has installed, like an .eslintrc?

Comment · 11 years ago
If your branch conflicts, rebase off master (the branch you're making a pull request to). Then it will merge cleanly. There's no practical downsides to having merge commits in master, but you should never (or rarely) see merge conflict resolution commits. You should be able to rebase to a mergeable state before merge.
Comment · 11 years ago
I've always heard good things about Vue from its users. I have to compare all Javascript frameworks to React, because to me React feels like the first framework that got it "right." The API of React is surprisingly thin. Looking at Vue templates, the syntax seems quite alien, halfway between Django and Angular:

    <th v-for="key in columns" @click="sortBy(key)" :class="{active: sortKey == key}">
And the API seems to needlessly separate HTML and Javascript, with some strange (to a newcomer) API calls:

    Vue.component('demo-grid', {     // moving away from JS classes
        template: '#grid-template',  // Why separate view code from view code?
        replace: true,               // what is this?
Has anyone heavily used React and Vue and have an argument for what this thicker API affords?
Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
This seems to take the declarative nature of SVG and make it more imperative, like HTML5 Canvas, even though it ironically uses a virtual DOM implementation under the hood. For my React projects I chose SVG over canvas because I could write my layout declaratively, and avoided imperative manipulation libraries. How do you modify existing SVG shapes with this library?
Comment · 11 years ago
Remove the ?currentPage=all from the URL to get the non-broken version of the link.
Comment · 11 years ago
This may be a silly question, but could you elaborate on why you prefer the project to be open sourced? I'm keeping it closed source now for potential business and security reasons.
Comment · 11 years ago
All shaders are beautiful :)

This is a problem with user content submitted sites. It's hard not to conflate the quality of the content (shaders) with the quality of the product (ShaderFrog). There are no default ShaderFrog shaders, they're all user created.

The more oddball shaders (my favorites) are the composed shaders, which are not eligible to be used as inputs to other composed shaders. Only the basic shaders, which are generally higher quality because they require more knowledge of how GLSL works, can be inputs to composed shaders.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton