HNHacker News
TopNewBestAskShowJobs

jkelleyrtp

2,460 karma · joined September 24, 2018

https://jonathan-kelley.com
submissionscomments
jkelleyrtp··on Dioxus: User interfaces that run anywhere
Dioxus renders HTML. Right now using WebKit, but in the future, its own engine with the same accessibility libraries that power the platform’s accessibility with the layer to get from HTML.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
You can already run Dioxus on an SBC. I’m not sure it’s realistic to run on an stm32 without some real limitations. IMO “everywhere” means everywhere in the physical sense, like desktop, mobile, server, AR/VR, handhelds, etc. we can’t support something like a Pic-8 ever, so it’s not worth trying to qualify that.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
For most platforms relying on the browser’s webview is fine since most platforms ship with a browser! But you can always specify WebKitGTK as a dependency which I think is a one time 2GB cost.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
It uses HTML as the base so accessibility is built right in. As we stray into more custom solutions, then we’ll use accessibility kit, but since in the short term it’s all rendered straight to the DOM, we get it for free.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
The rust docs don’t run UI libraries with any helpful output.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
We’re using tailwind and it looks like the media breakpoint is set for a size too big/small. Should be easy fix!
jkelleyrtp··on Dioxus: User interfaces that run anywhere
Satellite is building their startup’s app with Dioxus!

https://github.com/Satellite-im

Dioxus is still less than a year old, but it’s getting more and more use.

jkelleyrtp··on Dioxus: User interfaces that run anywhere
We’re leveraging the work done by Druid so the plan is to use AccessibilityKit as the foundation. Our native renderer is essentially a GPU-accelerated HTML/CSS renderer so we’ll pull in all the accessibility tech there. We don’t want people to learn anything new to get started, so sticking with web foundations is smart even if it’s not as great as a bespoke solution.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
You can get down to less than 60k. It’s just the average binary that links in various system resources with no size optimizations comes out at around 1.5mb. Tiny for desktop!
jkelleyrtp··on Dioxus: User interfaces that run anywhere
LiveView here describes the approach, not the integration with phoenix. Multi-window support is coming. You can hack it together today, but we’re actively upgrading the core architecture to support multiple renderers per UI tree for declarative multi-window setups.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
On the web, you can get the final bundle down to about 60k gzipped, which is comparable to react.

The average desktop/mobile binary is less than 2mb, but that’s with zero size optimizations to shrink the output. You can certainly get less.

Dioxus runs on a native thread and renderers into the webview, so there’s very little JS footprint and the render resources are shared among all webview on your system.

I haven’t experimented with it, but it’s entirely possible to run on a raspi with webkitgtk. We’re building a native renderer with WGPU and already support rendering to the terminal.

jkelleyrtp··on Dioxus: User interfaces that run anywhere
Creator here - ask away! We added a bunch of new features to master that haven’t been released yet, like liveview, WGPU renderer, instant hot reloading, autoformatting, and more.
jkelleyrtp··on Dioxus: User interfaces that run anywhere
It uses web tech so all the accessibility is built right in!
jkelleyrtp··on US Department of Energy: Fusion Ignition Achieved
There are pictures of CAD and experimental setups for the targets. They’re also pretty open with the setup numbers, so in theory, you could make your own NIF setup and try to get their target designs working.

From what I understand, a lot of the work from the past years has been trying to piece together geometries, pulse timing, stability, and quality of targets.

jkelleyrtp··on US Department of Energy: Fusion Ignition Achieved
> LLNL’s experiment surpassed the fusion threshold by delivering 2.05 megajoules (MJ) of energy to the target, resulting in 3.15 MJ of fusion energy output, demonstrating for the first time a most fundamental science basis for inertial fusion energy (IFE)

Yesterday, everyone was complaining about the 2.2:2.0 ratio, but now we're working with 3.15:2.05.

With modern lasers, that'd be a total Q of 0.375 assuming 100% efficiency through direct-energy-capture.

The jumps to get here included

- 40% with the new targets

- 60% with magnetic confinement

- 35% with crycooling of the target

The recent NIF experiments have jumped up in power. The first shot that started this new chain of research was about 1.7 MJ of energy delivered. Now, 2.15 MJ. However, the output has jumped non-linearly, demonstrating the scaling laws at work.

> I’ve helped to secure the highest ever authorization of over $624 million this year in the National Defense Authorization Act for the ICF program to build on this amazing breakthrough.”

It's nice to see this milestone recognized, even if the funding it still rather small.

jkelleyrtp··on Fusion energy breakthrough by Livermore Lab
1. The same research that brought us the atomic bomb brought us so much more. Who cares about the motivation of the research? This is such a bad take considering the history of technology evolving out of military development.

