Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cortesi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
cortesi
11y ago
I've been using Atom full-time for about a year, after switching from Sublime. I'm happy with it as an editor, and like the momentum behind the plugins ecosystem. Performance has been completely adequate, and I've seen none o
62.
▲
by
cortesi
11y ago
Well, first, I think it's perfectly fine to have multiple takes on the same problem space. This is how we progress - people try different things, and we gradually figure out what works. Live-server does a specific set of things, and de
63.
▲
by
cortesi
11y ago
I'm moving in a similar direction for similar reasons - but by shifting functionality out of the node ecosystem altogether. I recently released devd, a small, dev-focused HTTP server with build-in livereload which has taken the place o
64.
▲
by
cortesi
11y ago
This matches my experience with react-router. I use it in a few side projects, and I have the feeling that there's been a lot of "design-thrash" - every new release seems to bring a new interface and new ways of doing things,
65.
▲
by
cortesi
11y ago
Nearly all of them, depending on what exactly you're looking for. Simple things like being able to exclude results from forked repos can save a huge amount of time, and being able to limit results by language, creation date and even nu
66.
▲
by
cortesi
11y ago
Github search does many, many things you can't trivially recreate through a Google search: https://github.com/search/advanced You can access all of this functionality with ghrabber. One of my suggestions to Github
67.
▲
by
cortesi
11y ago
I published a tiny script that makes mass grabbing of files from Github easy ( https://github.com/cortesi/ghrabber ), and wrote about some of the interesting things one could find with it. For example, there are hundred
68.
▲
by
cortesi
11y ago
Intelligence is the wrong word in this case. These are complicated emergent behaviours that arise from extremely simple rules applied locally and iteratively by each individual. There's no planning, forethought, or central driving will
69.
▲
by
cortesi
11y ago
The world of social insects is filled with ideas for tackling resource tradeoffs of this sort. These are usually not signs of "collective intelligence", as much as they are a manifestation of good algorithm design, honed by aeons
70.
▲
Trawling GitHub for cookies, bookmarks and browsing history
(corte.si)
11 points
by
cortesi
11y ago
|
4 comments
71.
▲
by
cortesi
11y ago
No problem! Hope it was useful.
72.
▲
by
cortesi
11y ago
It's worth thinking carefully about what you expect to gain from Open Sourcing code, before you do it. One of my projects ( https://mitmproxy.org ) is pretty widely used commercially (both as a tool for analysts, and as a bac
73.
▲
by
cortesi
11y ago
Devd doesn't appear in my gulpfiles at all, actually. Gulp literally just renders to disk. I then start devd separately with the appropriate livereload flags to handle the service end of things. For instance, here's a devd command
74.
▲
by
cortesi
11y ago
Slinky looks very neat! I do feel it inhabits a very different niche from devd, though. I have no ambitions for devd to compete with tools like Grunt, Gulp or Slinky. Devd has a simple job: it just serves files and triggers livereload when
75.
▲
Devd: a small, self-contained web daemon for developers
(corte.si)
229 points
by
cortesi
11y ago
|
34 comments
76.
▲
by
cortesi
12y ago
Right - these are the frequency dot plots I first saw in Greg Conti's work (some examples here: http://sebug.net/paper/Meeting-Documents/BlackHat-USA2008/BH... ). They're definitely on the way. Regar
77.
▲
by
cortesi
12y ago
Frequency analysis and byte dot plots are definitely on the way. Do you have a concrete example of the digraph frequency feature you can link me to? Any other feature suggestions are welcome too.
78.
▲
by
cortesi
12y ago
Author of the post here. I'm working on a browser-based interactive analysis tool based on these visualizations. It's nowhere near ready for release, but those who are interested can find a demo here: http://binvis.io
79.
▲
by
cortesi
13y ago
Thanks for the heads up. We'll track that down.
80.
▲
by
cortesi
13y ago
We're looking at the sound set bug right now. Also, see my other comment about the intrusive sounds. We plan to have some demo streams tuned for real-world use (i.e. not as alarming) soon.
81.
▲
by
cortesi
13y ago
Apologies! The demo is tuned to be way more intrusive than a real-world data stream would be. Our theory is that if we have people's attention for 15 seconds, we should show them the full range of sound intrusiveness. Hope it wasn'
82.
▲
by
cortesi
13y ago
There are so many possibilities. A few weeks from now, we should have the ability for users to create, edit and share their own soundpacks.
83.
▲
by
cortesi
13y ago
I'm somewhat late to the party, but I spent some time playing with procedural colour picking using space-filling curves (the Hilbert curve in particular). I describe the basic technique here: http://corte.si/posts/
84.
▲
by
cortesi
13y ago
I certainly don't want to give the impression that we're unaware of the long history of auditory display projects. In fact, it's my reading in these areas that resulted in this project. Keep an eye on my blog for some posts d
85.
▲
by
cortesi
13y ago
When we began, the idea was to synthesise everything, and have many perceptual variables to play with. Then we realised that we could validate the idea using pre-rendered sound snippets. We'll turn back to something more sophisticated
86.
▲
by
cortesi
13y ago
Have a look at my co-conspirator's blog post about Choir: http://alexdong.com/choir-dot-io-explained/ We definitely see Choir fitting in where you can't look at or interact with a screen. Cars and wearable co
87.
▲
by
cortesi
13y ago
It's not just you - the GitHub demo is a tad annoying. The idea was that we might have people's attention for 15 seconds on average, and we wanted them to get a feel for the full spectrum of sounds in that time. So, it's tune
88.
▲
by
cortesi
13y ago
Yes, absolutely. My initial idea was to synthesise all the audio ourselves, using a native desktop client and libpd. Then I realised that we could test 95% of the idea using web audio and pre-compiled sound snippets. And here we are. Contin
89.
▲
by
cortesi
13y ago
I've added Mixpanel to our list of proposed integrations. We'll get round to all of them in time. That feeling of being in touch with your applications and servers that you experienced at Dropbox is _exactly_ what we're aimin
90.
▲
by
cortesi
13y ago
Fix will be inbound shortly. We've had a bit of an unexpected bump in traffic today, and we're waiting for our moment in the sun to fade before we revamp things.
More ›