Live data from Hacker News

Ask HN: What are you working on?

news.ycombinator.com

51–60 of 252 posts

Re: Ask HN: What are you working on?

#51
post #7

Earlier quoted context omitted.

But then what would he use for the voltage source, + and - 4.5V? It appears he wants the + and - 9V available for the amplifier. But my EET is extremely rusty.

The 5 V from the USB. Leave the opamp with it's ground connected to the joint between the two resistors, choose the bias so it drives the output from the -2.5 V the opamp sees (which really is the 0 from the computer) to the +2.5V (which is the +5 of the computer).

I'm only giving the circuit a cursory look, but I thought he wanted a 9V reference voltage added to the sensor voltage going into R7. But I guess a lower reference voltage may be adequate too.

Re: Ask HN: What are you working on?

#55
Brick and Mortar startup, with online enhancements:

Currently in the process of purchasing an art gallery space in Denver, which we will renovate, and hopefully open in the fall of 2010. (Would be sooner, but we are having a baby in the spring.)

I intend to have an exhibition every 3 months that will seek to blend technology with a physical installation of some kind. Details TBD, based on online collaboration -- The web site will spend the 2 months between exhibitions working towards collaborating on the next exhibit. Each collaborator will hopefully be able to visit in person, to create a true blending of online and physical life.

Re: Ask HN: What are you working on?

#57

Building support for matrix datatypes and operations (arithmetic, eigenvalues, and factorization) in PostgreSQL. I think I will use the Gnu Scientific Library, but I am still looking around at options with looser licenses.

Try LAPACK. Incredibly fast, and a minimal license. You'll have to deal with FORTRAN, though.

Re: Ask HN: What are you working on?

#58
Compiling our JVM language (Gosu) down to bytecode. It's slow going; the bytecode side isn't hard, but the language has been evolving for 7 years or so and has all sorts of obscure edge cases, as well as some looseness in the semantics that has to be tightened up in bytecode, so getting every little detail right so all the existing code still runs 100% correctly is difficult. We're still hoping for an initial open source release some time between probably June and September.
Post reply on HN