Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
thedaniel
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
The New and Improved Atom Flight Manual
(blog.atom.io)
10 points
by
thedaniel
11y ago
|
0 comments
32.
▲
by
thedaniel
11y ago
Along those lines, it would be wonderful if someone would write a coffeescript implementation that output clean, idiomatic ES6 rather than ES5!
33.
▲
by
thedaniel
11y ago
We've been working on Atom for a long time. I think that CS was a great choice when it was made some years ago, and I can say that the core team quite likes ES6 (which directly addresses a lot of the same JS warts that CS was designed
34.
▲
by
thedaniel
11y ago
Running `atom --safe` will start the editor with only bundled packages activated.
35.
▲
by
thedaniel
11y ago
Do you provide an export function as well, to prevent lock in?
36.
▲
by
thedaniel
11y ago
It says "See how they are listening to their users" on the home page. Does this imply that not using this tool or not desiring feature voting is the same as ignoring your users? That's some pretty unpleasant positioning IMO.
37.
▲
by
thedaniel
11y ago
I dunno, we're doing OK on Google with "Atom".
38.
▲
by
thedaniel
12y ago
yes: https://github.com/github/git-lfs/blob/master/docs/api.md
39.
▲
by
thedaniel
12y ago
atom-shell absolutely has made the switch to io.js, that's where Atom's node comes from.
40.
▲
by
thedaniel
12y ago
I think you're being overly literal. "The text" is obviously "the meaning" or "the object" to a baby, but it's the same idea.
41.
▲
by
thedaniel
12y ago
And folks are apparently already hacking their in-cabin sounds to sound like higher-performance models! (cf. http://jalopnik.com/someone-hacked-their-bmw-m135i-to-sound-... )
42.
▲
Atom's New Event Subscription API
(blog.atom.io)
18 points
by
thedaniel
12y ago
|
0 comments
43.
▲
by
thedaniel
12y ago
We moved to Ruby 1.9+ quite a while ago with our patched-up Rails 2.3.
44.
▲
by
thedaniel
12y ago
We had already backported a whole bunch of of stuff to 2.3 so hopefully the 3->3.2 transition won't be so terrible.
45.
▲
by
thedaniel
12y ago
We don't. http://readwrite.com/2014/08/14/github-government-ben-balter...
46.
▲
by
thedaniel
12y ago
I want to agree with the sentiment about the human side of versioning being unreliable, but when the author "pins" the argument on the fact that pinning all versions is "annoying" s/he loses me. Pinning (and vendori
47.
▲
by
thedaniel
12y ago
> First, that is a low blow linking to others doing it. I thought the same thing at first, but the users that are linked to are all big, big names that get millions of plays on Soundcloud that will never get takedowns, whether they have
48.
▲
by
thedaniel
12y ago
How fundamental are we talking here? Is npm still going to be a couchapp?
49.
▲
by
thedaniel
12y ago
It is pre-1.0, and only official builds are provided for OSX so far. That said people are having a lot of luck getting things working on disparate configurations so I am feeling optimistic about the progress of lin/win!
50.
▲
by
thedaniel
12y ago
Yeah, no conspiracy here. Sometimes when people say they're going to have a beta to gather information and make an informed decision, they actually do it.
51.
▲
by
thedaniel
13y ago
licecap
52.
▲
by
thedaniel
13y ago
The download is only available for Mac today, but we are working on the Linux and Windows builds.
53.
▲
by
thedaniel
13y ago
> an automatic language detection model that the developer has zero control over Pull requests welcome :) https://github.com/github/linguist
54.
▲
Cryptography in the Browser
(blog.opal.io)
78 points
by
thedaniel
13y ago
|
83 comments
55.
▲
by
thedaniel
13y ago
If you use the "fixes #7" syntax in a branch commit, the issues will be closed only when that branch is merged to your default branch (usually master). I realize that this is only part of what you desire, but it's a useful re
56.
▲
by
thedaniel
13y ago
"But I read an outsourced rebranding that came in nicely wrapped up, even with legalese in appendix A." I can assure you, your read is wrong. This work was done by GitHubbers collaboratively and painstakingly.
57.
▲
by
thedaniel
14y ago
The maintenance commitment cannot be understated. If you add some kind of processing to a file format, people are going to expect it to always be there, and always work, so you're taking on an eternal renderer maintenance workload. That sai
58.
▲
by
thedaniel
14y ago
What browser/os? This is how it looks for me on mac chrome: http://cl.ly/image/271T2o3w1v0V
59.
▲
by
thedaniel
14y ago
This is great - I can't wait to dig in and think about it in the context of software development.
60.
▲
by
thedaniel
14y ago
I have a developer unit and can confirm: it's legit. I don't want to go into too much detail because of the developer agreement, but think it is best characterized as like a "useful, portable, affordable, easy to integrate kinect". I'm havi
More ›