Aren't they trying to use Rust in the Linux kernel? That should accelerate adoption.
C/C++/C#/Go/Java/Obj-C/Rust/Swift etc more Static Strongly-Typed, Compiled Language Programming [Official Discussion Thread]
- Thread starter null
- Start date
Secure Da Bag
Veteran
Never forget the underrated Jai Programming Language - jai programming language resources and information
Last edited:
null
...
ok cool. i might learn rust at some point in the future. it will be either rust or go.
Yeah, I saw something recently about them integrating Rust into the kernel soon.
Mission249
All Star
You might as well have named the thread "Web developers stay out" 
null
...
You might as well have named the thread "Web developers stay out"
not at all.
+ servlets, JSF, JSP
Shout out to any other iOS devs on here
I've started learning Rust too for a side project I've been thinking about tackling. Some of its concepts take a little effort to wrap my head around. But on the flip side, I think knowing Swift has actually made it easier for me to pick up on certain aspects of the language. I'm liking it so far.
null
...
Shout out to any other iOS devs on here
I've started learning Rust too for a side project I've been thinking about tackling. Some of its concepts take a little effort to wrap my head around. But on the flip side, I think knowing Swift has actually made it easier for me to pick up on certain aspects of the language. I'm liking it so far.
yeah rust looks like a really cool and modern language. c++ is a bit of a mess now so it makes sense that someone would create a (c++)++.
it's interesting that they say that heap veriables are auto-deleted without the need for reference counting.
it would appear to me that that means that casting pointers to ints/longs and back (as people do in c/c++) while the original goes out of scope is not permitted. or at least could cause problems. to take it one step further where those int ptrs are written disk or shared memory and all references go out of scope.
or does rust somehow keep track?
i found this discussion which suggests that in can be problematic.
"Transmuting pointers to integers (i.e., not going through the regular cast) is a problem. This is demonstrated by the following silly example:"
What about: Pointer-to-integer transmutes? · Issue #286 · rust-lang/unsafe-code-guidelines
Transmuting pointers to integers (i.e., not going through the regular cast) is a problem. This is demonstrated by the following silly example: fn example(ptr: *const i32, cmp: usize) -> usize { ...
github.com
-
c++ is far too big and they keep adding to it
. all the conflicting and complex rules increases the chance of writing buggy code.The funniest thing about Rust evangelists is that they think they are going to win in embedded systems by beating out c++ but many of the embedded guys I know have even refused to move onto c++ from c 
.
I'm not a good enough dev to even worry about these things
. Garbage Collector 4 life for me .
.I'm not a good enough dev to even worry about these things
. Garbage Collector 4 life for me .C# and Java are big time in web development thoYou might as well have named the thread "Web developers stay out"
c++ is the goat language for output but we both know the developer experience can get grimy.yeah but you know c# devs believe that windows is an acceptable operating system ...
it depends on what you were exposed to on the way up.
i mean javascript (web centric and barely a language) is above C++ (control systems, supercomputers, flight systems, operating systems) in that list.
null
...
I have been working with C++ and threads.
In particular the c++11 threading model the effects fences, barriers and cache memory ines have on consistency and throughput. part of that is lockless concurrency as well. then further to that the way chipsets are moving towards a standard that allows for barriers and fences with low overhead. in particular the aim is low read overhead with acceptable write overhead.
there are some good c++ con talks about this online. two vids on atomic weapons by sutter are good. total about 2h30m.
plus i went though the majority of this book
the big issue I see with c++ threads is how to interrupt threads (not cond var waits).
in c#/java that's pretty straightforward.
i need to look at it a bit more.
I read that python to golang is easier than python to rust.
i think I will start learning rust towards the end of the year as my main new compiled language. the fact that it will be used in the linux kernel and on android is a good sign to me. also rust scores prety high here Stack Overflow Developer Survey 2020 and has since 2016 as most loved language.
i should be in the US by then so cannot be sure. it depends on other real world factors.
i prefer technical rather than scripting-like languages/syntax and so I think rust is a natural fit for me.
c++ is a mess now. even after all these changes ranges are coming soon - which will disriupt the use of iterators for range definitions (even in the STL). then on top of that transforms incl lazy transforms which is going to be another cycle of relearning.
to be fair i think i will need to revisit the question of rust vs. golang eventually.
what are your thoughts?
from what I have read some people think rust is hard to learn, esp. the borrow semantics and writing elegant idiomatic code.
rust's concurrency model relies on the compiler statically informing you of errors. is that tried and tested enough for business to rely on it when c++/c work already?
dunno.
null
...
bump.
