214 karma · joined February 17, 2016
How can they prevent my, let’s say vim, client from connecting to a closed-source server if they both speak the same protocol?
If this course doesn't include relevant legal topics, do you know any other "programming for lawyers" course that you would recommend?
Have heard many good things about the book - curious to get some concrete anecdata
How informative is git log/blame?
Imagine if one could do a major feature contribution to clangd/pyls/rust-analyzer as part of their advanced compilers course. The student gets a better understanding of (open-source) software development practices, gains a deeper proficiency in the language (not just the APIs), the project brings new contributors and users (including the student herself) benefit from the new feature.
Double bubble!
He designed the course to be an exercise in working in an existing codebase that one needs to understand before adding features.
I guess that is one of the many reasons CMU grads kick open the door into many companies.
According to this, https://en.wikipedia.org/wiki/International_taxation#Taxatio..., Hungary, Myanmar have the same as the US. Spain and Turkey and several others have it for some citizens.
Also, if you have children and one of them secures an offer to study in Cambridge, MIT, your country’s equivalent of a prestigious university - will you tell them to turn that offer down to lend their privilege?
I just want to use tools that help me get stuff done. C++ has had a 30-year head start, why can they not see the overall value-add of a default build and test tool and a format for package declaration and management.
All integer types have "checked_" arithmetic operations, which return None in case of overflow. https://doc.rust-lang.org/std/?search=checked_
First of all, the proliferation of header-only libraries that people vendor into their Cpp projects has the same attack surface. Additionally, there is less tooling to help you track vulnerabilities in Cpp dependencies and upgrade when fixes come out. If you do rely on external cpp deps, then you must have a code review process before those deps are whitelisted for use.
Now, you can extend this code review process to rust crates.
Run a security review of a crate after which that crate is pushed to an internal registry. Every external crate upgrade can go through the same security review process until which point developers will build with the old version present in the internal registry.
In the context of a large enough organisation, an increasing number of crates will become internal, thus solving the trust/responsibility issues.
by no means, do i suggest that crates is unhackable. That's why I want to raise awareness of already existing infrastructure and procedures to vet code before including in your systems.
Safety
Before we get to ownership and some thread-safety, how do you explain the fact that integer addition and number conversion are safe operations in Rust, which throw/panic when they fail instead of the default Cpp behaviour, which _silently_ corrupts data?
If the first manager fires her because of her gender, we can take him to court for unlawful dismissal.
There are many mean individuals out there. That’s because we all have capacity for discrimination and ultimately violence. The call to stop discussing politics at work might result in fewer such frictions and keep us focused on the job at hand. A more productive and socially cohesive outcome in my opinion.
Disclaimer: I’m an immigrant.
I’m generally a pro-market person. In the case of UK real estate, I support a ban on non-residents buying property similar to what Canada have.
I interpret the “capitalists are screwing the working class” as a) erroneous b) long-term dangerous c) convenient way for those bureaucrats to divide and conquer. Meanwhile they take risks with our economy without accountability.
Are Nike basketball sponsorship deals targeted at black people or are they targeted at the most successful and famous basketball players regardless of their skin pigmentation?
100 milliseconds is practically an eternity
From what I have heard, Optiver have a performance lab, which replicate real conditions with an exchange replayer and they can measure wire-to-wire latency for every release.
Hiring people for their maths chops as quants, you probably don't expect them to know about HW-level optimisations at the beginning of their finance careers, which, I guess, is the reason for such a performance lab. Build tools that help people bring their best skills to the table and catch regressions.
My 2 cents. I think rust-analyzer offers a great new dev onboarding experience. issues labelled with has-instructions usually have a a link to the relevant snippet of code in the repo and sometimes even the stub of a failing unit test. While it might be obvious to you, the author, how and where to find the necessary code, it enables a great many people to send patches.
Witness the number of contributors with <10 commits https://github.com/rust-analyzer/rust-analyzer/graphs/contri...
If you want to increase adoption, please borrow as many dev experience tricks from rust-analyzer as possible