@arendjr@mstdn.social
@arendjr@mstdn.social avatar

arendjr

@arendjr@mstdn.social

Husband & dad. Software engineer by trade and author for leisure.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

arendjr, to rust
@arendjr@mstdn.social avatar

@sophiajt just introduced : an systems language that is easier to use and learn, possibly quite interesting for application development. Will supposedly have interoperability. Very interesting!

An example of a circular linked list
Lots of roads ahead: Continue building reference compiler, better abstractions, Rust interop and more exploration of easy-to-use safety mechanisms

arendjr, to rust
@arendjr@mstdn.social avatar

Starting tomorrow, @rustnl will be taking place in Delft. I’ll be attending, so if you like to discuss things related to @biomejs or in general while there, hit me up!

arendjr, to rust
@arendjr@mstdn.social avatar

Time for another progress update on integrating GritQL into @biomejs : https://github.com/biomejs/biome/discussions/2585

arendjr, to javascript
@arendjr@mstdn.social avatar

Today I have been busy creating a lot of issues for @biomejs regarding our progress as well as upcoming .

They’re all bundled under this umbrella: https://github.com/biomejs/biome/issues/2463

arendjr,
@arendjr@mstdn.social avatar

We’re also looking for input on which JS engine to use for @biomejs: https://github.com/biomejs/biome/discussions/2467

arendjr, to programming
@arendjr@mstdn.social avatar

If anyone is curious about our progress towards implementing (GritQL) in @biomejs , I’ve written a progress update: https://github.com/biomejs/biome/discussions/2286

arendjr, to ai
@arendjr@mstdn.social avatar

This is the first time I created a PR for a project that had an bot do an auto-review for me. It actually created an auto-generated summary and walkthrough, and even helpfully offered to add issues to track some FIXMEs I left in the code. It's not super-smart, but it's helpful enough to be useful. Kinda impressed actually :)
https://github.com/getgrit/gritql/pull/66

arendjr, to random
@arendjr@mstdn.social avatar

in progress update: @biomejs 's parser is now merged. Next steps: Implementing GritQL formatting and integrating the Grit engine to perform some actual code matching transforms.

https://github.com/biomejs/biome/pull/1998

arendjr, to rust
@arendjr@mstdn.social avatar

Shoutout to Grit.io for open-sourcing their engine: https://github.com/getgrit/gritql

Looking forward to integrating it into @biomejs as part of my plugin efforts! https://github.com/biomejs/biome/discussions/1762

arendjr, to rust
@arendjr@mstdn.social avatar

Wrote a piece exploring how we can improve @bevy ’s UI system: https://arendjr.nl/blog/2024/03/in-search-of-a-better-bevy-ui/

arendjr, to typescript
@arendjr@mstdn.social avatar

Received an invite for the https://jsr.io beta. This looks like a potential winner!

  • First-class @deno_land support
  • ESM-only
  • Built-in
  • Auto-doc generation from your TS sources
  • Seamless publishing from Actions
  • integration

Especially the part where you can just publish your TypeScript package without transpilation, and they handle /NPM compatibility is pretty big for IMO.

arendjr, to node
@arendjr@mstdn.social avatar

Today we released v1.0.0 of our autometrics-ts library. The version number coincides with the release of the 1.0 specification for Autometrics, but there’s one more thing I’m particularly happy about: First class @deno_land support. There’s some small kinks to work out still (I really wish deno.land would allow us to filter tags, for one…) but most of our core development happens in now.

https://github.com/autometrics-dev/autometrics-ts/releases/tag/lib-v1.0.0

janriemer, (edited ) to javascript

This is mad 🤯

oxc - The Oxidation #Compiler is creating a suite of high-#performance tools for the #JavaScript / #TypeScript language re-written in #Rust - by Boshen:

https://github.com/web-infra-dev/oxc

Its linter is 50 - 100 times faster than #ESLint...

https://github.com/Boshen/bench-javascript-linter

...and its parser is even 2x faster than #swc

https://github.com/Boshen/bench-javascript-parser-written-in-rust

#JS tooling goes brrrrrrrrrrr! 🚀

#RustLang #WebDev #WebDevelopment

arendjr,
@arendjr@mstdn.social avatar

@janriemer Is it faster than though? Those guys already have a functional formatter and linter released with similar performance.

arendjr,
@arendjr@mstdn.social avatar

@janriemer Hah, that’s neat. I was under the impression Rome was at least on par with SWC, but I guess the way they handle error tolerance might cause some overhead.

Though in fairness I’ll probably still stick with Rome since they have a good set of rules now and their IDE integration is also pretty good, and they’re certainly fast enough 😅

