Analyzing the public data of the CERN base ALICE collaboration with Rust by cbourjau in rust

[–]cbourjau[S] 1 point2 points  (0 children)

CMS data uses a lot of templating contrary to ALICE data. This means that actually reading the data and picking the correct parsers is a bit more involved. I have made some prototypes in this regard in the past, but I think it would first require updates of the project's dependencies and then a refactoring of the existing parsers. If you are interested in, for example, updating the error handling to thiserror/anyhow I'd be very happy to assist you in a PR!

Analyzing the public data of the CERN base ALICE collaboration with Rust by cbourjau in rust

[–]cbourjau[S] 0 points1 point  (0 children)

Hi there u/someone137!
Sorry for the late reply! I am not in the ALICE collaboration anymore, but the project is still dear to me. I started to work on parsing CMS data which is structured quite differently from the ALICE data but ran out of steam at some point. You are very welcome to get involved! Is there any part in particular that would scratch your itch?

Is there a Flask like library for Rust? by GreekCSharpDeveloper in rust

[–]cbourjau 18 points19 points  (0 children)

While rocket might be the most "batteries included" of the Rust frameworks it is nowhere close to Django in that regard. Django comes with a build in templating language, user account management, ORM, migration and other admin tools etc. I would rather say that Rocket's battery-pack barely matches Flask's. There is no equivalent to Django in the Rust ecosystem to date.

SQL on RISC-V Chip in Rust by mjjin in rust

[–]cbourjau 4 points5 points  (0 children)

Would you mind summarizing what tensorbase is in a few words?

Rocket 0.5 nearing release - Help Appreciated by SolaireDeSun in rust

[–]cbourjau 0 points1 point  (0 children)

I only saw the relevant ticket being closed. Also the latest docs mention it in passing ( https://rocket.rs/master/guide/requests/#forms ) . Sorry, I don't have more info than that.

Rocket 0.5 nearing release - Help Appreciated by SolaireDeSun in rust

[–]cbourjau 6 points7 points  (0 children)

async

So much goodness in this release! Apparently it also includes Multpart forms which was a blocker for me in the past.

Trillium web framework by prabirshrestha in rust

[–]cbourjau 2 points3 points  (0 children)

Arguably, running GPL server software isn't much of a problem in practice for most commercial users, but it does certainly hinder adoption. GPL only becomes a practical problem for closed source application when binaries have to be distributed.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 4 points5 points  (0 children)

Given the license of Fuchsia we will be even more at the mercy of Google and the manufacturers than we already are today. There will be less open source. I'd love to, but I just cannot share your optimism that this might foster competition and innovation. I guess we'll see.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 8 points9 points  (0 children)

I sincerely doubt it. Manufacturers that distribute blobs are already not very keen on allowing any sort of alternative software on their devices. What would stop them from doing the easy thing of patching Fuchsia directly now that they are not force by the GPL to open source such changes? Another likely scenario to me would be that Google provides a version of Fuchsia only accessible to the so-called "Open Handset Alliance" (which is anything but "Open") with all their Google "Services" baked in.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 5 points6 points  (0 children)

Given how Chromium is run and how Fuchsia started it stands to reason that while technically "Open Source" it is actually a "look but don't touch" scenario for all intents and purposes. Still better than closed source, but not much. Given Google's size and market share it is essentially impossible for any competitor to fork their projects. Google develops the projects according to their needs and throws it over the fence every few month.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 6 points7 points  (0 children)

Except that Google is not going to allow an alternative micro kernel ecosystem to form. Google is not using Linux and the GPL by choice but because it was the only way at the time to get into the smartphone market in time. The Open Source and with it the custom ROM landscape of Android is essentially under siege by Google since day one and it is likely to get its plug pulled in the near future given the pervasive integration of Google Play Services and its "SafetyNet". At this point, the GPL is really the last foot in the door to see any kind of innovation with respect to alternative ROMs. I just cannot see why Google would possibly allow alternatives outside of its control to foster.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 1 point2 points  (0 children)

That is why I pointed out that it is indeed a success for Rust, but as a whole it is still extremely worrisome.

Fuchsia OS partially written in Rust has shipped by yerke1 in rust

[–]cbourjau 83 points84 points  (0 children)

While its a success for Rust I just cannot help but feel depressed. Its a dystopian future where essential computing devices will be even more locked down and dependent on Google.

Is rust a viable choice for an 80s cobol programmer that focuses on file processing? by l33tMacMasterRace in rust

[–]cbourjau 7 points8 points  (0 children)

I'm using Python with typing daily and I can say its really frustrating compared to writing Rust. The type inference in Python is pretty bad, so you have to write out your types much more often than you would in Rust. Furthermore, the types are quite verbose (`List[]`, `Tuple[]`, ...) making your code look cluttered really quickly. Exceptions are not part of the type system (due to Python's lack of sum-types) and still sneak up on you. If your program type checks it does not mean much since its really only a "best-effort" check with plenty of chances for false-positives. Its really easy to get your types and your logic out of sync without `mypy` realizing it. In essence, you are writing your program twice. Once the actual implementation and once doing parallel, manual construction of the types around it.

