tshepang | 7 years ago | on: Calls between JavaScript and WebAssembly are finally fast
very good
tshepang's comments
tshepang | 9 years ago | on: Announcing Remacs: Porting Emacs to Rust
What about it makes it the wrong tool for the job?
tshepang | 10 years ago | on: My Initial Experience with Rust (Eric Sink)
This should be http://ericsink.com/entries/rust1.html
tshepang | 11 years ago | on: Nim binary size from 160 KB to 150 Bytes
Why can't one use Cargo for bare-metal applications?
tshepang | 11 years ago | on: The Sortix Operating System
In some cases, especially new projects (like a new OS), I think the pain of using an immature-and-powerful language is less than using a mature-and-weak one.
tshepang | 11 years ago | on: Rust Priorities after 1.0
The core team has reserved the right to break backcompat without changing the major version if they find a serious problem in 1.x series. So I expect that it will be a while (at least a few years) before 2.0 is created.
tshepang | 11 years ago | on: Rust Priorities after 1.0
I don't think systemd does follow any semantic versioning: each of the feature releases change the major version.
tshepang | 11 years ago | on: Rust Priorities after 1.0
No one knows, and I don't think there's been (a public) discussion about it by projects leads. The only guarantee is that 1.x will not break anything (according to some definition of "break").
There needs to be more experience with widespread use and multiple releases, to see how far that backcompat can be held. Perhaps after 10 releases, it should be a lot more clear whether or not a Rust 2.0 will be needed.
tshepang | 11 years ago | on: Linux 4.0
nice catch :)
tshepang | 11 years ago | on: Show HN: Exa, a replacement for ls written in Rust
Would also be nice if the cp replacement (optionally) checks for available storage space before copying files.
tshepang | 11 years ago | on: On Rust and Nim
I think you should replace 'time' with 'a lot of time'. I've seen several commits that optimize things.
tshepang | 11 years ago | on: Announcing Rust 1.0 Alpha
most of the stuff; there are some notes when stuff is outdated
tshepang | 11 years ago | on: Ask HN: What to build with Rust?
A parser for some lightweight markup language, like reStructuredText, sounds like a good challenge.
tshepang | 11 years ago | on: Tornado Without a GIL on PyPy STM
Why doubt the amount that can be received from Gratipay? What do you need to see to consider using it for PyPy funding? Would a promise of, say $500/week, be enough to make it worth a bother?
tshepang | 11 years ago | on: Tornado Without a GIL on PyPy STM
Better it be the team account, to avoid having donors try decide "who contributes how much"... let the team decide. Also, please offer it as an alternative to PayPal on the project website.
tshepang | 11 years ago | on: Tornado Without a GIL on PyPy STM
Please create a PyPy team on Gratipay.
tshepang | 11 years ago | on: Windows 10 will come with a command-line package manager
What horrifying Iceweasel bugs did you experience?
tshepang | 11 years ago | on: On Error Handling in Rust
No need to wait. You can dive in right now without losing much later (I think changes between now and 1.0 aren't going to be that drastic). The guides are really good.
tshepang | 11 years ago | on: We have C++14
People would, on the surface, see a different beast, even though it remains 99% the same language. Not worth it.
With this argument, every release that adds a new keyword (for example) would have to be given a new name, since it will very likely break some code. Question that remains is how much must the changes be before the thing deserves a new name.
tshepang | 11 years ago | on: We have C++14
No one implied people are expected to compile every compiler they want to use on every system they want to use it. Point was it's not hard. Maybe link to a message where you detailed your troubles?
page 1