HN user

joerick

59 karma
Posts3
Comments29
View on HN

I have a Focusrite Saffire that has lots of nice, quiet preamps and ADC channels. I managed to get an old Mac to connect over FireWire and using the Focusrite Control app, I configured the routing to map all the analog inputs to ADAT. That works great but it's always at the wrong sample rate, and I can't change that without getting the old Mac out. Maybe I'll look into one of these rPi shields too. Anyone got any reverse engineering tips for the control protocol?!

Uncertain<T> 11 months ago

I've been wondering for a while if a program could "learn" covariance somehow. Through real-world usage.

Otherwise, it feels to me that it'd be consistently wrong to model the variables as independent. And any program of notable size is gonna be far too big to consider correlations between all the variables.

As for how one might do the learning, I don't know yet!

Interesting, but your hypothesis assumes that 'tone' is one-dimensional, that there is a single axis you can remove. I think tone is very multidimensional, I'd expect to be removing multiple 'directions' from the embedding.

The thing that puzzles me about embeddings is that they're so untargeted, they represent everything about the input string.

Is there a method for dimensionality reduction of embeddings for different applications? Let's say I'm building a system to find similar tech support conversations and I am only interested in the content of the discussion, not the tone of it.

How could I derive an embedding that represents only content and not tone?

The touchscreen might be better than you're giving it credit for. Direct interaction (vs the indirectness of mice, keyboards, gesture) is one benefit that I can't see done better any other way. I think people will always have some kind of handheld touchscreen as a result.

Vue 3.5 released 2 years ago

Biggest functional difference is that Vue's reactivity is built on Proxy objects, which lets you simply bind your view layer to your model layer and things just keep in sync, without any extra APIs to think about. React has useState which gives you a setter that you need to use with an entirely new object each time. In Vue you can just change a property deep inside the model layer and the view updates.

That's what's keeping me in Vue primarily. I think MobX does something similar in React but the API is clunkier than Vue.

On top of that, the API is just much nicer. None of the confusing functional language and concepts e.g. "what exactly did the programmer intend by this 'useEffect' call??"

I've been thinking for a while that digital photos should include a signature derived from a hardware key on each camera. That at least would prevent people lying in metadata, and give us some means to verify. If I trust Canon's signature, I trust that these pixels were taken by a camera.

If a project is really mature, reusable components in design tools can work. But for early stage stuff, they can quickly prove more trouble than they're worth.

The designer's job is to think creatively, on behalf of the user, through the entire system, the states, the transitions. Faffing around with reusable components gets in the way of the right kind of thought, IMHO. It's like the design version of big complex class hierarchies. Done too early, they will really slow you down.

Figma made a mistake including the absolute positioning in their Dev mode. It's never useful, and leads to confused engineers like this.

Figma is a design tool. It is used by designers as a way to build the visual mocks of software. It's not building HTML under the hood. As a frontend engineer, I have to interpret the designs given to me and translate the layouts into something that will be responsive, cope with different data, etc. that part is the job of a frontend engineer, and so far there is no tooling that solves that.

The Figma dev mode helps shortcut some of that work, by providing easy copy-paste for attributes like background, border, fonts, spacing etc. it's a timesaver. But you should never copy the whole thing.

This is awesome! I noticed on the 'Experimenting with lines' section, when smoothness is low, warp is high and length is high, that the lines end up mostly coalescing into big roads. It reminded me of ants forming paths, but it's interesting that this required no communication between the lines. Is this a particular feature of the noise function or does it always do that?

This is confusing. The response to a raw Ethernet frame is JSON containing "https_response" Why drop down to a layer 1 Ethernet frame when the response is specific to HTTP?

While I support the cause, HTTPS is the biggest thing obsoleting old devices in my experience.

Currently hitting this with an old eink project that's based on an obsolete ereader. I wonder if there's some kind of proxy I could connect to over HTTP that does the modern HTTPS on my behalf. (I'm aware of the security implications, just want it to get a tweet/weather forecast)

Objective-C, Mac

Mixim [getmixim.com] | London, UK

Looking for an Objective-C developer (full-time, part-time or contract) to work on a brand-new collaboration service for musicians on the Mac. Email me (Joe, Lead dev) at joe@getmixim.com with a CV.

One thing I've never understood is why we have to shift computer time to match celestial bodies. We have a definition of the second (in terms of a Caesium atom) and we've agreed on the epoch, so why can't we just leave it be?

I understand that if we want to know the time in 'human language' (in terms of the earth's rotation around the sun, and the specific timezone that we're in) we then have to apply these corrections. Surely that's simpler than every timekeeping device on the planet having to adjust a second? Electronic devices are much more likely to be sensitive to a second's difference than us humans are.