You can see that, to some extent, in how the article’s points apply to language and communication in general, not just between Japanese and English. While turns of phrase give your repartee a flavour that sells your point—like what you’re reading now—it’s also a product of your thinking process, and as the article says, could cloud the point you’re trying to make. If you can speak or write clearer, then your points will also become clearer to yourself. That’s follows my experience, since I speak a lot of German for work. In German, I must think carefully about each point I make, otherwise I’ll run into a sentence for which I don’t know the words. I endeavour to respect the language and culture, and in doing so put effort into making my points simple enough for me to reach for the right words and phrases to show this respect (at least, I try!)

For a good example: David Sylvian collaborating with the late Ryuichi Sakamoto. You can see them writing ‘Blue of Noon’ in the Brilliant Trees sessions on Vimeo/Youtube. David talks about his use of really minimal language to get musical structure and points across, since Ryuichi’s English wasn’t yet as perfect in the 80s as it was later on. You see this directly in the session videos. What’s truly the best about it, is the respect they show for each other.

Bad example (potentially): Aston Martin F1 collaborating with Honda on the new F1 engine :-) . After several years of extensive development and billion-dollar investment, today they’re at the back end of the grid, more than 3 seconds off the pace. According to recent rumours, as recently as November, the Aston Martin F1 bosses visited Tokyo to discuss progress of the engine that had been in development for a few years, apparently having hardly visited before, and were shocked to learn that only about 30% of the original workforce from Honda's previous venture in F1 remained. It seems they didn't even know how far behind schedule Honda was! For projects as large as F1 car development, it’s unfathomable that this mutual curiosity, which in effect is a form of respect, apparently wasn’t there.

- the necessary basic electronics;

- PCB design;

- 3D CAD;

- your particular iterative process,

among other things? I get the impression you built things incrementally, observed what happens and learnt via that feedback loop? Maybe others could share their own feedback loops, too.

As for fully integrated optics, it's where quantum computers eventually want to be, and there's no physical limitations currently. But perhaps it's too early to say whether we would absolutely require free space optics because it's impossible to do some optics thing another way.

With quantum computing, one is forced to use lasers. Basically, we can't transmit quantum information with the classical light from LEDs (handwaving-ly: LEDs emit a distribution of possible photon numbers, not single photons, so you lose control at the quantum level). Moreover, we often also need the narrow linewidth of lasers, so that we can interact with atoms in the way we want them to. That is, not to excite unwanted atomic energy levels. So you see in trapped ion quantum computing people tripping over themselves to realise integration of laser optics, through fancy engineering that i don't fully understand like diffraction gratings within the chip that diffract light onto the ions. It's an absolutely crucial challenge to overcome if you want to make trapped ion quantum computers with more than several tens of ions.

Networking multiple computers via said optical interconnects is an alternative, and also similarly difficult.

What insight do i gleam from this IEEE article, then? I believe if this approach with the LEDs works out for this use case, then I'd see it as a partial admission of failure for laser-integrated optics at scale. It is, after all, the claim in the article that integrating lasers is too difficult. And then I'd expect to see quantum computing struggle severely to overcome this problem. It's still research at this stage, so let's see if Nature's cards fall fortuitously.

Comments URL: https://news.ycombinator.com/item?id=43957231

Points: 62

# Comments: 12

I think that's the real key to this stuff: what makes these things actually sound good?

I was using the demo just now: the sounds you get out of this are actually better than I expected! And I see what you meant in the videos about intuitive editing, rather than abstract.

Although, I was often hitting 100% CPU with some presets, with the sound glitching accordingly. So I could experiment only in part. I'm on an M1 Pro; initially I set 128 buffer sample size in Ableton but most presets were glitching, I then set to 2048 just to check for improvement, which it did, nevertheless it does seem a bit high. Maybe my audio settings are incorrect? I can give more info later if it helps you.

Remind me of Korg's Berlin branch with their Phase8 instrument: https://korg.berlin/ . Life imitates art imitates life :)

