Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT feedback from students this semester


I received a few more replies.

One pattern that seem to emerge is that users sometimes don't go through the effort of setting up Eclipse CDT for their first/second assignment as they are not that hard. However the third assignment was pretty tough and large and that's when a whole bunch of students decided to setup Eclipse CDT.

One student was quite eclipse-savvy. He found out about the Remote Systems Explorer (on his own):
What he did was to setup Eclipse on his personal laptop and use Remote Systems Explorer to develop/build/run on the university computers via ssh connection. Coming to think of it, this is what I did in my last year of university for some assignments as well. It doesn't have the full indexing support of local files but is good for basic editing/hacking.

I think so far almost everyone complained that the debug perspective felt clunky but had all the functionality that they needed.

On Thu, Dec 15, 2016 at 4:31 PM, Leo Ufimtsev <lufimtse@xxxxxxxxxx> wrote:

As per request in CDT discussion:

I've had some feedback from students who used Eclipse CDT this semester.

Here is a compiled summary based on around 10 replies that I got back from survey. (Class of 150 students).

- A 2nd year university (University of Toronto, Canada) course on System programming in C.
- Eclipse CDT was used as their main IDE this semester (for the first time).
- I held a guest lecture on how to setup and use Eclipse CDT at the beginning of the semester and helped some students get going with it.
  Lecture slides:
- Eclipse was used for 3 C based assignments.
- I had University IT staff pre-install the Eclipse CDT spin on university computers. (Ubuntu 14.04)
- Some students had familiarity with Eclipse JDT.

Please note: Student's often complain that applications are too complicated because they have very limited time to learn a tool.
This doesn't necessarily reflect the difficulty of learning Eclipse in the industry.

- 7/10 used Eclipse.
   - One used CLion. The reason was that he learned to use Intellij a year ago and didn't feel like migrating to Eclipse because he didn't knew it very well.
   - Two used only a text editor (Atom).
   - Those who used Eclipse CDT would occasionally use text editors (eg Atom) for simple little hacks like editing makefiles.
   - It was rare for students to do all their work in Eclipse (although possible). Many resorted to terminal for SVN, compiling or other external tools as it was too complex for them to figure out how to do it in Eclipse. (Although info provided in the slides).

- Dark theme was not functioning that well (for older Eclipse Neon release). (This is not CDT specific, but CDT users liked to use Dark theme).
- Debug perspective feels cluttered. Too many windows and each one is too small. (Even on 1900x screens). (Not CDT specific, but debugging was used with CDT).
- Valgrind was hard to install for them. Some didn't see what functionality the visual valgrind had that the command line version didn't. (But Valgrind extensively).

Most commonly used features:
- Visual debugging  (Main reason people setup Eclipse).
- Code navigation
- Keyword highlighting
- Refactoring (variable name/function names), Autocomplete.
- Version Control / Local history.

Also mentioned:
- Students wanted to have a Terminal build into Eclipse.
  - They were not aware of TM Terminal's existence (which provides this functionality).
- Students wished for a 'simplified' version of Eclipse. Something similar to PyCharm's "Edu" version which would have a limited set of features just enough for learning a new programming language.

Leo Ufimtsev
Software Engineer, Eclipse team.
Toronto, Canada

Red Hat, Inc.

Leo Ufimtsev
Software Engineer, Eclipse team.
Toronto, Canada

Red Hat, Inc.
Leonidas@xxxxxxxxxx |

Back to the top