bkolobara

7 ms·

31.
90%(lucumr.pocoo.org)
106 points by bkolobara 1y ago|35 comments
32.
by bkolobara 1y ago
I didn't need to hold the lock across the .await point and in that case the official docs recommend a regular lock.
33.
by bkolobara 1y ago
My intention with the blog was to show that Rust's lifetime tracking and trait system allow you to catch much more complicated issues than just "one type doesn't match another" errors. That's the main reason why I c
34.
by bkolobara 1y ago
Your Rust example would not work, because `window.set_href("/foo")` would not return anything (it would return the unit type "()" aka void). And you can't call `set_href()` again on "()". This is a co
35.
by bkolobara 1y ago
Thanks! I should have clarified a bit better that example. The point I was trying to make is that Rust's ownership model would allow you to design an api where calling `window.set_href('/foo')` would take ownership of `w
36.
by bkolobara 1y ago
Yes, if you use a scheduler that doesn't move work between threads, it will not require the task to be Send, and the example code would compile. Rust can use that type information and lifetimes to figure out when it's safe and whe
37.
Unexpected productivity boost of Rust(lubeno.dev)
525 points by bkolobara 1y ago|505 comments
38.
by bkolobara 1y ago
I have been working on the PR implementation for lubeno[1] and have been thinking a lot about the code review process. A big issue is that every team has a slightly different workflow, with different rules and requirements. The way GitHub i
39.
by bkolobara 1y ago
The actual announcement (now deleted on GitHub's blog): https://archive.is/IoMEg
40.
OpenAI's new GPT-5 models announced early by GitHub(theverge.com)
79 points by bkolobara 1y ago|72 comments
41.
by bkolobara 1y ago
> Unfortunately they thanked me for my application but said the team doesn't have the capacity to review additional applications. It seems like they didn't even look at his application.
42.
by bkolobara 1y ago
It still helps sometimes. I was changing some settings on the server and messed up the automatic renewal. Getting an email from them saved me a lot of issues.
43.
by bkolobara 1y ago
The main issue with LLMs is that they can't "judge" contributions correctly. Their review is very nitpicky on things that don't matter and often misses big issues that a human familiar with the codebase would recognise.
44.
by bkolobara 1y ago
Many companies start in the "garage" and if you have privacy concerns, you can't use your home address as company address. This requires you to rent a spot in a coworking that allows you to use their address as company addres
45.
by bkolobara 2y ago
I have used jj for about one month on a project with a colocated git repo. So far, I enjoy it a lot. Previously I would have a bunch of 'wip', 'fix typo' commits, but my commit history got much cleaner with jj. It's
46.
Flawless Replay - time-travel debugger for Rust workflows(flawless.dev)
1 points by bkolobara 2y ago|0 comments
47.
by bkolobara 2y ago
You can get most out of it by using it as a "sidecar" next to your native Rust application. That way you get access to the full power of Rust by triggering "native actions" from flawless through http. And you can still u
48.
by bkolobara 2y ago
Hi! I'm Bernard, the creator of flawless. Happy to answer any questions ^^
49.
Is Anyone Out There?(prospectmagazine.co.uk)
4 points by bkolobara 2y ago|0 comments
50.
by bkolobara 2y ago
https://www.youtube.com/watch?v=GjDwj7RWOgs K23: A Secure Research OS Running WASM - Jonas Kruckenberg (RustNL 2024)
51.
Experimental WASM Microkernel Operating System(github.com)
3 points by bkolobara 2y ago|1 comments
52.
Nvidia hits $3T and surpasses Apple as second most valuable company(theguardian.com)
4 points by bkolobara 2y ago|1 comments
53.
AI and the Fetishization of Ideas(terribleminds.com)
2 points by bkolobara 3y ago|0 comments
54.
by bkolobara 3y ago
In this scenario, the workflow is marked as "failed" and requires manual approval to continue. Sometimes you just can't resolve the issue without human input.
55.
by bkolobara 3y ago
Hi! I'm the author of flawless. Exactly once execution is one of the guarantees I want to provide. Flawless should always give you peace of mind, and in cases it can't guarantee exactly once execution it will sacrifice progress. W
56.
by bkolobara 3y ago
Hi! I'm the author of the essay. Durable execution is meant to complement your application. You will never want to model everything with it. It solves the problem of needing to decide how often to manually make snapshots of some import
57.
Work Is Work(codahale.com)
2 points by bkolobara 3y ago|0 comments
58.
Rust Is Growing(flawless.dev)
5 points by bkolobara 3y ago|1 comments
59.
Bleacher Report gutting out OTP(old.reddit.com)
5 points by bkolobara 3y ago|0 comments
60.
The Onyx Programming Language(wasmer.io)
197 points by bkolobara 3y ago|138 comments

More ›