2. Again, all technology is expensive in the beginning. Who cares? The important thing here is to climb magnitude by magnitude. NIF climbed many magnitudes in recent history, making it notable.

3. As you mentioned, Helion and direct energy capture. D+He3 + DEC might be not feasible with a tokamak, but the scaling laws of fusion (size, current, B field) are in favor of experiments that get close.

4. See 3

5. See 3

6. See 3

7: See 3

I think you have a very negative take on what is an amazing breakthrough accomplishment. Even if the NIF doesn't end up converting their research into a commercial powerplant, they have at least demonstrated experimental viability of inertial confinement fusion. It's only a matter of time before the next generation shows viability of D+He3 fusion and then we'll have even more options.

jkelleyrtp··on Fusion energy breakthrough by Livermore Lab
Before ignition, very little science had been explored in the "burning plasma" regime. Now that ignition had been figured out, an entire new field of experimentation has been opened up.

https://www.llnl.gov/news/three-peer-reviewed-papers-highlig...

In particular, the original article talks about magnetic compression hypothesis being a byproduct of white dwarf simulation. With this new regime, they were able to apply the same ideas to fusion, resulting in the breakthrough.

With ignition being a regular thing in laser fusion going forward, I suspect many groups will have some slightly varied approach or some technique improvements.

If you're into fusion and lasers, there's a lot of areas that are still ripe for magnitude leaps.

- Laser power, timing, materials, and cost

- Metallurgy of the target canister

- Construction of the target and perfecting it as you mentioned

- Absorption of energy

I believe the NIF will focus on #2 and #3 as of course they focus more on making the "boom bigger" rather than making it cost effective of useful. IMO another group (startup or otherwise) will step in as an actual project in this space.

One area to innovate here is to use a different fuel mixture that doesn't produce neutrons. We wouldn't need liquid lithium/lead, breeding, or any of the complexities people very commonly complain about.

- https://en.wikipedia.org/wiki/Aneutronic_fusion

- https://en.wikipedia.org/wiki/Direct_energy_conversion

It's entirely within the realm of possibility that the technique to achieve ignition will open the door for 5:1 or 10:1 q with neutron-free fuels.

Even a total Q of 2:1 or 3:1 is a huge win, and that's within a magnitude of the modern tech.

--

Something I want to mention here too - the easiest aneutronic fuel mixture available is H2 + He3. It hasn't been explored too much since He3 is hard to come by on earth (though you can mine it from the moon!).

But, Helion has patented a way to generate He3 from H2 fusions. We don't need to mine He3 to achieve neutron-free fuels, just need to transmute it from seawater.

jkelleyrtp··on Fusion energy breakthrough by Livermore Lab
Very disappointed by the discourse in this HN thread. The same old quips over and over. "NIF is just a nuclear stewardship program", "it's not actually generating power", "fusion still 30 years away".

I think it's very clear, given the past year that NIF has had, that they are very rapidly approaching a point where we have the tech to "solve" inertial fusion.

https://lasers.llnl.gov/news/papers-presentations

Getting fusion right is done a magnitude at a time. Right now NIF is within 1 magnitude if they built it with modern laser tech. Many fusion designs are 10 magnitudes away or more.

Their most recent article has a ton of great data and next steps:

https://lasers.llnl.gov/news/magnetized-targets-boost-nif-im...

This includes

- Cryo-cooling the main target

- New alloys

- Magnetic compression of targets

The recent advancement that helped reach ignition (in the last article) boosted performance 40%.

The advancement between then and now: nearly 60%.

Within the past 6 months, NIF has nearly doubled energy output of the reaction.

Plus, if you know anything about fusion research, you'd know that energy outputs tend to scale non-linearly with energy input and size. This tends to be on the order of the power 3 or 4. Hence the existence of ITER.

NIF has uncovered some new science, closed the magnitude gap, and made it actually realistic for inertial confinement to be a feasible tech for a power producing plant.

jkelleyrtp··on At SpaceX, work was taken away from me in case I “might retire or die.”
Then SpaceX should've given him headcount to build out his own team.
jkelleyrtp··on Today I Deleted Notion
Agreed. I consider myself to be pretty technical and I explored Github Wikis, static site generators, local markdown, etc, and then Notion showed up one day. I could click to create a new markdown-ish document, collaborate on it with the other people on my team, embed images, write equations, and do way more than I could in any of the other solutions I sorta hodge-podged together.

I don't have time to write notes app, and even if I did, I probably would've made something like notion, but worse.