arendjr,
@arendjr@mstdn.social avatar

@janriemer @spyke As someone who is fluent in both TS and Rust and still use both regularly, I would say Rust is generally the more productive language of the two. It’s harder to learn, and not the greatest for quick’n dirty prototyping, but when it comes to building a product the advantages of its type system and its package ecosystem can quickly outweigh that.

arendjr,
@arendjr@mstdn.social avatar

@janriemer @spyke I should also say that Rust’s type system is simpler than TypeScript’s in many ways. Its borrow checker may be harder to get used to, but otherwise TypeScript’s type system with its type unions and intersections, and conditionally derived types, is vastly more complex than Rust’s. Problem is, that complexity is there to deal with the idiosyncrasies of JS, rather than offering useful value on its own, making its use much harder than it should be.

arendjr,
@arendjr@mstdn.social avatar

@janriemer @spyke Well, Rust doesn’t have generators (at least in stable), so it’s simpler in that regard too 😅

But I get what you’re saying. Using certainly limits the pool of developers you can hire from. Ironically, it’s still easy to hire Rust developers right now, because many want to find jobs where they can use the language, but I don’t think that’ll hold forever either :)

mcc, to random
@mcc@mastodon.social avatar

When I'm writing Rust, I have a nigh-pathological focus on never using Rc or RefCells. I put a lot of effort into this. I tell myself this is because reference counting is an inefficiency, however small, and where that inefficiency is unnecessary it's worth avoiding. But if I'm being honest, I'm really doing it because I am trying to put off as long as possible looking up which one is Rc<RefCell<>> and which is RefCell<Rc<>>

arendjr,
@arendjr@mstdn.social avatar

@mcc I also try to avoid them, but isn’t that the point? While it’s indeed annoying when you require some complexity that pushes you to nest containers, the reality I’ve found is that in the vast majority of situations you don’t need them. And then it’s a good thing to push people a little to make them consider if they really need a container or not.

Languages are opinionated and it seems Rust has optimized for the common case at the expense of verbosity in the complex cases.

arstechnica, to random
@arstechnica@mastodon.social avatar

iPhone 15 rumors take shape: More screen, titanium body, and (finally) USB-C

All models should see meaningful upgrades, though Pro will get the usual extras.

https://arstechnica.com/gadgets/2023/07/iphone-15-rumors-take-shape-more-screen-titanium-body-and-finally-usb-c/?utm_brand=arstechnica&utm_social-type=owned&utm_source=mastodon&utm_medium=social

arendjr,
@arendjr@mstdn.social avatar

@arstechnica you say all models, but I don’t think I see any mention of the mini?

bagder, to rust
@bagder@mastodon.social avatar

libraries written in is fun and all, but when the provided C API has no documentation it makes it less fun. This seems to be a pattern for almost all rust libraries. Like your language would prevent the problems that happen because we can't understand how to use your library.

arendjr,
@arendjr@mstdn.social avatar

@thejpster @bagder I suspect you might indeed be seeing inverse of a problem that’s existed for decades. It used to be C programmers who created libraries that were consumed from other languages, often with binding generators in between. Those generated bindings also often lack documentation, but people accepted it because they wanted to use the C libraries and they solved it by creating idiomatic wrappers with documentation.

edfloreshz, to rust
@edfloreshz@hachyderm.io avatar

For all those working professionally with , what’s your job about?

arendjr,
@arendjr@mstdn.social avatar

@edfloreshz working in a startup for observability tooling. We have our backend in , parts of our frontend and a -based plugin system. We also built https://github.com/autometrics-dev/autometrics-rs

arendjr,
@arendjr@mstdn.social avatar

@somedev @netwren I wrote an older article about implementing Redux reducers in Rust: https://fiberplane.com/blog/writing-redux-reducers-in-rust

For us, the use case was migrating existing Redux reducers written in TypeScript to Rust for code reuse (and later, performance) reasons. We didn’t need to rebuild Redux itself though, since our Rust reducers could still be invoked from the TypeScript side of things.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • thenastyranch
  • magazineikmin
  • cubers
  • InstantRegret
  • cisconetworking
  • Youngstown
  • vwfavf
  • slotface
  • Durango
  • rosin
  • everett
  • kavyap
  • DreamBathrooms
  • provamag3
  • mdbf
  • khanakhh
  • modclub
  • tester
  • ethstaker
  • osvaldo12
  • GTA5RPClips
  • ngwrru68w68
  • Leos
  • anitta
  • tacticalgear
  • normalnudes
  • JUstTest
  • All magazines
    •