Slashdot Mirror


How Rust Can Replace C In Python Libraries (infoworld.com)

An anonymous reader quotes InfoWorld: Proponents of Rust, the language engineered by Mozilla to give developers both speed and memory safety, are stumping for the language as a long-term replacement for C and C++. But replacing software written in these languages can be a difficult, long-term project. One place where Rust could supplant C in the short term is in the traditionally C libraries used in other languages... [A] new spate of projects are making it easier to develop Rust libraries with convenient bindings to Python -- and to deploy Python packages that have Rust binaries.
The article specifically highlights these four new projects:
  • Rust-CPython - a set of bindings in Rust for the CPython runtime
  • PyO3 - a basic way to write Rust software with bindings to Python in both directions.
  • Snaek - lets developers create Rust libraries that are loaded dynamically into Python as needed, but don't rely on being linked statically against Python's runtime.
  • Cookiecutter PyPackage Rust Cross-Platform Publish - simplifies the process of bundling Rust binaries with a Python library.

187 of 304 comments (clear)

  1. But why? by Anonymous Coward · · Score: 4, Insightful

    Why use the new language of the month when C has been around for decades, is welll understood and does exactly what we want?

    How long before I start replacing rust with decay? 6 months? A year?

    1. Re: But why? by Anonymous Coward · · Score: 1

      Safety. Many python liba and Luna in other languages wrap c. If there are buffer overflows in c, those languages are just as hackable. Rust won't remove those issues while adding a whole new host of issues and performance regressions.

      Fixed that for you.

    2. Re:But why? by squiggleslash · · Score: 2, Interesting

      Because C is awful? It always was pretty bad but we used it because when you're trying to manually render a 16 color 2.5D image on a bitplaned VGA screen using a 6MHz 80286 then you pretty much have to forget array bounds checking, be willing to assume endianess, and have an easy way to translate integers into pointers.

      These days there's pretty much no reason to do any of this, which means that the only times you're going to do it is by accident. ie when you put a bug in your application.

      We need to ditch C.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:But why? by Anonymous Coward · · Score: 1

      I see you picked up some useful lingo to appear as if you're part of the tribe. But it would have helped if you knew the history of both C and Assembly language. Then you wouldn't have sounded like a poser. You gotta walk the walk cupcake before you make lame jokes.

    4. Re:But why? by dlleigh · · Score: 3, Insightful

      Portability. Think of C as a portable assembler.

    5. Re:But why? by 0100010001010011 · · Score: 1

      So think of Rust as a highlevel portable C abstraction.

    6. Re:But why? by slashdice · · Score: 3, Interesting

      I can (and sometimes do) compile C code that was written in the 80s or 90s. And it often works with little or no modifications. (And there are people running awk scripts from the 70s, calling me a whippersnapper). With something like rust or go or swift, your code will not compile in 6 months. (which is hilarious in the case of go because it's more 70s than Disco)

      --
      Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
    7. Re:But why? by Anonymous Coward · · Score: 1

      So think of Rust as complete garbage.

      Somebody needs to spray this in your eyes.

    8. Re:But why? by squiggleslash · · Score: 1

      To be fair, I was addressing the notion we shouldn't switch from C. I have no opinion on Rust itself.

      --
      You are not alone. This is not normal. None of this is normal.
    9. Re:But why? by gweihir · · Score: 4, Informative

      We actually need to ditch people that cannot handle C. Go be a "business coder" but stay away from real programs.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    10. Re:But why? by Anonymous Coward · · Score: 4, Interesting
    11. Re:But why? by Zero__Kelvin · · Score: 1

      Yes. It's a damn good thing that performance isn't an issue anymore! Remember when computers used to solve problems that required lots of iterations? Remember when Python was written in C so it would be fast? Thank God those days are behind us!

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    12. Re:But why? by chuckugly · · Score: 1

      If I had mod points. Someone mod this man up.

    13. Re:But why? by mikael · · Score: 1

      I remember porting one of my old MS-DOS demos from C to SDL. I had used a simple structure to abstract the VGA framebuffer into a rendering API. Figured it would take me an entire evening to port across. Recompiled and run in 15 minutes. Which left me another 15 minutes before I went out to catch the bus to do my weekly shopping.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    14. Re:But why? by jovetoo · · Score: 1

      Why? To run after the latest programming language fad, again?

      I liked the feature list of Rust, until I read the book and ran into their chapter on Ownership, I quit right there and then. I'll stick to std::shared_ptr<>, thank you very much. Research in programming languages is all nice and all these things contribute in their own way but in the end, the programming language should not get in the way of whatever algorithm you are trying to express. You need to be able to control your code in every aspect. Abstracting away memory management and locking is a good thing but only if it does not cost in expressiveness, in other words, it should not be handled by compiler.

      I agree, memory management and thread synchronization ARE HARD problems, especially for new programmers. Let them use Rust. Switch them to C++ for the real work. I would love to see someone implement enterprise class software like Apache/IIS/MariaDB/MySQL/Oracle/... in any other langauge than C/C++.

      For me, Rust is just another fad and now these guys are desperate to find a niche for their new toy. Except... most python packages are just wrapper around existing C/C++ libraries. And however much they like their Ownership idea, I truly hope it dies a quick and merciful death.

    15. Re:But why? by jovetoo · · Score: 1

      C but not C++.

    16. Re:But why? by geoskd · · Score: 4, Insightful

      These days there's pretty much no reason to do any of this, which means that the only times you're going to do it is by accident. ie when you put a bug in your application.

      That has to be the most ignorant thing in these comments so far, and there are some pretty stupid things in the comments above...

      Ignoring the performance of your software is just plain dumb. Web companies tend to get away with it, because they are not paying for the compute power directly, but it still annoys their users. If Google or Bing ignored the performance of the software needed to perform search, they would need vastly more hardware to keep up with demand. It is no accident that the backend of Google Search is written in C++, and that this all runs on a customized linux based OS.

      Do you have an HDMI TV? Have you noticed that it takes many 10's of seconds to turn on? That is because some dumb F^@# thought it would be a good idea to implement the interface in Java and it takes *forever* to start up. 50+ years ago, Kernigan and Ritchie came up with C because assembler was not portable. decades later, Stroustrup came up with C++, and there has not been a language since that can match the performance of either.

      When you are selling 50M of a product, and you want to put a processor that costs $0.50 more in it because you are too incompetent to write efficient code, your ass will be fired and replaced with someone who can do their job. In the mean time I hope I never have to use a product that has any of your "work" product in it.

      --
      I wish I had a good sig, but all the good ones are copyrighted
    17. Re:But why? by geoskd · · Score: 2, Interesting

      Let them use Rust. Switch them to C++ for the real work.

      Unfortunately, these interpreted languages tend to ruin programmers. Most (not all, but most) of the programmer I have met who were taught using a "modern" language like python, Go, Rust, Eiffel, etc... just don't amount to much. When they do eventually find they can no longer ignore the performance implications of their code, they are woefully unprepared to deal with C or C++. They consider the error messages cryptic and arcane, and they try their almighty best to use C and C++ the way they have used these other languages. The result is code that is slow bloated and buggy as hell.

      Programmers need to face the memory management demons early in their education. The longer they wait, the less comfortable they will be tackling pointers and all of their implications when the time comes.

      --
      I wish I had a good sig, but all the good ones are copyrighted
    18. Re:But why? by ArchieBunker · · Score: 3, Informative

      You're part of the problem we face today. Computers are order of magnitude faster than 20 years ago and yet software still never runs any faster. Web pages still render as quick today as they did in 1997. Software still has loading screens and even with an SSD we have to wait for the operating system to boot up and settle down.

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
    19. Re:But why? by hord · · Score: 2

      I'd never work for your "company". A real program:

      x) Abstracts work into reusable components
      x) Abstracts interfaces into functional, communicable units
      x) Doesn't care what languages it is written in

      Everything you mention I have done multiple times in multiple languages. Modulo the brain damage of library authors and language run-times they are all the same. They all have bugs in all the libraries you mention. And the weird thing is that most of them eventually rely on the C runtime like virtually every other piece of software. It's almost like every one wanted to be a C programmer but couldn't figure out pointers.

      Me? I write in C.

    20. Re:But why? by Anonymous Coward · · Score: 3, Insightful

      C was never awful, It is and has always been a wonderful language. It is true that it is designed for people who know how a computer works... That might be a bit much to ask from "modern" "coders". If you have zero knowledge of what a computer actually does I can understand that you see it as awful.

    21. Re: But why? by F.Ultra · · Score: 1

      Thank you for the most insightful comment in the entire thread!

    22. Re:But why? by Anonymous Coward · · Score: 1

      Moore's Law: Every 18 months hardware speed doubles.
      Gates' Law: Every 18 months software speed halves.

    23. Re:But why? by johanw · · Score: 1

      If you want web pages to load faster, use an adblocker. Ads are the worst reason of slow loading.

    24. Re:But why? by hord · · Score: 2

      You mean like Rust? Which compiles to LLVM? Which is written in C++? Which uses the C runtime?

      $ ldd /lib/libstdc++.so
              linux-vdso.so.1 (0x00007ffe1ad6f000)
              libm.so.6 => /usr/lib/libm.so.6 (0x00007fce35da5000)
              libc.so.6 => /usr/lib/libc.so.6 (0x00007fce359fd000) /usr/lib64/ld-linux-x86-64.so.2 (0x000055f372126000)
              libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fce357e5000)

      But I've never used C so what do I know?

    25. Re:But why? by Anonymous Coward · · Score: 1

      A real program is done in a reasonable time.
      Is maintainable.
      And is written in a language you find Employees for.

      The latter one is why Rust is unlikely to ever replace C.

      And most certainly it is not written in a portable assembler, unless you have to, e.g. in some embedded environments where C++ is overkill or not manageable.

      Or, you know, you actually need to do something without using all the memory in the world and with lower power consumption so your battery isn't dead in 30 minutes. Oh right, you could just write the important parts in C/C++ and the rest in some other language or framework.

      x) Abstracts work into reusable components
      Close to impossible in C, as C is not object oriented. You are stuck with simple libraries like stdio and math etc.

      You seem to be ignoring the existence of many many libraries in C. You don't need object orientation to do this (and indeed in some cases it only gets in the way).

      x) Abstracts interfaces into functional, communicable units
      Completely impossible in C as C has nothing that resembles interfaces.

      You mean that pretty much no OS kernel, ever, has defined an interface you've used?

      Me? I write in C.
      I doubt that. Or you would not have written nonsense like above.

      And the weird thing is that most of them eventually rely on the C runtime like virtually every other piece of software.
      You are an idiot, right? Unless you compile for a virtual machine all languages/compilers compile to machine code. Pascal, COBOL, Fortran and co don't need/use any C ...

      They don't link against libc? Have you ever looked at the link lines for any of the languages you mention, and you have the gall to call the OP an idiot?

    26. Re:But why? by Anonymous Coward · · Score: 1

      I think that you are missing the point.

      [I'm an expert in C with 20 years of very successful career writing professional embedded software using it.]

      But I would still choose to program in any of the modern compiled languages over C.

      Why? Because it is very hard and very time consuming to write professional quality code in C. Modern languages try to automatically handle the things that programmers (both good and bad) repeatedly get wrong.

      Perhaps you are a true coding genius that can write really excellent C code. If you are then I would say that would put you in the 0.01% of all C programmers, and I congratulate you.

      But perhaps more likely you have a somewhat over inflated opinion of how good your C programming skills really are, and perhaps you might start to wonder why none of the new programming languages look anything like C.

    27. Re:But why? by phantomfive · · Score: 1

      With swig, you can write a C library and automatically use it from 17 different languages. It's cool that Rust is adding compatibility with Python, but they have a ways to go before they come anywhere close to the portability of C.

      I'm looking forward to the Rust community adding these features.

      --
      "First they came for the slanderers and i said nothing."
    28. Re:But why? by MichaelSmith · · Score: 1

      Its a fact of life that you have a progressive stack from hardware to microcode to machine code to assembly code to C and to a VM. C has to be there and yes its hard to write securely. CPython is written in C. Whats the alternative? There has to be something outside the VM.

    29. Re:But why? by chuckugly · · Score: 1

      Yeah, that's why no modern multicore computer runs a kernel written in C. Please by all means, keep digging that hole.

    30. Re:But why? by Jeremi · · Score: 1

      Why use the new language of the month when C has been around for decades, is welll understood and does exactly what we want?

      If C did exactly what we want, there wouldn't be buffer-overflow exploits in any C code. The fact that we receive security advisories on a regular basis regarding C-based software shows that our C code often does rather more than we intended it to.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    31. Re:But why? by Jeremi · · Score: 1

      Its a fact of life that you have a progressive stack from hardware to microcode to machine code to assembly code to C and to a VM. C has to be there and yes its hard to write securely. CPython is written in C. Whats the alternative?

      There was a time before C existed, and people were able to make their computers function even then. The ubiquity of C is a historical accident, not an inevitable conclusion; the layers of functionality we currently implement in C could just as easily have been implemented in ADA or Pascal FORTRAN or some other language, had history gone down a slightly different path.

      C is definitely useful, but not uniquely so. If Rust can give us the benefits of C (low-overhead computation and low-level control of the hardware when necessary) without the drawbacks (undefined behavior, programs that are insecure-by-default), and overcome C's huge installed-base inertia, then more power to it.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    32. Re:But why? by MichaelSmith · · Score: 1

      There are some places where C is useful

      C underlies everything you use. Its in the firmware, the OS, the virtual machines and the compilers. Most things run on C. And yes, many applications these days are better written in a higher level language than C.

      I am a former C coder and current python coder.

    33. Re:But why? by MichaelSmith · · Score: 1

      To do that Ada, Pascal and FORTRAN would have needed more low level features, which make them both useful and insecure. In other words, something like C has to exist. C is in some respect, a super macro assembler. Tied to the machine and the OS if it exists at all.

      Rust would have to exist between C and python.

      A friend of mine who did a lot of Ada programming told me that his project turned off array bounds checking because it was just too slow for their application to function. There is little difference between that and coding the app in C.

    34. Re:But why? by AndroSyn · · Score: 1

      Do you have an HDMI TV? Have you noticed that it takes many 10's of seconds to turn on?

      There was a brief period in history where TVs came on instantly, post-tube era, but pre-HDTV. So like..mid 1980s to late 90s-early 00s?

      Now we have TVs that take longer to come on than the old tube sets took to warm up. So much for digital making everything better :(

    35. Re:But why? by theweatherelectric · · Score: 1

      C has been around for decades, is welll understood and does exactly what we want?

      Because it doesn't do exactly what you want. Decades of C usage has lead to decades worth of security problems. The history of security flaws in programs written in C has been a costly one. Rust doesn't solve the whole security problem but it offers memory safety features that C doesn't.

    36. Re:But why? by theweatherelectric · · Score: 1

      Learn to program. Learn your tools.

      Decades worth of security problems have clearly demonstrated that no one has learnt to program and no one has learnt their tools. It's naive to claim otherwise.

    37. Re:But why? by theweatherelectric · · Score: 1

      Unless you believe, as I do, that the majority of those security problems stem from dev cycle time pressure, mismanagement, and inadequate QA.

      So your argument is that it is more difficult and it takes longer to get C programs right and, as a consequence, C creates organizational complexity and overhead.

      You've made a strong case for everyone to save time and money by using Rust.

    38. Re:But why? by dog77 · · Score: 2

      Are you sure the tv was not slow because it was running Linux? I have seen a number of Linux based products running on embedded hardware, that take longer than 10 seconds to boot up. Maybe because they were not optimized, under powered, or special hardware bring up but I do see it happen. On the other hand, I don't think using Java or even something slower like python for the user interface would actually make much of a difference for the boot time.

    39. Re:But why? by theweatherelectric · · Score: 1

      There's no silver bullet, and the problems are institutional, not technical.

      The technical problems create the institutional problems. You said you need more support and hand-holding to develop in C. You said you needed management to cosset you and QA to find your mistakes for you.

      Rust helps you make fewer mistakes and to be more independent.

    40. Re:But why? by LightningBolt! · · Score: 1

      > Rust? Which compiles to LLVM? Which is written in C++? Which uses the C runtime?

      Your ignorance is truly on display now.

      --
      Old people fall. Young people spring. Rich people summer and winter.
    41. Re:But why? by Baloroth · · Score: 1

      Why use compiled language of the month when assembly has been around for decades, is well understood and does exactly what you want?

      If you need the low-level optimization available with assembly and not compiled languages, sure, go ahead. There are people who can and do exactly that, when even C isn't lean enough. As far as "why C?", well' it's simple. C has been around for 40+ years, supports every kind of system on the planet, has the largest set of libraries in the world, and has compilers so optimized they can spit out assembly that runs nearly as fast as if it was hand-optimized. When Rust can claim, say, half of those qualities, to half the same degree (hell, I'll be generous: a quarter), maybe it'll be something the average programmer should pay attention to. Until then, like dozens of other flavor-of-the-year languages, maybe it's worth using for specialized tasks, but it should barely register for most programmers.

      --
      "None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
    42. Re:But why? by theweatherelectric · · Score: 1

      These have nothing to do with the technical features of the language.

      Review what you have previously said. You said C is more difficult to use and takes longer to get right. The technical features of the C language create the necessity of an organizational perfection that will never exist.

      Rust eliminates some classes of mistakes

      So you agree Rust helps you make fewer mistakes and saves time and money over C. We're not actually arguing here.

    43. Re:But why? by LightningBolt! · · Score: 2

      > Completely impossible in C as C has nothing that resembles interfaces.

      There are a couple reasons you are incorrect on this.

      First, an "interface" has a few meanings in software development. It can simply mean the boundary between functions. A function declaration in a header file is an interface by this terminology.

      Second, function pointers in C allow the type of interface definition I assume you are referring to (as in Go or Java for instance). The actual function called can be selected at runtime using this mechanism, and with a "self" struct pointer as a parameter, you can have all the functionality of an interface in other languages. Look at how COM objects can be called from and implemented in C for a good example of this (https://www.codeproject.com/Articles/13601/COM-in-plain-C). It's not quite as natural in C as in other languages, but it is certainly done.

      --
      Old people fall. Young people spring. Rich people summer and winter.
    44. Re:But why? by buzmeg · · Score: 2

      Are you daft, ignorant, or am I *completely* missing something. Rust is compiled. And memory management with the borrow checker is front and center even *moreso* than C and C++.

    45. Re:But why? by theweatherelectric · · Score: 1

      making mistakes you shouldn't be making anyway, if you know what you're doing

      You're arguing for a fantasy world that doesn't exist. This is naive. Decades worth of C usage has demonstrated that it will never exist.

      All you have done is effectively make the case for the necessity of languages like Rust. You have convinced me that Rust is the better choice over C.

    46. Re:But why? by theweatherelectric · · Score: 1

      They don't link against libc?

      That is correct. Free Pascal, for example, doesn't link against libc unless you use libc directly or use some library which depends on libc. Free Pascal is not dependent on libc.

    47. Re:But why? by UnderCoverPenguin · · Score: 1

      Rust would have to exist between C and python.

      Rust is a compiled language. Presumably, the first Rust compiler was written completely in C, with newer versions having progressively more Rust source.

      Obviously, Rust, with it's run time checks, can't match the performance of C without those checks.

      A friend of mine who did a lot of Ada programming told me that his project turned off array bounds checking because it was just too slow for their application to function. There is little difference between that and coding the app in C.

      A co-worker told me that early C compilers put bounds checking (and other checks) in to the generated code. He and his classmates routinely disabled the checks, only turning them on to demonstrate their code passed the checks.

      I see no compelling reason to switch to Rust. If having those run time checks "built in" is desirable enough, I think it would make more sense to re-introduce those checks to C compilers, (Yes, I know, Rust has other features "built in", but most, if not all, of those features are available in libraries with many years of use and testing. (They might even be used by Rust.))

      --
      Don't try to out wierd me, three-eyes. I get stranger things than you, free with my breakfast cereal. --Zaphod Beeblebr
    48. Re:But why? by Per+Wigren · · Score: 1

      Just because it's possible to write linearly scaling highly concurrent large applications in C or C++ does not mean that it is not cumbersome compared to writing them in languages whose paradigm and conventions are scalable and concurrency safe by default. With C and C++ you have to really go out of your way to make your application make efficient use of all your 24 CPU cores (or even just 4), but with some languages fine-grained concurrency comes naturally. The natural, streamlined way to write C and C++ applications leads to single threaded or one-thread-per-major-task programs.

      --
      My other account has a 3-digit UID.
    49. Re:But why? by theweatherelectric · · Score: 1

      To do that Ada, Pascal and FORTRAN would have needed more low level features

      Pascal has the same low level features as C with a better type system and optional bounds checking. Pascal gives you the same power as C with better safety.

      Strings and dynamic arrays are a good example. Strings and dynamic arrays are far easier to work with in Pascal than in C. They're both reference counted in Pascal as part of the core language. It makes things much simpler.

      But equally if you really want to manage memory manually in Pascal then you can choose to do that too.

    50. Re:But why? by theweatherelectric · · Score: 1

      Presumably, the first Rust compiler was written completely in C

      No, the Rust compiler was written in OCaml before it became self-hosting.

    51. Re:But why? by DrXym · · Score: 1

      Yes C is well understood, as are the multitude of problems that come from programming in it.

    52. Re:But why? by DrXym · · Score: 1

      Rust uses LLVM as its backend, same as the Clang C/C++ compiler. It's not an abstraction of C, but it can link with code written in C relatively easily.

    53. Re:But why? by DrXym · · Score: 1
      Rust compiles to just about anything supported by LLVM, which is a lot of targets but includes Windows, BSD, Linux, iOS, Android + various others including bare boards, How much portable do you want it?

      In my experience code is also very portable because the toolchain, package management and stdlib work the same across platforms. The stdlib comes with thread, socket, path, file & io functions that do more to hide OS differences than C or C++. And for that matter, the toolchain supports cross compilation out of the box - just use rustup and add the target you want to build for.

    54. Re:But why? by DrXym · · Score: 1

      Yeah because C is a MANLY language.

    55. Re:But why? by DrXym · · Score: 2
      Rust is not an interpreted language. It compiles to machine code. In fact it compiles to machine code using the same compiler as clang - LLVM. And if you're worried about people learning memory management then you would appreciate the Rust compiler because you won't be compiling anything until you do.

      Performance wise, the code runs about the same as the equivalent in C.

    56. Re:But why? by Anonymous Coward · · Score: 1

      Neither Go nor Rust are interpreted, AFAIK

    57. Re:But why? by DrXym · · Score: 1

      Did your 1997 browser have multiple tabs open, each running megabytes of javascript, css and content from multiple domains, complex layouts and streaming video and audio? That's what a modern browser has to face.

    58. Re:But why? by DrXym · · Score: 1
      If I am writing mission critical software, or software which is handling untrusted data, or simply prefer happy customers instead of angry ones then I care less about how "wonderful" a language and more about the stability and reliability of what comes out the other side.

      Rust is getting a deal of traction because it stops C or C++ bugs by design. For example the null pointer has been described as the billion dollar mistake. Rust doesn't use pointers in normal safe programming, and so at a stroke it eliminates an extremely common runtime error. Memory allocation is via lifetime tracking in the compiler, so memory leaks and dangling pointers are another problem gone. And things like threads, file io & sockets are RAII so they close when they come out of scope. Lots of things like this add up to less bugs.

    59. Re:But why? by gweihir · · Score: 1

      You never will be CTO/CIO in my company ...

      No need, I am already CTO in a company that actually does understand technology.

      Incidentally, all that stuff you describe is "business coding", nothing complicated in there. Just one big mess of glue. And usually one big mess of not understanding what is actually going on. I deal with that daily.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    60. Re:But why? by gweihir · · Score: 2

      Indeed. An interface is a concept on architecture level, not on language level. You can implement interfaces in _any_ language. But all those wannabe "coders" think it is the language that provides the interface. Classical case of not understanding abstraction and why it is important. No surprise there is so much badly structured code out there.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    61. Re:But why? by theweatherelectric · · Score: 1

      has the largest set of libraries in the world

      How do you know? Are you sure Java isn't bigger? And if I use a language like Pascal which can use C libraries in addition to Pascal libraries, doesn't that mean the set of libraries available to Pascal is bigger?

    62. Re:But why? by jovetoo · · Score: 1

      I will believe that if I see real programs running in Rust, something that is intensively multi-threaded and uses complex memory structures.

      I believe their single ownership requirement will cost them dearly, because of single ownership and lack of pointers, complex tree structures are difficult. You will have to work with arrays of objects and store indexes to objects instead of pointers or do a lot of copying: circular lists, queuing the same buffer at multiple sockets, hash tables for multiple indexes, ...

      It will work but then you are designing your program to work around your language limitations...

    63. Re:But why? by angel'o'sphere · · Score: 1

      You want to tell me, your company is writing their business applications in C?
      Sorry, I don't believe that.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    64. Re:But why? by angel'o'sphere · · Score: 1

      Pointers and pointers to functions have nothing to do with an interface.

      You could argue that you could define an "interface" by simply declaring some functions in a header.

      Then a/the corresponding C file would be the implementation. But that would be on a very low level. E.g. you usually would need tricks and dynamic library loading to have more than one implementation in your code.

      COM is actually an interesting example :D Lucky I have no longer to program for that bullshit and IUNKnown or however the first interface in the chain was called.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    65. Re:But why? by angel'o'sphere · · Score: 1

      An interface is a well defined term, the wannabe expert here is you.

      If you want to talk in C, then it is an API you define and not Interface.

      If you want to do C talk and talk about interfaces, then put them in quotes. Because most of your talk you only are riding the anti pattern "intellectual violence" and unfortunately you are very bad at it :D

      Again: on a language level C has no interfaces. If you don't agree, you have a mental problem. A header file defining a few C functions can barely be called an interface. And it is not abstracting anything away.

      If you want to talk about interfaces, then Pascal units would have one, e.g. or Modual 2 definition modules would be some, or a C++ class with _only_ pure virtual functions would be one, or a Java/Scala/Groovy interface "class" would be one, or the C# equivalent ofc.

      Nitpicking alone does not make you right, it only makes you look like an idiot.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    66. Re:But why? by angel'o'sphere · · Score: 1

      Linking to a library is not a "runtime."

      Perhaps you should get a dictionary of terms?

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    67. Re:But why? by DrXym · · Score: 1
      Real programs are running Rust. Firefox for one, but also many others. e.g. Dropbox uses Rust for its cloud storage servers.

      And ownership isn't difficult but Rust will force you to define it. If you want to build trees, acyclic graphs or whatnot you can use an Option, or something like a Weak reference.

      If you were absolutely desperate to mimic the way C did something (e.g. to interoperate with some 3rd party library), you could even use pointers and nulls from inside an block marked unsafe. e.g. the openssl bindings for Rust call out to C code but they wrap it all up in some nice RAII objects.

    68. Re:But why? by chuckugly · · Score: 1

      C++ and AMP.

      How hard was that, really?

    69. Re:But why? by chuckugly · · Score: 1

      Or .... std::async ....

    70. Re:But why? by gweihir · · Score: 1

      I really do not care to address your insight-resistance and your superficial grasp of software engineering. That is why I will stop responding now.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    71. Re:But why? by gweihir · · Score: 1

      He very likely does not. Good point and an extreme fail on his part. Fits right in with his other statements though.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    72. Re:But why? by Tough+Love · · Score: 1

      Why use the new language of the month when C has been around for decades, is welll understood and does exactly what we want?

      You get 1 out of 3: C has been around for decades. It is not well understood in the sense that the average programmer who thinks they have mastered it is actually a hazard to security and reliability. C certainly does not do what we want, on many levels. Just picking one off the stack: generic programming in C is a pathetic fuckfest.

      Rust is hardly "of the month". The same genius is behind it who developed the direct ancestor of Git.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    73. Re:But why? by Tough+Love · · Score: 1

      Me? I write in C.

      Hang yourself up on a hook in a museum right next to the Underwood typewriters.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    74. Re:But why? by Tough+Love · · Score: 1

      C is a MANLY language.

      I cee.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    75. Re:But why? by Tough+Love · · Score: 1

      C was never awful, It is and has always been a wonderful language.

      Well, except of a smattering of abominations here and there such as zero terminated strings, a few operator priority gaffs, some nutsoid syntactic ambiguities, macro language designed to make you slit your wrists, and missing almost everything you need for large scale software engineering.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    76. Re:But why? by theweatherelectric · · Score: 1

      You're right. It's naive of me

      So again you admit Rust is the better choice over C. I don't know what you're trying to argue. You've done nothing but agree with me.

      chasing that silver bullet

      Whoever said anything about a silver bullet?

    77. Re:But why? by theweatherelectric · · Score: 1

      What I'm arguing

      No. You've tried to mount a defense for C's shortcomings but you've failed. All you've done is make the case that Rust is a better choice than C.

    78. Re:But why? by jovetoo · · Score: 1

      I am not desperate to do things the way C/C++ did them, I just want to make sure I eliminate unnecessary copies, allocations and locking. It's not because the Rust compiler hides those that they are gone, it just means you have to be a Rust expert to understand when they are done.

      From what I read of your links about using Weak and std::rc, things certainly haven't gotten any less complex. So first they introduce ownership, then they go and recreate C/C++ pointer semantics?

      If I ever get a job where I need to write code in Rust, I will. Until then, I'll stick to what has served the worlds programming needs for over 34 years.

    79. Re:But why? by theweatherelectric · · Score: 1

      You've completely missed the point

      You didn't make one other than to tell me to use Rust instead of C.

    80. Re:But why? by theweatherelectric · · Score: 1

      Now you're just getting petty. It's true that C has let you down but it's time to let it go.

    81. Re:But why? by DrXym · · Score: 1
      Compiled performance in Rust is largely equivalent to C or C++ as is memory usage. E.g. if you use a Vec in Rust or a std::vector in C++ they have similar memory allocation behaviour. Rust isn't hiding what it's doing - if you want a var on the stack, you declare it in scope just like a var in C. If you want to create it on the heap you use a Box which is basically a scoped pointer. The code that comes out the other side is functionally and performantly equivalent to code in C. It doesn't force you to do unnecessary copies, allocs or locks any more than the same code in C or C++, assuming that code was written safely.

      An Option isn't recreating pointer semantics. It is explicitly stating that the value is nothing, or something. That something could be a primitive, a reference to an object, an actual object, an array of objects, a tuple etc. So a node in a tree may or may not have a parent. You'd only use Option if that's even a possibility for what you're holding otherwise you directly reference the value and it cannot be null. It's not like a C/C++ pointer where calling something without checking for null will blow up at runtime, or where the non-value might be a dangling pointer. For the code using Options to compile you have to explicitly unwrap the value in code to use it which demonstrates coding intent.

    82. Re:But why? by dwarfking · · Score: 1

      x) Abstracts work into reusable components Close to impossible in C, as C is not object oriented. You are stuck with simple libraries like stdio and math etc.

      See Cfront the first C++ translator that output C code for a C compiler. There is nothing fancy about class-based OO. Every method in your class is nothing more than a C method with an additional hidden variable this. The member attributes are the same as C structure attributes, the compilers simply recognize more protection levels and won't let code read private data directly. If you want data protection, define an opaque C structure and a collection of get/set methods that take a pointer to that structure as the first argument. Your OO code is doing exactly the same thing only hiding the details from you. The one area of OO that C doesn't do as well is RAII more specifically the auto cleanup of a resource. Being able to run a cleanup routine when a structure leaves scope is not well defined in C, usually it is a compiler specific capability.

      x) Abstracts interfaces into functional, communicable units Completely impossible in C as C has nothing that resembles interfaces.

      An application programming interface is nothing more than the definition of functions and/or protocols that can be called. C has had header files for a very long time that are just as much an interface definition as any OO based one.

    83. Re: But why? by sellibitze · · Score: 1

      I don't see why that should be the case. While interfacing languages like Python and Rust typically requires a C interface—C being the lingua franca—Rust code could still internally make use of safer alternatives, effectively reducing the attack surface. I say that even without having checked how all those mentioned projects ease the Python/Rust integration.

      What's your argument for the unavoidable performance regressions? Rust achieves most of its safety using compile-time checks based on better type system. Those don't incur any runtime penalties. The way abstraction works in Rust is pretty much the same as in C++ and sometimes even better than that. I can even give you multiple examples for that if you care to check it out off the top of my head:

      • In C and C++ functions decay to pointers. In doing so, the behaviour of the function is not preserved its type which makes inlining more difficult for the compiler. In Rust the name of a function is a unique type which preserves its behaviour in its type. Passing that to a generic Rust function easily allows the function to be inlined in the generic method.
      • The overhead of type erasure in C++ is higher than in Rust. See C++'s std::function versus Rust's Box<Fn>
      • C++ and Rust both offer "futures" as part of the standard library or a popular and easily installed crate. Rust's futures are lower overhead and don't require as many dynamic allocations when composing them.

      Which of Rust's design choices am I missing that supposedly intrinsically imply a runtime penalty?

    84. Re:But why? by sellibitze · · Score: 1

      Where do you draw the line, though? What does it mean to be able to handle C? How many memory safety and data-race bugs are you allowed to introduce by accident if you pride yourself to be among those able to "handle C"? Zero? How many coders do you think would be left after you ditched everyone who produced at least one memory safety issue in their life? Why risk security critical bugs to be detected so late by attackers instead of early at compilation? Where's the logic in that?

    85. Re:But why? by sellibitze · · Score: 1

      Not sure what this has to do with "We need to ditch C". A safer C alternative doesn't necessarily imply a performance regression.

    86. Re:But why? by sellibitze · · Score: 1

      "Modern Coder"—we're in a thread about Rust—doesn't imply ignorance about how computers work. Being into a new language like Rust does not imply that one doesn't know how to write code that performs well. You guys need to ditch the preconceived notion that "new/modern" necessarily implies being more disconnected from the bare metal. It doesn't. See Rust. Yeah, C is kind of awful IMHO. I don't like the (lack of) type safety. It's very limited in terms of ways to express abstractions. It's just a "portable assembler" with objectionable defaults. Your sentiment makes me believe that you don't know what else is out there besides C, C++ and a whole bunch of "I-don't-know-what-I'm-doing-please-give-me-training-wheels" languages like those that are interpreted or run on cushy VMs.

    87. Re:But why? by phantomfive · · Score: 1

      That's good to know, thanks.

      --
      "First they came for the slanderers and i said nothing."
    88. Re:But why? by angel'o'sphere · · Score: 1

      Rofl, besides insults, you did not contribute much to our two different threads of conversation.
      FYI: I'm an expert in software engineering (amoung other areas of software development), but most likely you again misplaced your dictionary and mean something different with the term 'software engineering' than the rest of the world.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    89. Re:But why? by angel'o'sphere · · Score: 1

      There is nothing fancy about class-based OO.
      Stop nitpicking.
      If you need to do it by hand: then it is!

      C has had header files for a very long time that are just as much an interface definition as any OO based one.
      No they are not. Header files and corresponding *.o files or *.libs are not comparable with what interfaces are in other languages.

      If you would spent your time with learning something you don't know instead of nitpicking over stuff you barely know you would not make such posts, facepalm.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    90. Re:But why? by jovetoo · · Score: 1

      From what I read, a Rust Weak pointer is exactly like a weak pointer in C++, an Option is a container that can contain nothing (I don't see the functional advantage compared to a weak pointer). As I see it, the main difference between C++ and Rust from a language point of view is that Rust has a lot stricter rules for basic languages constructs than C++ (specifically, pointers and memory management) and those rules are enforced by the compiler. Once you need more advanced features, you start using the standard libraries and all the advantages of Rust disappear.

      Why would I, as an experienced programmer, drop a language that has tons of proven libraries for a language that has mainly features that suit beginners and virtually no established code base?

      And *if* a new language is required, why Rust over the dozens of other alternatives?

    91. Re:But why? by erapert · · Score: 1

      Indeed. The programming language shootout is showing Rust almost matches C-- yes, C-- for speed. Not that surprising really since Rust uses LLVM for its compiler back end.

    92. Re:But why? by DrXym · · Score: 1
      The compiler enforces the rules for the standard libraries. e.g. It won't let me share reference to an object between threads unless the object is protected with an atomic reference count or read/write lock. It won't let me send an object from one thread to another unless it is marked as safe to send. It won't let me copy an object unless it implements a Clone trait and so on. It

      A weak pointer is a reference to something without affecting its lifetime. So if I had a bunch of nodes pointing to each other they could hold weak pointers and I would actually control their life time from a master list or something. That could be one way of doing it. An option - something or nothing might be used to hold a strongly reference counted, allocated Node, e.g. Option> - or nothing. I think the master list would be safer in an acyclic graph because nodes could self reference without causing issues.

      As for why not other languages, probably because there isn't anything close to Rust for writing systems programming. If you're building a higher level application there are plenty of choices depending on your runtime performance requirements and tolerance for failures. e.g. graphical / enterprise apps might think of using Java, .NET, Ruby, Python, Go, Swift, C++, NodeJS depending on what they do. Generally even there C++ has been squeezed out because stability is seen as more important than performance. The likes of Go & Swift try to strike a middle ground, being compiled languages with GC and are gaining some traction.

      At the systems level performance, memory and correctness does matter. Rust offers the same characteristics as C or C++ but stops many problems dead in their tracks. This is a compelling reason to use it, especially for people who don't like software to ship with bugs or exploits due to weaknesses in the language.

    93. Re:But why? by sellibitze · · Score: 1

      The abundance of kernels written in C does not prove the point you seem to be trying to make.

    94. Re:But why? by sellibitze · · Score: 1

      Funny you should mention that. Of course, you could compare what the libraries for C++ and Rust have to offer. And obviously they are restricted by what the language allows you to express. The existing libraries don't necessarily represent what's possible to express in the respective languages. But yeah, let's compare things like C++'s std::async/std::future/std::function against their Rust equivalent. I'll help you out as I'm already familiar with both, C++ and Rust. C++'s version of std::future and std::function has type erasure baked into its design which means indirections which means it's harder to inline stuff. Rust's futures and functions compose better with lower overhead. Composing futures in Rust using methods like "and_then" don't require extra memory allocations and end up being rather efficient state machines when compiler optimization is turned on. That's not really a difference between the power of C++ versus Rust. It's a design trade-off for some library component. You could build a C++ library just like that. But the C++ standards committee didn't.

    95. Re:But why? by chuckugly · · Score: 1

      The post I replied to said :"But for today's 48 core CPUs, C is a very poor choice, because it does concurrency badly.", which I still think is a foolish statement given that (almost) every kernel ever and a lot of very concurrent applications software is written either partly or completely in C. I never said it was the best choice for every application. I would say that Rust is close to the worst choice.

  2. Fuck off with Rust spam by Anonymous Coward · · Score: 3, Informative

    And wake me up when Rust stop being a cult and becomes an actually useful language.

    1. Re:Fuck off with Rust spam by Anonymous Coward · · Score: 1

      You could say it's a ... cargo cult.

    2. Re:Fuck off with Rust spam by angel'o'sphere · · Score: 1

      For tha we would need to know your bitcoin address!

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  3. The future of rustlang is tied up with Mozilla by mnooning · · Score: 5, Insightful

    I've read a third of the Rust nightly book and watched many, many Rust videos on youtube. I like Rust very much. However, I believe Rust was invented by, is sponsored by, and gets it's major funding from the Mozilla foundation. There is essentially no more Mozilla Thunderbird, and the Mozilla Firefox browser is getting significantly less usage. We've had articles on such here on Slashdot. If the Mozilla browser itself falters any more, would Mozilla, and hence rust, stay alive?

    1. Re:The future of rustlang is tied up with Mozilla by NoNonAlphaCharsHere · · Score: 1

      Let's talk about Sun Microsystems...

    2. Re:The future of rustlang is tied up with Mozilla by loonycyborg · · Score: 2

      I don't think that existence of Mozilla will be the deciding factor of the success of the language. For example, no particular corporation was supporting C++ initially, and even now core C++ design is done by volunteers. Even if Mozilla goes bankrupt a community can still thrive around the language if it deserves it. If not then it'll eventually wither in any case, even if Mozilla ends up thriving.

    3. Re:The future of rustlang is tied up with Mozilla by Anonymous Coward · · Score: 1

      C++ was heavily supported by Bell Labs and then became an ISO standard.

    4. Re:The future of rustlang is tied up with Mozilla by Anonymous Coward · · Score: 1

      ...no particular corporation was supporting C++ initially...

      Are you really so ignorant that you never heard of AT&T Bell Labs?

    5. Re: The future of rustlang is tied up with Mozilla by Anonymous Coward · · Score: 1

      What about them?

      They created a useful language in Java that was adopted by many major industry users. There were even several independent, and very usable, implementations of things like the compiler, VM, and standard class library.

      Even now, years after Sun disappeared, Java is still going very strong, and seeing frequent updates from Oracle. Its development process is now more open and community-based than it was during the Sun days.

      Java is the language of business, and likely will be for decades to come. It's the language of Android, the most popular OS. It's even still the language of education, although Python is challenging it.

      It should be obvious that Rust is nothing like Java is, or even Java was at a similar point in its lifecycle. Compared to Java, Rust is a complete failure. It has one implementation. The only major user and benefactor, moz://a, appears to be a slowly dying organization. Its community is widely disliked.

      Java will be going strong a decade from now. Rust will likely have been almost completely forgotten by then.

    6. Re: The future of rustlang is tied up with Mozilla by NoNonAlphaCharsHere · · Score: 1

      So you're saying a language that people find useful could persist without the company that created it continuing to exist? Huh. Never thought of that.

    7. Re:The future of rustlang is tied up with Mozilla by Cyberax · · Score: 2

      At this point, probably yes. There's a critical mass of Rust-based projects, enough to continue maintenance and development of new features.

    8. Re:The future of rustlang is tied up with Mozilla by jma05 · · Score: 4, Informative

      Python and Perl would have never made it, if people filtered by that logic.

      Programming languages don't need a huge company backing them up, as long as there is enough of a community. If Rust folks are as zealous as the Ruby folks were during the Rails era, we will have a neat C++ replacement.

      I have not used Rust yet and have even been critical (as in, just add those semantics to C++ somehow and don't create a whole new replacement) of it. But the community does seem to be building momentum.

      A peek at module counts
      http://www.modulecounts.com/
      shows that the Rust community is quite active. They are not merely evangelizing it, but rapidly building value. It does not look like Mozilla is significantly driving it on the module front. It only has half the modules as Go (which is impressive for a zero-cost abstraction language compared to a language that is high level application language), but the modules seem to be accumulating at more than twice the speed now. Modules make the language.

      I wish Nim had that kind of momentum though. That is a language better aligned for my purposes.

    9. Re:The future of rustlang is tied up with Mozilla by Desler · · Score: 1

      For example, no particular corporation was supporting C++ initially

      Bell Labs was a corporation last time I checked.

    10. Re: The future of rustlang is tied up with Mozilla by petermgreen · · Score: 1

      Sometimes you have to try a design idea in the real world to see the problems with it that aren't apparent at a lab scale. So you make your initial design everything seems good at lab scale, so you push it out to the real world, the cracks then start to show.

      Do you have your language evolve to fix the design issues, possibly at the expense of backwards compatibility or do you build up layers of cruft as new stuff is added but the stuff which didn't really work out right sticks around.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    11. Re:The future of rustlang is tied up with Mozilla by terjeber · · Score: 1

      Let's talk about Sun Microsystems

      You do realize that when a company is bought by another, and the buyer invests resources into the products of the company bought, that it continues to exist, right? Do you think that someone would buy Mozilla for anything but it's users? It no longer has any products that are attractive.

    12. Re:The future of rustlang is tied up with Mozilla by sellibitze · · Score: 1

      From all the programming language projects Rust seems to be among those with the most open developtment process. A lot of work is already done by people that aren't paid by Mozilla. To me this looks rather healthy. Good community, open and welcoming development process. Time will tell.

  4. What happens to Rust when Mozilla is gone? by Anonymous Coward · · Score: 3, Insightful

    Rust is very tied to Mozilla. And Mozilla's only remaining "successful" product is Firefox. But Firefox's market share is dropping. It was only a few percent, last I saw, while Chrome is over 50%. Mozilla reportedly gets a lot of funding from Yahoo, due to a Firefox search deal. So here we have an organization with one major product, but this project is being rejected by consumers, and what might be this organization's most significant source of revenue comes from this failing product and is paid for by another company that isn't doing so well. I fear for Mozilla's future if, say, the Yahoo deal wasn't renewed and they couldn't find a replacement.

    If Mozilla goes the way of the dodo bird, then I can't see the Rust project really going anywhere. I don't think it has a robust independent community like C++ has, for example.

    I think it is too risky to adopt Rust, especially for important long term projects. The tech industry moves fast. Rust could plausibly be gone in 3 years, while languages like C, C++ and even PHP are far more likely to be going strong.

    1. Re:What happens to Rust when Mozilla is gone? by gweihir · · Score: 2, Informative

      As C has been constantly in the top 3 languages that coder positions are offered for and C does not tie you to a SJW infected cult, this is not even a valid comparison. Rust is a hype-du-jour, with its proponents blind to its shortcomings. They are retards that still think coding is all about the language you do it in (which is about as far from the truth as you can get, and which has been known to smart people for something like half a century) and Rust is their chosen deity that can do no wrong.

      When Mozilla collapses, Rust will be gone as well. It really has not many things to recommend it, but some major shortcomings including the rabid and insane Rust community.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    2. Re: What happens to Rust when Mozilla is gone? by Anonymous Coward · · Score: 1

      Retards also claim that good tools GENERALLY lead to better outcomes. Programmer skill is obviously important. Good tools are obviously important. Not understanding that is impressive, and not in a good way.

    3. Re:What happens to Rust when Mozilla is gone? by K.+S.+Kyosuke · · Score: 1

      They are retards that still think coding is all about the language you do it in (which is about as far from the truth as you can get, and which has been known to smart people for something like half a century

      Smart people have also claimed the exact opposite.

      --
      Ezekiel 23:20
    4. Re:What happens to Rust when Mozilla is gone? by ShanghaiBill · · Score: 5, Funny

      As C has been constantly in the top 3 languages that coder positions are offered for

      But those "coder positions" are for white males only. C was designed in the 1960s, when colonialism was still rampant, and that is reflected in the language design. C ignores array bounds just as the imperial powers ignored the boundaries of tribal societies. Rust can free us from syntactic oppression, and provides "safe spaces" for everyone's data regardless of their culture or previous gender.

    5. Re:What happens to Rust when Mozilla is gone? by angel'o'sphere · · Score: 1

      Honestly, I rather code in Rust than C.
      Yes, a lot of coding *is* about the language, and the eco system of tools and libraries in that "platform", that is e.g. why Java is so widely successful. As a language It is just a simpler C++ but with VM and libraries and tools it is far beyond everything else.
      E.g. I never would code in VB ... (regardless of old or .Net), it makes me eye cancer and brain cancer same time.
      I rather take the bullet and code in Lisp/Scheme ... and get lost in the labyrinth of braces ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    6. Re:What happens to Rust when Mozilla is gone? by angel'o'sphere · · Score: 1

      Exactly.

      And that is why we still see ppl on /. who argue functional or object oriented is evil.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    7. Re:What happens to Rust when Mozilla is gone? by K.+S.+Kyosuke · · Score: 1

      I find it hard to come up with scenarios in which exposing yourself to novel ideas can be considered evil.

      --
      Ezekiel 23:20
    8. Re:What happens to Rust when Mozilla is gone? by CustomSolvers2 · · Score: 1

      LOL to the n power. Unfortunately, I have no mod points left.

      --
      Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
    9. Re:What happens to Rust when Mozilla is gone? by angel'o'sphere · · Score: 1

      Exactly my point.
      However /. is full with people who consider "new things for nerds" evil instead of interesting.
      No one has to use Rust. But it has lots of nice features. Self proclaimed experts here should acknowledge that.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    10. Re:What happens to Rust when Mozilla is gone? by K.+S.+Kyosuke · · Score: 1

      Indeed it has. Nevertheless, the rather heavy footprint (and static nature, and other things) is unlikely to steer me away from Scheme. But I'm perfectly happy with people doing nice stuff in it.

      --
      Ezekiel 23:20
    11. Re:What happens to Rust when Mozilla is gone? by Anonymous Coward · · Score: 1

      simply brilliant ;)

    12. Re: What happens to Rust when Mozilla is gone? by F.Ultra · · Score: 1

      Is Firefox developed in Rust? Wonder since Firefox always (together with all other browsers) get's hacked at pwn2own.

    13. Re:What happens to Rust when Mozilla is gone? by c++horde · · Score: 1

      Honestly, I rather code in Rust than C. Yes, a lot of coding *is* about the language, and the eco system of tools and libraries in that "platform", that is e.g. why Java is so widely successful. As a language It is just a simpler C++ but with VM and libraries and tools it is far beyond everything else. E.g. I never would code in VB ... (regardless of old or .Net), it makes me eye cancer and brain cancer same time. I rather take the bullet and code in Lisp/Scheme ... and get lost in the labyrinth of braces ...

      I doubt you can code in either.

    14. Re:What happens to Rust when Mozilla is gone? by ShanghaiBill · · Score: 1

      Laugh if you must, but do you really think there will be justice in the world as long as a transgender person of color has to put an asterisk next to their address just to dereference their own data?

    15. Re: What happens to Rust when Mozilla is gone? by theweatherelectric · · Score: 2

      Is Firefox developed in Rust?

      It's just now starting to be. Mozilla's research browser, Servo, is written in Rust and they have started to integrate Servo components into Firefox. Components like Servo's WebRender significantly outperform other browsers.

    16. Re: What happens to Rust when Mozilla is gone? by theweatherelectric · · Score: 1

      It was the same test for all the browsers. Four times better than the next best is not an anomaly, it's a fundamentally better architecture.

    17. Re:What happens to Rust when Mozilla is gone? by UnderCoverPenguin · · Score: 1

      C ignores array bounds

      According to a co-worker of mine, that wasn't always the case.

      When he was a student in the early 1980s, the C compiler, installed on the BSD Unix systems at his college, generated array bounds checking, pointer de-reference checking and a few other run-time "sanity checks". He also said there were options to disable these features.

      While I can certainly understand that re-adding these checks to the code generated by the C compiler would reduce performance, I doubt it would be any worse than the performance of Rust (or most of the other "safer" languages).

      --
      Don't try to out wierd me, three-eyes. I get stranger things than you, free with my breakfast cereal. --Zaphod Beeblebr
    18. Re:What happens to Rust when Mozilla is gone? by h33t+l4x0r · · Score: 1

      They chose an unfortunate name for the language. "Rust" conjures an image of something old and discarded. How about "Shiny"? Or perhaps "SwingingDick"?

    19. Re:What happens to Rust when Mozilla is gone? by CustomSolvers2 · · Score: 1

      I am such an insensitive idiot! Sorry for having made fun of your brave struggle against the horrible programming-language creators, always trying to perpetuate unfair stereotypes.

      As a keepgender person with skin of some colour (#ffe0bd-ish), I feel the pain of my brothers and sisters forced to type symbols which, in certain contexts and for some people, might eventually have a somehow pejorative meaning for the community in which they are implicitly included on account of their generic features or life choices. I will join your noble efforts and stop using these tools of oppression right away: no more pointers in my C code until the language specs will be updated and more tolerant symbols included!

      Compliance with my self-imposed policy of tagging all my not-too-evident-for-everyone posts: LOL.

      --
      Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
    20. Re:What happens to Rust when Mozilla is gone? by DrXym · · Score: 1
      I can't even fathom what you're talking about here. The Rust community isn't "rabid". I'd also love to know what these shortcomings are and in what context. Or why Rust's success is tied to Mozilla when there are over 10,000 published packages for it and numerous external projects developed with it. Even if Mozilla died tomorrow (it won't), it's not like Rust would up and die.

      My own experience of the language is that it is very challenging to start, more so I suspect for people coming from C than perhaps a language like Java. No denying it. The compiler is very strict but the pay off is code that doesn't suffer the litany of runtime issues that happen in C or C++. Memory leaks, buffer over/underruns, dangling pointers, null pointer exceptions, data races. For systems programming or surfaces that should be hardened against attack that seems rather important don't you think?

      Does that mean I hate C or C++? Not at all. I write code in C and C++ all the time. And Ruby, Javascript, Java and other languages. I suspect many people in this "cult" as you call it do too. Stop seeing languages as a threat but something to embrace. If they die and fizzle out so what? You've still learned something.

    21. Re: What happens to Rust when Mozilla is gone? by DrXym · · Score: 1
      Bits of Firefox are being replaced with Rust code. And it is precisely because of hacking / exploits and performance that they're doing it. Writing code that withstands malicious data and input is incredibly difficult. And writing code that is safely concurrent is incredibly difficult.

      Rust has a lot of language design elements that make code far safer. For example there is no null pointer or pointers at all for that matter in normal safe programming. You declare an object, either on the stack, or the heap (e.g. via a box) and the compiler tracks how long it should live for and ensures that only one thing owns it or modifies it at a time. If you share an object (e.g. between threads) then you MUST protect it to prevent data races.

    22. Re:What happens to Rust when Mozilla is gone? by dbIII · · Score: 1

      When Mozilla collapses, Rust will be gone as well. It really has not many things to recommend it, but some major shortcomings including the rabid and insane Rust community.

      I have not been paying attention to Rust (I still see Python as that "new thing", like Perl but with whitespace, so haven't even looked at the newer trendier things) but you've got me curious now. What sort of things give the Rust community that reputation?

    23. Re:What happens to Rust when Mozilla is gone? by angel'o'sphere · · Score: 1

      Why should I be incompetent when I prefer Java and C++ over C?
      Or Scala over Lisp? Or Groovy for that matter?

      What has competence to do with this discussion?

      You can not do Aspect Oriented programming in C, well, there is an experimental tool chain for LLVM and C++, I guess a few parts would work for C.

      No idea why you are ranting so angry.

      C is for people who _need_ to use it for a particular reason. For everyone else it is a break, no idea why you want to argue about simple facts like this.

      The toolchain is important. Especially if you need to hire people who can operate, maintain and improve it.

      If you think otherwise, then you are incompetent, not me.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    24. Re:What happens to Rust when Mozilla is gone? by angel'o'sphere · · Score: 1

      I can code in basically every language (after fooling around a day with it, if it is an obscure language).
      My resume lists more than 30 I think.
      Of course, only because I had to use them in a certain project, not because I'm super fluent in them, e.g. my COBOL skills are basically non existing but where enough to do Y2k reengineering.

      I used Lisp in the university, but never liked it ... it was only a a few weeks for a course. A friend of mine jumped into it and became a kind of CLOS expert, but later moved to Python and now he works for SAP and mainly does Java.

      I would love if we would have a slightly tamed C++ for the JVM or a similar VM ... in the Java world we have so many tools and libraries based on reflection and byte code analysis/morphing ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    25. Re:What happens to Rust when Mozilla is gone? by CustomSolvers2 · · Score: 1

      FURTHER CLARIFICATION FOR PEOPLE WITH PARTICULARLY LIMITED UNDERSTANDING SKILLS: my reference to the #ffe0bd hex code colour was meant to be understood as white (caucausian or whatever the most adequate denomination is now). I made-up the word "keepgender" as a descriptive-enough way to indicate the opposite of transgender; I think that cisgender is the current politically-correct term.

      --
      Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
    26. Re:What happens to Rust when Mozilla is gone? by Tough+Love · · Score: 1

      Mozilla's only remaining "successful" product is Firefox.

      Give it a rest, anonymous cuck. Never heard of Thunderbird?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    27. Re:What happens to Rust when Mozilla is gone? by Tough+Love · · Score: 1

      How about "Shiny"?

      Forgettable. "Rust" is not forgettable.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    28. Re:What happens to Rust when Mozilla is gone? by DrXym · · Score: 1

      Thanks for your input anonymous idiot.

  5. Because of the cool acronyms by goombah99 · · Score: 2

    For example Py-CRust.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  6. Rust and SJW Nonsense by Anonymous Coward · · Score: 4, Insightful

    I was interested in learning Rust and perhaps using it for some personal projects, but then I discovered how the community seems to care so much about social engineering.

    We're not allowed to use "Master" and "Slave". https://github.com/rust-lang/rust-buildbot/issues/2

    We're required to rephrase old texts to fit into "gender non-binary" language. https://github.com/rust-lang/rust/pull/25640

    I'm sure they don't have problems "killing child processes" though...

    etc., etc.

    I'm not interested in using a programming language as some kind of social engineering experiment.

    1. Re:Rust and SJW Nonsense by Anonymous Coward · · Score: 1

      bad_style to be removed because it is "a rather rebuke-y shame-y annotation on code"
      https://github.com/rust-lang/r...

      "Reword 'stupid' and 'crazy' in docs."
      https://github.com/rust-lang/r...

  7. Why does Rust's community lack diversity? by Anonymous Coward · · Score: 3, Interesting

    What I don't get is why the Rust community lacks diversity, despite them putting so much emphasis on supposedly supporting diversity.

    Years ago, back when I was a Java developer, I would sometimes go to Java conferences. There would be men there. There would be women there. There were probably transsexuals there. There would be old adults and young adults. There would be people representing every possible skin color. There would be somebody from pretty much every major ethnicity. There would be practitioners of pretty much every major religion. There was true diversity, without anyone actually trying to impose it through Codes of Conducts and Moderation Teams and "initiatives" and "affirmative action".

    Yet here we have Rust, with its invasive Code of Conduct, and the Rust Moderation Team to force it on the community, and all of its focus on "diversity" and "social justice". But when we look at the profile pictures of Rust's contributors, they appear to mostly be mid-20s white males (I'm assuming "steveklabnik" is a male).

    Now don't get me wrong, there's nothing wrong with being a mid-20s white male programmer. This isn't about singling anyone out, or about claiming that some mythical "privilege" exists, or anything like that.

    The issue here is that it appears that the more that the Rust community intentionally pushes for "diversity", the less of that we actually see. Instead of seeing a naturally diverse community form on its own, like pretty much every other programming language has, we've seen Rust's community become extremely homogeneous.

    It's as if the Rust community's efforts to force diversity on their community has actually had the complete opposite effect! While trying to create the most diverse community, they've actually only managed to create the least diverse one I've ever seen!

    1. Re:Why does Rust's community lack diversity? by Anonymous Coward · · Score: 1

      > What I don't get is why the Rust community lacks diversity, despite them putting so much emphasis on supposedly supporting diversity.

      Because it simply can't be forced, and no one wants to be around assholes who force it except people who feel guilty, i.e. white people.

    2. Re:Why does Rust's community lack diversity? by 0123456 · · Score: 1

      In my experience, the people who demand 'diversity' the most prefer to live in white ghettos.

  8. By now the propaganda alone is reason to stay away by gweihir · · Score: 4, Interesting

    Something that gets this much hype cannot be good, or the hype would not be needed. Seems to me some cretins are using Rust as a religion-surrogate.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  9. Re:I'll never use anything from Mozilla. by Anonymous Coward · · Score: 1

    So what does your excellency suggest that is used instead?

    Chrome? Oh yes and pass every detail of what you are doing to Google to use in Adverts to you
    Edge? Ditto but for Microsoft.
    Safari? Well only for Macs.
    Opera? Is that still around?

    I use Firefox ESR with a classic theme. Hot seen any changes to it for years.
    not forgetting UBlock Origin and noScript. Makes the internet actually usable.
    No adverts. Deep joy.

  10. Python and LLVM by John+Allsup · · Score: 1

    Being able to represent the sort of thing you'd use C or C++ for as a data structure within Python, and then turn into binary via LLVM is something I've been wishing for for a long time. I imagine I'll need to keep wishing for a while longer, but things like numba (in python), and application of LLVM like LLVMPipe, and the Synthesis OS project from a few years back suggest the pieces for doing this are gradually appearing.

    --
    John_Chalisque
  11. Wake me up... by maestroX · · Score: 3, Insightful

    .. when Linus decides the next major release is to be written in Rust.
    Or for argument's sake, Mozilla itself.
    Every language has it pitfalls, at least with ye olde C/C++ I know where to look and what to expect.
    ...
    Suddenly you start to respect and embrace the get-off-my-lawn attitude, you simply want things to work rather than be written in the next greatest language of the moment.
    I think I'm ready to deal with my dad now :)

  12. Rust: an example of Autism-Driven Development? by Anonymous Coward · · Score: 4, Interesting

    I don't intend this to be taken as a joke in any way, nor do I intend it to be unnecessarily mean, but I think that the Rust community inadvertently discovered a new paradigm of software development: Autism-Driven Development.

    When we look at what they've created, both from a technological standpoint and from a community standpoint, I can't help but notice the impact that Asperger Syndrome may have had on how things have developed.

    Let's start with the community. While the communities of languages like Perl, C++, Python, Java and C# developed organically over time, it is almost as if the Rust community has been manufactured instead. It's like the community's interactions have been scripted, to use a programming analogy. It seems to me that the Rust Code of Conduct may actually be there as a way to allow people who suffer from varying degrees of social ineptitude to interact in a way that mimics how they see other, naturally-formed programming language communities made of sociable individuals interacting. They wouldn't be able to manage this social interaction on their own. But if you give them a script or a checklist they can follow, they can at least engage in something that appears, on the surface, to be socializing. That's why I think their incorporation of social justice is quite interesting. In many ways the concepts of social justice are all about imposing a foreign order on what is naturally a very chaotic and perhaps unfair reality.

    The language and its standard library also reflect behavior that may be expected from those suffering from Asperger Syndrome. While creating the language, it is as if its developers haven't been able to make the normal trade-offs that other language developers have made with ease. We've seen this result in Rust, as a language, constantly change over time. It's like they're striving for some unattainable form of perfection that most normal people would realize could not be attained. While other people would accept some drawbacks to their creation and move on, the Rust community appears to waver back and forth, unable to really make up its mind about how to proceed. Even the supposedly stable Rust 1.x release branch has seen 19 minor releases!

    I think the complexity of the language also reflects the role that, I suspect, Asperger Syndrome has had on the development of Rust. It has become an immensely complex and convoluted language, even compared to a rather complex language like C++. It's like the language has been designed, perhaps unintentionally, to be cryptic and unwelcoming to normal people. By its very nature it is like it is trying to be self-isolating, to avoid having to interact with the world and the people around it. Programming languages like Java, Python, C++, Perl and PHP want to be used by normal people. Those languages evolved in ways that draw in new users. But Rust? It has evolved to become very difficult and awkward to use, especially for new, average users.

    From what I can see, the entire Rust ecosystem exhibits the traits that have come to be associated with Asperger Syndrome, or autism in general. Rust has a certain natural awkwardness to it; a inherent difference from every other programming language and programming language community that exists. It's like it wants to fit in, yet no matter how hard it tries it just can't. It's like, in my opinion, the entire Rust ecosystem lacks a natural understanding or ease of existence that other programming language ecosystems develop naturally.

    I am just speculating here, as I do not know any of the Rust developers on any personal level, but could it be that mild/moderate autism or some degree of Asperger Syndrome has influenced how the Rust programming language has developed? If the developers of a programming language exhibit autism or Asperger Syndrome, could they in turn pass this on, so to speak, to a programming language and a related community that they have created? Could Rust be an example of, for lack of a better term, Autism-Driven Development?

  13. Rust fans remiond me of Rush fans... by VAXcat · · Score: 3, Insightful

    They're really enthusiastic, mention that they think it's great at every opportunity, and can't understand when someone is underwhelmed by the object of their admiration....

    --
    There is no God, and Dirac is his prophet.
    1. Re:Rust fans remiond me of Rush fans... by MichaelSmith · · Score: 1

      It looks like C with a few nasty bits taken out. Not enough of a step forwards to be justified IMHO.

  14. Re:How Rust Can Soothe Your Autistic Shitbrain by boa · · Score: 1

    +1 for making me laugh :) Satire at its best

  15. what's the point? by doctorvo · · Score: 1

    Most C libraries in Python exist in order to interface with existing APIs, also written in C. Adding Rust to the mix merely complicates things without any significant improvement in runtime safety.

  16. GTFO Rust by FutureDomain · · Score: 2

    Rust can go and, well, rust. If you want to get safer C, than add Cyclone support to gcc and use that. No rewrites, no learning a new language, no hitching your project to a SJW converged organization that is slowly dying, no fanboys who pathetically spam puff pieces on Slashdot... Seriously, Cyclone or any of the other safe-C alternatives are better and less intrusive than a Rust rewrite.

    --
    Hydraulic pizza oven!! Guided missile! Herring sandwich! Styrofoam! Jayne Mansfield! Aluminum siding! Borax!
    1. Re:GTFO Rust by serviscope_minor · · Score: 1

      Rust can go and, well, rust. If you want to get safer C, than add Cyclone support to gcc and use that.

      Why bother? Rust and C++ are much more powerful alternatives to C with similar machine models. Why on earth would I want to use a language where everything has to be micromanaged by hand.

      no learning a new language,

      Oh the horror!

      --
      SJW n. One who posts facts.
  17. Re:By now the propaganda alone is reason to stay a by boa · · Score: 1

    Jeez.

    I wonder what would happen if brilliant and smooth-talking developers like Linus Torvalds or Theo de Raadt joined the rust community.

  18. Julia! by Anonymous Coward · · Score: 2, Interesting

    I make money doing embedded C. If I am going to replace C with something else it will be Julia. I get the speed of C, the coding efficiency of Python and real support for computational algorithms.

  19. that Rustfags to you, by Rujiel · · Score: 1

    fuckface.

  20. Why replace C with Rust and not C++? by angel'o'sphere · · Score: 1

    Well,
    C++ might be a bit ugly when it comes to templates, but for that you have typedef.
    Nothing against Rust, it looks like a decent enough language (exept for the name, looks like the inventors like to repeat the subvers-ive/ion failure).

    Anyway: why would one replace C with Rust instead of C++ is beyond me.

    If you write new code, then I would probably agree, but for existing old code I see no justification.

    I wonder if there is a Rust to JVM compiler ... googeling a bit ...

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  21. Re:By now the propaganda alone is reason to stay a by angel'o'sphere · · Score: 1

    Why do you call the once a year mentioning of Rust a Hype?
    Typical american?
    You know something, which most people don't know, you get news about it "again" and then you call it a hype?
    I would assume that 90% or more "developers" or "programmers" never ever have heard about Rust.
    I only know Rust because it is occasionally mentioned on /.

    This "hype scare" is a quite strange thing for us europeans.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  22. Re:Give up by serviscope_minor · · Score: 2

    When people whine about how the stories aren't techy enough, thye get modded up. But apparently people who whine when stories realy are only for nerds (along with some gratuitous homophobic slurs) also get modded up.

    Seems like some people will never be happy.

    --
    SJW n. One who posts facts.
  23. Re:I'll never use anything from Mozilla. by DontBeAMoran · · Score: 1

    Opera is still around but AFAIK was bought by some Chinese company.

    So your only option seems to be a Mac.

    --
    #DeleteFacebook
  24. Re:I'll never use anything from Mozilla. by angel'o'sphere · · Score: 2

    Since 5 years or so Firefox is autoupdating (you can not disable it) and causing problems over problems (failed updates etc. or UI changes). Why Mozzial.org thinks removing the menu bar and having a "hamburger menu" instead is a good thing is beyond me. Most people tried to revert but could not, then they deleted FF and went to other browsers.

    None of my friends is using FF anymore. I only use it when a software project demands FF compatibility and we have to use it for tests. Or for fancy GreeseMonkey scripts.

    I think I have no FF anymore n my Mac since 7 or 8 years ... and as long as they don't revert to a sane browser with a menu bar and no automatic forced update I won't try it again.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  25. Re:I'll never use anything from Mozilla. by Hognoxious · · Score: 1

    I use Firefox ESR with a classic theme. Hot seen any changes to it for years.

    You're not very observant, then. Percentage zoom indicator. What's that there for? There are two zoom sizes I care about - too big and too small, and it takes up a lot of space on a small screen. Refresh, reader view (whatever that is) & back button all tied to the URL when they used to placeable wherever you like. Fitt's law, you cunts.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  26. Rust by c++horde · · Score: 1

    If Rust is going to replace C on any project, I'm not going to work on the project, nor will I invest money in that project.

  27. Re:Give up by garlicbread2 · · Score: 1

    Here's a better idea, why not try D / DLang instead?
    https://dlang.org/
    Any valid C or C++ can be used with D

    Rust could potentially replace C, but not C++
    It's important to note that Rust does not have Object Orientation, it's more of a pragmatically functional language
    It separates data storage and functions into separate grouped objects
    but lacks features such as inheritance.

    D has inbuilt garbage collection, which can be disabled but is on by default
    I think one of the issues in the past has been the disabling of garbage collection with it's standard library, since it assumes garbage collection is enabled for that part.
    Although I heard they were working on fixing that, I'm not sure how far they got with it so far

  28. This is What Happens When Developers Make Business by brian.stinar · · Score: 3, Informative

    This is what happens when developers make business decisions. Seriously, why is Mozilla focused on promoting/using/developing Rust, when they could be focused on making their browser suck less? Probably because they have no business concerns, at all, about making a viable product (or company.) I spent two weeks exclusively using Firefox, right when Google was found to be recording everything I said, in the event I happened to say "OK Google" without a way to turn this off. After two weeks, I realized I'd rather be bugged than use Firefox any longer.

    This is exactly what Joel Spolsky wrote about, when Netscape did a complete rewrite here, or in his awesome book Joel on Software . Netscape focused on a rewrite, instead of making their browser suck less.

    It sounds like Netscape made this mistake and then became Firefox. Now, it seems like Firefox is making the exact same mistake. This has to be the funniest business case study ever.

  29. Get lost and go away by Anonymous Coward · · Score: 1

    There is nothing wrong with the older languages. The problem is in the newer 'programmers' (and I use that term lightly)

  30. Re:This is What Happens When Developers Make Busin by Zan+Lynx · · Score: 1

    By replacing small pieces of Firefox with new pieces that use Rust, they are avoiding the Netscape problem. They aren't rewriting the whole thing. But one day the whole browser will be Rust, replaced a piece at a time.

    You don't think Microsoft Edge still uses pieces of Spyglass or Mosaic do you? And yet, at no point did they rewrite the whole thing.

  31. Re:Give up by Kjella · · Score: 1

    Even in a modestly large group somebody will always be unhappy, but since opinions are like assholes meaning everybody's got one I'll share mine - the opinion that is, the rest I leave for the goatse.cx guy. The articles here have always sucked donkey balls, they're an untimely mess from an odd selection of subjects and done better by many other sites. The value has always been the discussion, which means the valuable articles have been those who create an interesting discussion. Sometimes there's been very nerdy articles that just doesn't leave much to discuss. Other times it's been soap opera drama that - if you take one step back - is like who gives a shit.

    The best articles IMHO are those about some sort of tech/sci advance that sets off a discussion about the subject/implications. Like, SpaceX can land a rocket but I can read that in a thousand places. What will that mean for the future of space travel? That's what is interesting to discuss. Probably second most interesting are the legal subjects, usually because we have a good understanding of the practical feasibility or consequences of implementing the law. Or sometimes how the absence of law lets technology accumulate information and erode their privacy. Of course that could get very narrow and repetitive, like the 1000th time refueling the BSD vs GPL flame war.

    I remember us talking about Bush in 2001, so there's politics, so Trump is not new to the mix. There was point releases of the Linux kernel, though of course they usually turned into YotLD discussions. I remember /.'s best headline as "Lance Bass to Continue to Plague Earth's Surface" which ultimately is about a boy band artist's ego trip and not really "news for nerds" at all. It was always kinda CmdrTaco's random blog with comments, it's hard to pin it down. But it was mostly nerdy things that even if they weren't your kind of nerd it felt like they could have been. If anything I'd say it lost that randomness and got too driven by certain submitters' repetitive agendas, like this is the 10th Bitcoin or SJW propaganda this week. Shit got old, discussions were rehashed, many people left.

    --
    Live today, because you never know what tomorrow brings
  32. Re:Give up by rtb61 · · Score: 1

    Why not come up with a coding dictionary first. Agree on the words, write/print, var make let, and the list goes on. Agree on the fucking words to be used at least before arguing over their arrangements. Agree on which symbols do what. Come up with reasons for any choices. We are going to keep churning languages driven by nothing but the greed of people pushing specific languages, reality is coders seem to be nothing more than a bunch of purposefully argumentative fuckups who do not want to agree on anything with other coders, argue to win with no purpose or valid reason other than winning the argument.

    --
    Chaos - everything, everywhere, everywhen
  33. Re:I'll never use anything from Mozilla. by LoneTech · · Score: 1

    Your very first claim is false: in Preferences - Advanced - Firefox updates, you can easily set it to ask or never check.

    The menu bar can be accessed by hitting Alt, and it can be unhidden by going Hamburger - Customize - Show/Hide Toolbars - Menu Bar. While hiding it is arguable it provides more space for content. The weird thing is the amount of blank space left behind.

    How many did you poll to conclude "most people"? I'd be surprised if it was a whole dozen... and the "none of my friends" part makes me wonder how many just won't broach the subject, if you fly off the handle like this at the mention of it.

    One of my reasons to use Firefox is that it at supports ad blocking on Android.

  34. Re: By now the propaganda alone is reason to stay by gweihir · · Score: 1

    I think 1984 called that "doublethink". The ability to do it is an absolute requirement for any self-respecting fanatic!

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  35. Re:By now the propaganda alone is reason to stay a by gweihir · · Score: 1

    Fail and fail and fail again. You have any effective intelligence? Seems not so.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  36. Re:By now the propaganda alone is reason to stay a by angel'o'sphere · · Score: 1

    Yes fail :D
    As I fail to see a hype.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  37. Re:I'll never use anything from Mozilla. by angel'o'sphere · · Score: 1

    Your very first claim is false: in Preferences - Advanced - Firefox updates, you can easily set it to ask or never check.

    I stopped using FF when they _removed_ that option.

    No idea if they reintroduced it.

    One of my reasons to use Firefox is that it at supports ad blocking on Android.
    Ah, I have a new Android device, I could try FF on it for that reason, thanx for the info.

    I know that you can activate the menu ... but as I said: I don't use FF anymore. Only if I have to do a manual test in an obscure software project.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  38. Re:Give up by sellibitze · · Score: 1

    but [Rust] lacks features such as inheritance.

    You overrate inheritance. Even in C++ the trend is to favour composition over inheritance. One good reason to use inheritance in C++ is to create something similar to what Java calls an "interface": basically an abstract base class which you can derive from using one or more concrete classes to do dynamic dispatch. In Rust you can get the same thing via traits -- no inheritance necessary for that.

    I'm not saying inheritance is never useful. But in Rust you can get by pretty well without it because of composition and traits. That being said, The Rust community is open for suggestions for language extensions. If you feel something is missing, start a discussion and/or write an RFC for it.

  39. Re:This is What Happens When Developers Make Busin by terjeber · · Score: 1

    You don't think Microsoft Edge still uses pieces of Spyglass or Mosaic do you? And yet, at no point did they rewrite the whole thing.

    As far as I know this is exactly wrong. Edge was written from scratch, it was not a re-write of IE at all.

  40. Re:By now the propaganda alone is reason to stay a by gweihir · · Score: 1

    Indeed. But true believers (that, by definition, ignore all evidence of any shortcomings of their chosen faith) will be unable to see their faith as "hype". This is quite normal and a sure way to identify what is going on with them.

    @angel'o'sphere: You will never hire my as CTO, because I am not available to you. You do not have what it takes to impress me enough. My current CEO does.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  41. "Knowing" Rust without paying attention. by sellibitze · · Score: 1

    Obviously, Rust, with it's run time checks, can't match the performance of C without those checks.

    I get that it's tempting to brush off backing up your claim with the word "obviously" especially if the claim sounds so reasonable. But you're actually wrong here. I encourage you to look into the details. Most of the checks are done by the compiler at compile-time incurring no runtime cost. And with respect to array bounds checking ... depending on what you do these checks can often be elided. What do I mean by that? I don't mean "opting out at your own risk"—though, that's possible, too—I mean that there are patterns that make bounds checking just unnecessary in a lot of cases. The Rust team would consider it a bug if a simple C for-loop iterating over an array would be faster than the equivalent idiomatic Rust code. With the help of Rust's zero-cost iterator abstraction and enabled compiler optimizations you'll get exactly the same machine code for the loop logic. People actually checked this because they care about performance.

    I see no compelling reason to switch to Rust.

    Well, with your attitude and preconceived notions, it doesn't surprize me. You don't really know what Rust has to offer.

    If having those run time checks "built in" is desirable enough, I think it would make more sense to re-introduce those checks to C compilers, (Yes, I know, Rust has other features "built in", but most, if not all, of those features are available in libraries with many years of use and testing. (They might even be used by Rust.))

    The magic is in Rust's type system. That's how it's possible to avoid dangling pointers without incurring any runtime costs or adding a garbage collector. Show me that C library that does it for C. Sheesh! Array bounds safety is probably the most boring thing about Rust. Everybody can have array bounds safety easily.

    1. Re:"Knowing" Rust without paying attention. by UnderCoverPenguin · · Score: 1

      The magic is in Rust's type system.

      While type constraints and iterator abstraction can avoid the need for run time checks of loops, there is still the case of calculated indexing. A tool like
      Polyspace might

      be able to determine if the calculation result will be within bounds. Mathworks would be extremely interested in hiring anyone who could independently develop similar analysis capability.

      Likewise for avoiding dangling pointers and null dereferencing.

      If the Rust compiler really has the same kind of source code analysis capabilities as Polyspace, I would think that even the most miserly of employers would be paying $$$ to send their software developers to "Rust Academy".

      --
      Don't try to out wierd me, three-eyes. I get stranger things than you, free with my breakfast cereal. --Zaphod Beeblebr
  42. Re:This is What Happens When Developers Make Busin by Zan+Lynx · · Score: 1

    And as far as I know, Edge was not a rewrite, it was IE with everything old and legacy ripped out.

  43. Re:This is What Happens When Developers Make Busin by terjeber · · Score: 1

    And as far as I know, Edge was not a rewrite, it was IE with everything old and legacy ripped out

    Let's see... the UI is new, re-written from scratch. The HTML parsing and formatting is new, written from scratch. The Javascript engine is new, written from scratch. What is left?

    Or, in short, if you rip everything out, isn't that a re-write per definition?

  44. Re:This is What Happens When Developers Make Busin by Zan+Lynx · · Score: 1

    I can't convince anyone without a copy of Microsoft's Edge revision control. So I guess think whatever you like.

    But if they didn't create a new revision history, then yes it is the same browser. Firefox is still Firefox even though there's nothing left of the original. Linux is still Linux. I think there was an old bit of TTY code and some floppy driver code in the latest Linux left from 1993, but all the rest of it changed, and it's still the same thing.