I have no specific knowledge of this stuff. But the generic answer is an obvious one.
However Python code does it can be replicated in Rust.
For example, if python code executes the driver as a subprocess, then that too can be done in Rust.
So checking how Python code does it will probably lead to an answer to this question.
Maybe ask a web dev community about this.
There could be something better written in Rust.
There could be something better NOT written in Rust.
They should know.
Good. But a lot of us do this already:
[target.x86_64-unknown-linux-gnu]
linker = "clang" # for mold
rustflags = ["-c", "link-arg=-fuse-ld=/usr/bin/mold"]
[target.x86_64-unknown-linux-musl]
rustflags = ["-Z", "gcc-ld=lld"]
I didn’t understand your sentence. But:
Having concerns is valid.
Having them in the context of this story/ad is misplaced.
IBM invested 1B$ in Linux all the way back in year 2000 (imagine how much that is worth with tech inflation), and they did it again years later.
That 1M$ is nothing. It’s not nearly enough to control the Rust foundation for one year, let alone controlling the Rust project as a whole. Calling it a “Vote of Confidence in Rust’s Future” was probably a good-spirited joke from the author, at least I hope it was.
Note that IBM still doesn’t control Linux (even after acquiring RedHat), and we still have no problem calling them evil. Some of us still have no problem calling MS evil either, although many of the new crop of developers won’t, because for them the chance to have the financial privilege of working there someday outweighs any moral considerations. Incidentally, there is a good intersection between this group, and the group that takes moral posturing about whatever in-group approved cause of the month to the maximum. Ironic, isn’t it?
This is effective advertisement, not a donation. A real ad (with a campaign) would probably have cost much more, and wouldn’t continue to be propagated for free months after the ad campaign is over, like this peace of news.
This type of ad is also much harder to filter/block, since not only it appears to be site-native, but also topic-native.
Not based on, but built on top of Iced.
The fork wouldn’t be that different from whatever upstream Iced snapshot it last synced with. There are two major, if peripheral, changes still. A renderer for some Wayland special needs, and some integrated accessibility support. At least that was the case until a few weeks ago. I don’t think anything significant changed since.
So the Iced API itself is largely the same. However, since this is built on top of Iced. COSMIC apps are more inclined to use abstractions and tools from libcosmic wherever applicable instead of using Iced API directly. But you still see plenty of direct Iced API use.
Thunderbird is still going?
What’s next? Rust in Songbird?
I wanted to mention that this reminds me of the old Delegation RFC, which some of us didn’t like, exactly because it felt like a problem for proc-macros to solve. It eventually got postponed.
But then, the delegation terminology is used in hereditary, so you’re probably aware of all that already ;)
Anyway, other crates like delegate, ambassador and portrait are mentioned in the latest comments below that RFC. I wanted to quickly check how many dependants each one of those have, but https://crates.io can’t do that at the moment. Nice error message though!
Unfortunately, I have no time to check what kind of code each one of them crates generates, so I have nothing of value to add.
If you’re not familiar with the tracing crate, give the instrument page a read. You may find the #[instrument(err)] part particularly useful.
As for the errors themselves, if you’re using thiserror (you should be), then the variants in your error enum would/should contain the relevant context data. And the chain of errors would be tracked via source/[source] fields, as explained in the crate docs. You can see such chains if you use anyhow in your application code.
It’s a conspiracy too big that I don’t think anyone of us can really understand or grasp the scale of it all.
Thankfully, the EU was aware and prepared. And the EUPL is ready to usurp whatever project license, whenever needed.
Used it last month for the first time. It was great.
Documentation is very good.
typst-lsp is also good.
Did it all from neovim, exportPdf = "onSave" as a part of lsp setup, and zathura open in a tiling window manager. zathura auto-reloads the PDF when it changes on disk. So no web editor needed ;)
First class RTL support (which was required for the task at hand) was a very pleasant surprise.
Gotta admit though that I couldn’t figure out why typst-lsp didn’t work initially. Took me some time to figure out that it needs a git repo and files checked in to work. That probably should be mentioned in the README.
And there was the odd behavior here and there, like setting gradients on text elements in table fields actually setting the gradient over the whole table for some reason. Not sure if it was my fault since I was learning on the go, or an edge case not handled.
All in all, would definitely recommend.
Meh, everyone scaring you into thinking you don’t own your own mind.
Assuming your boss is not the dangerous kind (beyond legal threats), and if the goal is to make it FOSS, then do it using an alias first. Do it differently. Use components/libs/algos from other people at first, even if they are not perfect. Make those parts easily pluggable/replaceable which would be good design anyway. The code then wouldn’t be wholly yours, not even your alias self.
You can join the project later with your real identity as an interested domain expert (maybe a bit after not working for the same boss). Start contributing. Become a maintainer. And maybe take over after a while. You can start replacing non-optimal components/libs/algos with better ones piecemeal.
Oh, and if Rust wasn’t the choice of implementation, use it this time.
A reminder that the Servo project has resumed active development since the start of 2023, and is making good progress every month.
If you’re looking for a serious in-progress effort to create a new open, safe, performant, independent, and fully-featured web engine, that’s the one you should be keeping an eye on.
It won’t be easy trying to catch up to continuously evolving and changing web standards, but that’s the only effort with a chance.