HN user

tritchey

153 karma
Posts2
Comments37
View on HN

Not a coincidence. Adonit manufactures the Ink & Slide for Adobe, and apart from some cosmetic differences, and an additional button, the JTPP has all the same functionality as the Ink.

Definitely, that is what we hope developers will start using it for. We expose the accelerometer data in the SDK, so developers can get access to the data. We also use the relative pen position to the iPad to sort out some offset issues to make sure the line appears to be coming from the tip itself.

The touch pressure for paper is done with a new touch Radius property. The radius property on touches was available as a private API, but only made available publicly in iOS 8.

The Ink and Adonit touch pixel point, which are basically the same (We manufacture the Ink and Slide for adobe) use a pressure sensitive tip in the pen itself, and communicate that pressure over Bluetooth. This gives you a much higher resolution on the pressure, with the trade off of the BT stack latency.

I'm sliding down the other side of that distribution myself.

One evening I was having dinner with my wife and her nearly 70 year old parents. Her mom made a comment that has stuck with me:

"You know, we still think and feel the same way we did when we were your age."

Ditto on the above lists. Similar to inter-app communication issue is some way to meaningfully work with documents and data outside of application silos, either to share documents between apps, or to get documents onto and off the device.

We recently launched a simple website monitoring app for the iPhone where we ping sites from our servers, and send push notifications when we detect something is wrong (a poor man's pagerduty or pingdom where you do everything from your phone and can subscribe using IAP).

Probably the biggest lesson we've learned from collecting data on latency and timeouts from our backend is that there are a LOT of very poor hosts out there. Trying to strike a balance between intermittent failures, and actual "Your site is down, you need to do something" is pretty difficult, unless you are willing to simply wait long enough. We'll regularly see timeouts from places like Tumblr and Github Pages--they never go down, but things can get spotty. We can also tell when certain hosting providers are doing their weekly backups (or something - just guessing) because things will just go to pot at the same time every weekend for about an hour.

I can second the S3/CloudFront recommendation. Pretty rock solid (modulo downtime in specific regions).

For anyone curious about the app: http://vigil-app.com

If it is related to manufacturing, then absolutely. My neighbor works for a Honda supplier, and one day had to drop everything and fly from Indiana to a plant in Brazil with a replacement for some part of the assembly line. It is surprising how quickly a supply chain disruption can ripple through the entire manufacturing line. These organizations track things in hours and minutes.

I've seen the current software patent debacle compared to a nuclear standoff. Reading this article made me think of another analogy: Gangs. How long until independent developers will need to either join the Bloods or the Crips in order to fall under the umbrella of their protection? Unless you are a paid-up member of the Apple or Google development programs, you are a potential victim of random drive-by-lawsuits. Even if you are a member you may get shot at, but the gang will retaliate on your behalf.

"a Swiss hosting company leasing blade servers"

If they are truly blade servers, then they were possibly sharing the same chassis, power supply and backplane. Could the FBI have pulled just the blades in question? Possibly. But I can very easily imagine the entire blade chassis being viewed as a monolithic component that they would want to be able to perform whatever forensic analysis they are planning. They could also have pulled whatever blades they were not after, and left them, but until you replace the chassis, you are dead in the water.

The end of Facebook 15 years ago

My comment would be that the author is conflating growth in users and page views to revenue growth. While the two are very highly correlated, they are not the same thing. How Facebook monetizes its users and page views doesn't have to be a 1:1 relationship. The question should be how Facebook will derive ever more revenue from each user over time. Slowing user growth is certainly an easy proxy to use in lieu of real revenue numbers, but it is a gross oversimplification.

Consider how destructive this kind of attitude is toward the programming profession. By trivializing any project, a programmer is by extension making it seem like programming is easier, and cheaper, than it really is. What starts out as an ego-pumping "hey, I'm smarter than THAT person." turns into a devaluation of the work we all do, all to fulfill some desire for acceptance among non-technical peers. You wouldn't pick the brain surgeon that told you he could get the job done in a fraction of the time his colleagues could muster.

I'm starting to wonder in how many ways I can screw up a 10 question survey. Thanks for the feedback. I had 5 other people proofread the survey and you are the only one to catch that.

There are a couple things we are looking at, but it basically boils down to filtering/buffering as much in the hardware adapter before shifting it to the phone on demand. Realistically, the product won't be able to do full line-speed Gbit dumps for extended periods of time, but for simple network scanning/troubleshooting, hopefully it will be adequate.

This article would be a lot more amusing if they took the opposite angle: "Times of economic growth obscure the fact that a large percentage of Americans graduate with no practical skills, and still get decent paying jobs."

I think I can paraphrase:

"Through careful academic research, we've decided what constitutes a smart, well-adjusted individual, but society is not rewarding us, err, I mean them, with material wealth—this unequivocally exposes inequities in the system."

Heck, it is only because my wife has a career, and a steady job, that I've been able to spend time exploring startup opportunities. I can do my work anywhere as long as there is a decent internet connection.

Well, FWIW, I am presenting at DEMO this year. We do actually have a video link right on the front page of our web site, and yet he claims that only one did, and the one he linked to wasn't us. http://paragent.com

I was tempted to post a comment, but I would rather avoid directing his vitriol directly at our company at this point. DEMO is a HUGE commitment for us. 18K is nothing to sneeze at, and a substantial part of our budget. However, living in the midwest, it is very difficult to form the kind of relationships that occur naturally on the east and west coasts. DEMO is an opportunity for us to meet face to face with many people we otherwise we never get to meet, and have some chance of attracting attention. Who knows if DEMO will have been worth it - I'll let you know after it is over. Undoubtedly, it will either end up in a best-of or worst-of compilation.

For most of Kentucky, I'd probably agree, but Lexington is actually a very nice city. I lived there for a few years while my wife was getting her PhD at UK. There is a LOT of money knocking around the area, mostly around horses, but it filters down into the entire feel of the city. UK also has a pretty vibrant tech community. Obviously it is no Boston or Palo Alto, but I'd move back there in a heart-beat.

Waiting for approval to join the ranks of iPhone application developers is made even more frustrating when you see the App Store spammed with 99 cent "ebooks"

We do much of our web development at http://bitfauna.com in Lisp. Most of our clients don't care what language we use, and wouldn't know Lisp from Ruby or Python. At the end of the day, the client cares about whether the site is a) working b) economical.

Lisp is not all we end up doing for clients, and we have the odd job where we maintain and update legacy applications in C# or ColdFusion. But, we have never found an issue using Lisp for new projects.