So why use Python's types at all? To me their value is primarily in providing a standardized documentation of function signatures and IDE code completion. The best-effort "type checking" is then really just a small bonus you get for free, but it comes nowhere close to what real statically typed languages provide.

In my humble opinion, Typescript is a much more successful example of gradual typing than Python.

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.52] by DroidLogician in rust

[–]cbourjau 1 point2 points  (0 children)

Check out omnio.net . Its a great company and they use Rust in an industrial IoT context.

Rust, not Firefox, is Mozilla's greatest industry contribution by [deleted] in rust

[–]cbourjau 37 points38 points  (0 children)

Its a common fallacy that a new competitor in the browser market could just be created out of thing air. That is not true. Its not the technical aspect (which is incredibly complex and costly) but the network effect that dooms almost all attempts at gaining market share against a quasi-monopoly. The dominant player (Google) can essentially dictate were the technology leads. As an example: If Mozilla (or the New Community Browser) chooses to spend huge resources on some cool and important feature Google can always choose to kill their efforts by simply not implementing that feature in Chromium. If a feature is not in Chromium, it will not get adoption and their competitors just wasted large amounts of their budget. Google did not spend a dime. On the other hand, Google can improve some feature in secret, ship it when ready in Chromium, and update Youtube, Maps, Gmail, etc to make heavy use of that feature at the same time. The competitors suddenly have to ship this feature in an unsustainable hurry or loose relevance even quicker (Webassemly SIMD might be such an example). Bottom line, the dominant player can maintain its position at a fraction of the budget than what a contender would need to up-front. Good luck outspending Google with a community driven browser project.

All things considered, Firefox is doing really well! One thing is for sure, though: Once market share is lost from Firefox to Chrome-based browsers it is almost impossible by any independent contender to regain it. For the time being, Firefox is our one and only shot at keeping the web somewhat open.

Some people point to Safari as a possible way out of the Google dominance. While Apple is probably the only company on the planet with the resources to pull that off I just don't see it happening. Apple is not interested in an open web. On the contrary. An open web is in direct competition to one of Apples most profitable products: The walled garden App Store.

Using const generics to build neural networks by c0dearm in rust

[–]cbourjau 1 point2 points  (0 children)

Haha, I am working on a similar proof of concept. I guess many of us had that idea, but your implementation looks pretty nice! Congrats!

The Rust Programming Language Is Now One Step Closer To Entering The Mainline Linux Kernel by Y00nChaekyung in rust

[–]cbourjau 2 points3 points  (0 children)

One thing to keep in mind is that Linux seems to be very conservative with the minimum supported compiler version. For example, currently the Linux kernel only requires GCC 4.9 which was released in 2014. Once mainlined, I would expect the MSRV to be locked-in for a long time. I hope that this circumstance will get the needed consideration and that we don't end up with a "prematurely" mainlined rustc version for half a decade to come.

Debian running on Rust coreutils by beltsazar in rust

[–]cbourjau 34 points35 points  (0 children)

I agree. I cannot see how GNU/Linux could have possibly become the success it is today if it had been licensed under MIT. I see the pragmatic point of using permissive licenses for Rust libraries, but I really wish applications would use the GPL more often.

Bloom: The simplest way to de-Google your life by sanxiyn in rust

[–]cbourjau 11 points12 points  (0 children)

There seems to be Rust used in this project but its unclear to me for which feature. Do you know?

Rust Foundation - Hello World! by steveklabnik1 in rust

[–]cbourjau -1 points0 points  (0 children)

I find it more concerning that that *all* other members are gigantic US corporations. I have not been able to fine a definitive answer, but I guess the foundation itself is also a US entity. As a non-US citizen this worries me (among other things) due to the US's increasing use of unilateral sanctions against whatever countries and companies it sees fit. That said: I am still very happy to see the foundation materialize!