I highly support and encourage this. Is there a way I could contribute to Anukari at all (I'm a physicist by day)? These kinds of advancements are the stuff I would live for! However I should stay rooted in what's possible or helpful: I'm not sure if this is open-source for example. As long as I could help, I'm game.

I looked up any connection to ARTIQ they may have: it seems they do full stack QC, as they have their own quantum compiler [1]. But I'm not really sure what they're doing currently.

[1] https://github.com/quil-lang/quilc

What's the fundamental physical limits here? Namely, timing precision, latency and jitter? How fast could PyXL bytecode react to an input?

For info, there is ARTIQ: vaguely similar thing that effectively executes Python code with 'embedded level' performance:

https://m-labs.hk/experiment-control/artiq/

ARTIQ is quite common in quantum physics labs. For that you need very precise and determining timing. Imagine you're interfering two photons as they reach a piece of glass, so that they can interact. It doesn't get faster than photons! That typically means nanosecond timing, sub-microsecond latency.

How ARTIQ does it is also interesting. The Python code is separate from the FPGA which actually executes the logic you want to do. In a hand-wavy way, you're then 'as fast' as the FPGA. How, though? The catch is, you have to get the Python code and FPGA gateware talking to each other, and that's technically difficult and has many gotchas. In comparison, although PyXL isn't as performant, if it makes it simpler for the user, that's a huge win for everyone.

Congrats once again!

It loads quick, and works with large data. Crucially, you can view and edit visually, not only programmatically.

Assuming those already working with such data have Excel and Python tools etc., the pitch here is that the $39 license fee saves time or effort. So, is it that the user can spot and correct errors that you couldn't otherwise do with either Excel or with other big data tools? And/or otherwise do the necessary data manipulations?

I came across the phrase 'eyes like a shithouse rat' recently, to describe the people doing final checks at a printing press. I think there's probably plenty of people out there who would pay $39 for eyes like a shithouse rat.

Also the website makes me nostalgic :)

As an example, Hamamatsu Photonics has been in the optics field a long time, and is going hard on developing for quantum physics applications. It's refreshing, since pretty much every company in quantum computing is very young, so hasn't had the time to build that craftsman vibe yet. Of course, there are people who've been working on quantum information technologies for a few decades now.

I look forward to seeing this ethos developing in quantum, for sure.

How?

I fully agree with what everyone else is saying here, it's really great advice. On the science aspect, their advice has you well-covered. From myself, I emphasise: the most important part of ingredient of your PhD, other than you, will be your prospective advisor. The choice of school is secondary to that.

My two cents: consider how well you will get on with your supervisor. Meet them, their students (past and present), their departmental colleagues and friends if possible. Get a feel for them, a vibe. Even the people who don't love them very much will give you an idea for what this person is like in just a few hours. Imagine: if this is what your supervisor will be like for one day, can you imagine being with them for several years? In this respect, it's like a long-term relationship, with one massive difference: if a (romantic) relationship goes south after a few years, you can break up, but for a PhD if you quit halfway you could end up without a piece of paper to show for it. You will then have to weigh up that possibility with the effort needed to continue, which drains from and adds a hefty cost to all parts of your life. I've seen this 'crossroads' occur for many people who left halfway.

To drive home the last point: my personal experience is such that I literally cannot think of anyone who's had a tougher PhD journey than myself and still managed to complete it---I'll concede that I'm biased, naturally. Backing up that statement: statistically speaking, across my department I don't think anyone in the whole Oxford Physics department fell in the same hole that I did for at least 20 years. I need not go into details, but if pressed, you could ask me directly (this is my first post on HN, I would have to figure out how to respond). Be cautious about the life aspect of the PhD, not just the science itself, is my point.

Also be aware of the life outside of your work. This is the point you highlight in your original question: it's great that you do. Specifically, the location matters since it defines your environment. For your PhD to work out, you need not just a support network but an environment in which you can succeed with as little effort as possible. Your hard work then compounds from there. You want to be able to get home/go out on the weekends and recover energy after your work, not drain it. If your PhD work takes your energy and you can't get back your energy or recover it, that's bad. Same goes for the work itself though, meaning your work should motivate you and give you energy too. Imagine, what will your evenings and weekends be like if you were in exactly the same place but didn't have any PhD work at all. Would you still enjoy it? Ultimately this decision is a personal one, and you have to use and trust your judgement. If you don't feel 100% confident to answer that, talk with others about this point before moving forward. It's difficult to get a feeling for this experience, so you need to be armed with quality advice.

Note that a PhD is a hard journey and a life-changing experience. Of course, it's about your life. There's lots of negative things to say about the experience, but I'll end positively: my PhD has completely opened my world to experiences that I wouldn't have been able to dream of otherwise. I simply wouldn't have known such things exist. It's broadened my horizons in a similar way to like someone moving from the island of Nauru in Oceania to Bay Area SF would experience. So, do what makes you happy :)

Good luck!

Footnote: Actually, it's late in Europe at the moment, so to save time I tried to dictate this post using ChatGPT Plus for the first time. It spoke out what I said for 7 minutes uninterrupted and absolutely flawlessly! Then ended with 'Transcript unavailable', and I lost the text. Perhaps this is like 'The house always wins", except there is no house, or winning. So, from now on, whenever I think of AI going forward, I will think: 'The always". Even if it doesn't make sense to anyone, I'm sticking with that thought, it has personality!