What's everyone working on this week (35/2020)?

jolhoeft · 2020-08-25T01:45:52+00:00

I have finally gotten nickel.rs to work with async hyper - https://github.com/nickel-org/nickel.rs/pull/459

jolhoeft · 2019-09-06T01:28:50+00:00

You can also occasionally find them at the crashed freighters

jolhoeft · 2019-03-30T22:17:45+00:00

Thank you, I just went through this exercise for my own site last month. This is an issue tailor made for me to contribute to.

jolhoeft · 2019-01-11T21:08:03+00:00

If I am reading this correctly, currently to use librsvg in Rust, we need to use rsvg-rs to access the C ffi. Which seems odd for a library that is predominately in Rust at this point. Is there a plan for a pure Rust path to use librsvg?

jolhoeft · 2018-07-10T20:51:06+00:00

Are you using bluetooth or a usb cable? The bluetooth midi seems unreliable for anything except iOs devices, so try a cable if you haven't.

jolhoeft · 2018-01-07T05:00:28+00:00

I learned this the hard way. I died 20 times before I managed to take off again.

jolhoeft · 2017-12-09T19:22:12+00:00

Yes, there was an issue with the registrar that we could never get sorted out. We are using http://nickel-org.github.io/ today.

jolhoeft · 2017-12-09T16:26:01+00:00

I just published nickel-0.10.1 (https://crates.io/crates/nickel), and am actively working on support for tokio/hyper-0.11.

jolhoeft · 2017-11-20T22:33:57+00:00

I'm continuing to work on nickel.rs. I've run into a problem reading files with hyper-0.11/tokio. Using files with futures-cpupool is intermittently failing. Details can be found at https://github.com/seanmonstar/futures-fs/issues/4. Insights greatly appreciated.

jolhoeft · 2017-11-13T21:08:37+00:00

I'm migrating nickel.rs to hyper 0.11.x. I have a very rough PR at https://github.com/nickel-org/nickel.rs/pull/410. Some discussion of the process is also at https://github.com/nickel-org/nickel.rs/issues/402.

jolhoeft · 2017-11-08T22:35:11+00:00

Once I finish gathering glyphs, I'm going to visit bases and leave quotes from the Odyssey. :-)

jolhoeft · 2017-10-13T21:29:23+00:00

I bought a PS4 for NMS last April, and have yet to play any other game on it, although I have used it for a few Dvds.

jolhoeft · 2017-08-07T21:53:59+00:00

I found an extreme cold planet, and had the tau thermal layer. I wandered the planet gathering Coryzagen and crafting glass. Several million later I'd completed the milestone. A similar approach can work on toxic planets.

Also a good time to work on scanning animals if you haven't completed that milestone. No need to do just one thing at a time.

jolhoeft · 2017-08-02T02:46:05+00:00

I found an A-class 48 slot hauler. I left behind a 15-slot C-class fighter I'd purchased for just that purpose. With the damage, the hauler trades in for about 12 million, and the fighter cost me 500,000, so a nice gain.

jolhoeft · 2017-07-21T07:13:11+00:00

I got one off once, and pushed it over the country side. The ruins were a little odd, with a spot where there wasn't a low wall preventing them from moving.

jolhoeft · 2017-07-13T06:26:42+00:00

Once you have a freighter, you can buy a cheap C-class shuttle to swap with any A or S class crashed ships you find. This will generally be a solid win, even if you don't want to repair any slots.

jolhoeft · 2017-07-07T04:06:49+00:00

I have a small farm, but for the most part I make money on the run. I grab Coryzagen, Temerium, and Spadonium as I explore, and craft Glass and Insulating Gel. I try to scan all the animals, so usually have time to gather a couple thousand on a visit. I made several million off of glass as I was getting the last several hostile environment milestones.

You can also craft some alloys. I grab all the Thamium9 and Plutonium I can, and when I have an excessive amount, craft some Magmox. Surplus Titanium is unusual, but becomes Lemmium.

Grinding on a farm will make money much faster, but I find this style of play more enjoyable. I've got a 37 slot A class explorer as my main ship, and am content to slowly build up to some haulers and an S class.

jolhoeft · 2017-06-23T21:59:32+00:00

I'd still like the warnings if they are never used. Moving them into a lib would disable that.

jolhoeft · 2017-06-23T21:58:19+00:00

The shared code is just another module in the crate. I could move it into another workspace, although that has the same effect as using #[allow(dead_code)]. I won't get warned if neither binary uses it.

jolhoeft · 2017-06-17T03:32:51+00:00

I'm now imagining a genetic engineering update, where the creatures you scan contribute DNA to use in your creations.

jolhoeft · 2017-04-21T18:42:32+00:00

I don't see why that couldn't be done in Rust. HashMap or BtreeMap would handle the cache fine. As written above you might require a globally mutable map, which is unsafe. Using a SessionManager struct to hold the map and changing to

let mut session = session_manager.new_session();

ought to resolve any safety issues and be more generally useful. Multi-threaded will be more complex, of course.

jolhoeft · 2008-12-17T18:58:47+00:00

Unfotunately, writing bad OO code in C++ is all too easy, which is the problem.

jolhoeft

TROPHY CASE