Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 days ago.
Improve this question
Why is the Rust programming language called "Rust"?
Is there anything known about who named it, and why? (I am having a hard time coming up with a positive association).
There is a thread on reddit that claims the answer.
TL;DR: Rust is named after a fungus that is robust, distributed, and parallel.
It is also a subsequence of "robust".
Found another interesting quote:
Also, calling Rust a research language is funny to me because -- as its name reflects -- we've tried hard to avoid incorporating new technology into it. We haven't always succeeded at failing to be novel, but we have a rule of thumb of not including any ideas in the language that are new as of the past ten years of programming language research. The field of programming language is full of old technology that hasn't been put to use in solving problems that it's exactly suited for. The goals with Rust were to avoid reinventing wheels, and see what the past had to teach us. I can't blame anyone for thinking Rust is a research language, though, since it is being developed by Mozilla Research.
So this alludes to "exclusively relying on old technology and shunning the new".
Again, I get the "old" implication of "rust", but still cannot get over the "will eventually corrode to junk metal" association.
It's by analogy to web browser architecture. The user-interface parts of mozilla are often called "chrome", because they're supposed to be shiny (this was the case even before the chrome browser came along). And in Firefox, a lot of chrome code is implemented in javascript.
Rust, on the other hand, is intended for implementing the guts of the browser; the non-chrome parts. The name makes me think of big metal gears meshing together deep in the bowels of some giant machine.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 13 days ago.
Improve this question
My Objective
I am trying to do Natural Language Processing(NLU to be precise) with spaCy. But the more I dive into this wonderful library, the more I realize that I need to understand some linguistics first.
The Problem
The problem is, spacy explains NLP with terminologies that just don't seem to follow a single branch of linguistics. I am new to NLP and if anyone can give me some pointers on how to study linguistics for Natural Language Understanding, I think I would have an easier time getting a grasp of this library.
I have tried understanding Morphology but stuff like Part of Speech tagging, syntactic dependencies, etc. all seem to relate to different concepts that are implemented together. How much theory and in which subfields of linguistics do I need to study to have a strong grasp of all the concepts used?
I want to learn the theory so I know what to do even if spacy is missing something that I might wanna use.
I would read an overview like this one Introduction to Linguistics for Natural Language Processing and then would dive deeper into the topics that interest you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I am new to programming and I try to research as much as possible in this field. And once I came across to this expression: "Extreme and pair programming". Pair programming is an easy term, and I found quite clear documentation about this. But extreme programming... I found some articles about it, but explanation wasn't so well. All I understood that extreme programming is an Agile development framework. But why I must use that, what is difference between this and another types of programming styles?
Can anyone explain me what is extreme programming language very clearly?
Extreme programming (often called XP) is an agile framework that was developed by Kent Beck in the 1990's.
There aren't too many people that use the whole XP framework these days, but a lot of the engineering practices it popularised are very common.
Examples include:
Pair programming
Test driven development
Continuous integration
Frequent releases
Constant refactoring
XP favours an approach of writing the minimum amount of code to solve the problem at hand. Things like optimisation and forward planning are generally a low priority. This is the 'extreme' part of extreme programming.
The idea is that you write code to solve the current requirement. If you then find you need the code to be faster, or scaleable, etc. then you refactor it.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What factors are important? How do you know if a given programming language is "simple" or "simpler" than another language?
I'm not sure if this is a fair question to ask, since different languages serve different purposes and it might not really be comparing apples to apples.
However, with that said, memory management would come to mind. One can argue that Java is a "simpler" language than C++, since it has a garbage collector that can deal with some of the complexities around memory management, instead of forcing you to do it yourself.
In my perspective, these are the points that define the complexity of a language.
Variation of syntax from common pseudocode and constructs
Ease of developing a structure for real-life entities like objects
Methods of structure enforcement at compile time.
Memory management strategy allocation/deallocation
Code reusability
Ease of code headers and directives management
Inbuilt libraries
Relative installation package sizes
Data exchange capabilities like over network of files
Process handling like thread management
Relative brevity of the code
Speed of compilation
Developer community size and documentation
OpenSource implementations
Platform dependence
And many more could be added to this list.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I would to know the software which can view code of Microsoft word software and any other software code. So that I can learn from that software code and how they used in there.
(sound's like illegal but really it is helpful for the programmer)
any Ideas
What you're describing is called a disassembler or decompiler. It is rarely useful for what you want it for, because the intent of the programmer expressed in variable, method, and class names - is mostly lost. This is somewhat less true for modern bytecode languages like Java and C#.
You ask for a decompiler. Please note decompiling is illegal in many juridictions. Also once you decompile you usually get very hard to read assembly code learning from which is problematic unless you have plenty of experience and know exactly what you're looking for.
You need to get a decompiler for viewing the code of dll and exe files based on the language its coded in.
example:
Delphi Dll Decompiler
search for an appropriate decompiler te get the code back.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
After reading E-myth Revisited, I realize that I can do a better job at making my company less reliant upon me... I spend a tremendous amount of time answering silly questions (silly to me, but necessary for my developers to get the job done).
I need to write a set of operating manuals for what to do in certain situations...
For instance:
How to make a build
How to write test cases
How to report status
How to fix a bug
How to handle support question A, B, C, etc...
What to do when you are stalled
What to do when the power goes out (really, I need to do this)
etc...
What are some useful, generic operating manuals that you can think of, for a software development company?And please, if you have some good, short, online versions that you know of, please post them. I would much rather use a starter manual and modify it for my needs, than start from scratch.
What about a wiki - at least then other people can start to contribute.
Otherwise they are just going to rely on you for the manuals
I disagree with the wiki. As the owner of the company -- it is your responsibility to write the manuals, or delegate it in a very controlled fashion. People should rely on you for the manuals.
Really though, back to the question. The obvious standards, coding, SQL, etc for your platform and programming languages. You'll be able to find examples of these anywhere on the internet. As for customer support, you should probably write that yourself, you know how you want your customers treated. As for test cases, again, you'd have expect your developers or testers to have a professional understanding of what needs to be done, you might indicate the acceptable minimums however.
What to do when you are stalled. That's what managers are for :-)
I think it boils down to writing the manuals that are unique to your business, and trying to steal or borrow manuals for the generic processes.