At this point, I do all of my technical writing in Notion. Equations, tables, nesting, publishing... I can even embed an interactive graphing calculator or videos of my work. A plain markdown file can't do that and neither can LaTeX.

jkelleyrtp··on Single Page Applications using Rust (with WASM)
I felt that yew was pretty verbose so I made a library that's closer to React with hooks.

http://dioxuslabs.com

It's pretty young but solves a lot of ergonomic issues with UI in Rust. It's probably the closest you can get to React-level ergonomics (better in some ways) with Rust.

jkelleyrtp··on TypeScript as fast as Rust: TypeScript++
In http://dioxuslabs.com we share our strings (interned) across the JS/Rust boundary and only send primitives back and forth. All diffing stays in Rust with bump memory allocators managing allocations. The JS side is only there to do DOM manipulation. [1] It's about 3-4x faster than React.

I'd say a lot of the ergonomics are there, but not every pattern has been translated cleanly from React into Rust yet.

[1] https://github.com/DioxusLabs/dioxus/blob/master/packages/in...

jkelleyrtp··on Ask HN: Who wants to be hired? (April 2022)

  Location: Bay Area
  Remote: Yes (prefer in-person or hybrid)
  Willing to relocate: Yes
  Technologies: Rust, TypeScript, Python, Go, C, C++, Lua, Verilog, OpenCL, CUDA, FPGA -- embedded, electronics, hard math/physics
  Email: jkelleyrtp@gmail.com

Resume: https://jonathan-kelley.com/resume

Github: https://github.com/jkelleyrtp

I'm a graduating senior at Olin College of Engineering with a nearly two years of fulltime work experience under my belt. I've built major components and products for venture-funded startups, worked on particle accelerators, and deployed hardware hundreds of feet above the ground on live constructions sites in San Francisco.

My most recent project is http://github.com/dioxusLabs/dioxus - with over 3000 stars in under two months.

My area of interest is software-for-hardware and full stack development that spans the entire stack. I'm looking for a full-time role in either small or big, and I'd be able to provide value extraordinarily quickly. I'd prefer to work with Rust and embedded systems, but can be thrown at C/C++/Python projects just fine.

jkelleyrtp··on Inspecting Web Views in macOS
I’ve been working on this :) https://dioxuslabs.com/
jkelleyrtp··on Goldilocks Zone Finder – Find your ideal climate
NC is a very temperate and beautiful place. Good prices and jobs too. If you live in the middle, both the ocean and mountains are 3 hours away.
jkelleyrtp··on Ask HN: Who wants to be hired? (March 2022)

  Location: Boston (current) / SF / LA / NC / NYC
  Remote: Yes (prefer in-person or hybrid)
  Willing to relocate: Yes
  Technologies: Rust, TypeScript, Python, Go, C, C++, Lua, Verilog, OpenCL, CUDA, FPGA -- embedded, electronics, hard math/physics
  Email: jkelleyrtp@gmail.com

Resume: https://jonathan-kelley.com/resume

Github: https://github.com/jkelleyrtp

I'm a graduating senior at Olin College of Engineering with a nearly two years of fulltime work experience under my belt. I've built major components and products for venture-funded startups, worked on particle accelerators, and deployed hardware hundreds of feet above the ground on live constructions sites in San Francisco.

My most recent project is http://github.com/dioxusLabs/dioxus - with over 3000 stars in under two months.

My area of interest is software-for-hardware and full stack development that spans the entire stack. I'm looking for a full-time role in either small or big, and I'd be able to provide value extraordinarily quickly. I'd prefer to work with Rust and embedded systems, but can be thrown at C/C++/Python projects just fine.

jkelleyrtp··on Apple announces 27-inch 5K Studio Display
Fun fact - if you have "reduce motion" enabled on macOS the webpage becomes a normal flat scrollable page (what you'd expect).
jkelleyrtp··on Apple Event March 8, 2022
If anything, better hardware is just an enabling technology for programming languages that run their static analysis at compile time. Rustc is written in Rust - it's not like it's going to get 10x faster any time soon.
jkelleyrtp··on Apple Event March 8, 2022
Would love to see Rust compile times on the M1 Ultra :-)
jkelleyrtp··on I’m porting the TypeScript type checker tsc to Go
TSC doesn't need to "stick around", right? Just a run-once and the program is over?

In those cases, https://github.com/fitzgen/bumpalo works amazingly as an arena. You can pretty much forget about reference counting and have direct references everywhere in your graph. The disadvantage is that it's hard to modify your tree without leaving memory around.

We use it extensively in http://github.com/dioxusLabs/dioxus and don't need to worry about Rc anywhere in the graph/diffing code.

← PreviousPage 5 of 9Next →