My wife and I are excited about our upcoming move to Germany this October, where she'll be pursuing her master's degree.
I'm currently exploring opportunities as a Go or Rust backend developer.
If you happen to know of any positions available, whether remote or in the Bielefeld area, I'd really appreciate it if you could let me know.
Sharing my resume and discussing potential collaborations would be wonderful!
Hurl is a command line tool that runs HTTP requests defined in a simple plain text format.
It can chain requests, capture values and evaluate queries on headers and body response. Hurl is very versatile: it can be used for both fetching data and testing HTTP sessions.
Hurl makes it easy to work with HTML content, #REST / SOAP / GraphQL APIs, or any other XML / JSON based APIs.
Heya! I'm in need of a new job. My current gig is contract based, which I don't see as a sustainable option going forward.
I'm a software developer based in Pennsylvania. I enjoy taking on complex problems and finding solutions to them, especially close to the hardware. I've been teaching myself to code for about nine years now, gaining experience in a myriad of technologies.
So, if anyone is in need of a developer with extensive experience in Rust, C/C++, CI/CD, or webdev, please reach out!
I can be reached via email at julia AT insertdomain DOT name.
Out of 6 languages recommended by the NSA, 4 are patended bvy multibillion comanies who can pull the plug on them at any time (and Oracle already tried that).
C# - PATENTED by Microsoft,
Go - PATENTED by Google
Java - PATENTED by Oracle, NOT FREE
Python - not too shabby
Rust - not too shabby
Swift - PATENTED by Apple
I’ve been out of job since June with very low self income (I don't qualify for public unemployment income) and the project I was due to start in February will probably be delayed until April-May.
I'm a Staff / Principal Engineer who likes to work with nice people on R&D projects, remotely, preferably async, but at this point I’m open to anything for the next two/three months (hoping for no further delays).
A while back I posted to announce we were enabling the use of #rust as a development language within @thunderbird
Pleased to say that we've now landed support, and as of today it's possible to write new libraries and xpcom components using #rustlang, as part of the libxul build!
The reader and input stack have been ported, which is basically everything. There's still some entry points in C++ (PR being reviewed) and test helper binary (might make a good external contribution as it's entirely self-contained), but almost all of the C++ is gone, and with it large chunks of the FFI.
Now we just have the second 90% to go - making sure this rewritten fish is portable and distributable!
🦀 I wrote a proposal for an #[export] attribute in #rustlang to allow for dynamic linking between Rust crates, without losing memory safety at the linker boundary.
This will make other ABI work aimed at Rust FFI directly usable between Rust crates as well.
Turn on overflow checks in your release builds. I do this in even the smallest embedded applications (16 kiB of flash or less). It doesn't hurt performance as much as you might expect, and has caught many legitimate bugs that would otherwise have stayed hidden.
This is particularly important if you never build in debug mode for space or performance reasons. (Overflow checks are not why debug mode is slow!)
During the past 6 months I invoiced a grand total of 11 days so at this point I will code for food, I guess 🫠
I have 15 years of experience from developer to CTO, out of 10 as freelancer, and 2023 will be my worst year ever. Living that while inflation explodes is probably not helping either 🥴
Whether you've just begun using #rustlang, are an experienced Rust user, stopped using Rust, or might use Rust in the future, we'd like to hear from you!
Available in seven languages and open until January 15th:
🦀 Small Rust reversing tip: The Rust standard library documentation hides a lot of fields and items by default. For example, the documentation for the struct std::vec::Vec does not show you what a Vec's internal fields are. This can be annoying if you're looking for the implementation details of a certain type - I found that I kept having to click the "source" button on every single struct I wanted to get more information about, to look at the source code directly.
pub struct Vec<T, A = Global> where A: Allocator,<br></br>{<br></br> buf: RawVec<T, A>,<br></br> len: usize,<br></br>}<br></br>
This version of the documentation also documents some items which are hidden from the regular documentation (i.e. items marked as #[doc(hidden)]). One example iscore::panic::panic_info::PanicInfo::internal_constructor, which is an implementation detail of core::panic::panic_info::PanicInfo.
Having the hosted https://stdrs.dev/ site is handy for quickly looking up certain standard library structs, but you can also generate the same information locally with rustdoc, via the --document-private-items and --document-hidden-items flags. The script used to generate the stdrs.dev site is here, and you can tweak the version of the standard library docs you want to generate as required (stdrs.dev has the nightly docs). There are some more details about the site from the author's initial Reddit post about it.
It’s probably the worst time of the year to post this, but as I have been bothering people here for the past 7 months : I’m open to freelance or contractor positions for 2024.
Read about the great progress made by the team behind Wasmtime (wasm runtime) and Cranelift (compiler backend used for Wasmtime and now Rust compiler) in 2023 and their plans for 2024.