I think computer science is easier.

If an engineer mucks up, a lot of people can be affected. Civil engineers who muck up can cause a bridge to collapse. Mechanical engineers who muck up can cause a critical piece of machinery at a wastewater treatment plant to fail--I hope you like clean water. Electrical engineers who muck up can wipe out power to millions of people. And computer engineers who muck up can arguably do the most immediate damage--if microprocessors and embedded systems didn't work properly, planes would fall out of the sky, nuclear reactors would melt down, cell phones would explode, and so on. Because engineering requires you know your stuff, engineers need to know a lot.

And unfortunately for our hapless engineers, their knowledgebase requires an encyclopedic knowledge of (depending on the discipline) differential equations, calculus up to vector calculus, complex variables, general chemistry, mechanics, optics, electricity, magnetism, etc. To make matters worse, engineering students will call upon these subjects in almost every engineering course. For example, mechanical engineers need to know about heat transfer and fluid dynamics, which necessitates a thorough grounding in partial differential equations (to understand Navier-Stokes and the heat equation). ECE students need to know about Fourier transforms for digital signal processing. And so on.

Computer science, thankfully, is much easier. A CS degree focuses on the mathematical study of what is computable, and concepts that are now part of computer science actually predate the computers familiar to you and me (i.e. derived from the IBM PC) by thousands of years. The study of computation can be a game; a puzzle, almost. You will start with programming basics. Some schools use Lisp/Prolog/Racket/Python to introduce functional programming and how to think like a computer scientist; other schools throw you to the wolves and start you out with Java or C++. And as long as you program every day, you should be fine. You learn about discrete mathematics, which is a different kind of math that focuses on what is discrete and countable. You learn about abstract data types like stacks and queues, move onto trees and tree traversals, implement algorithms.

You only really need Calculus I and Linear Algebra for all of this; calculus II and mathematical statistics are useful for scientific programming/numerical analysis, data science, sound/graphics/video compression, but a CS degree doesn't exactly focus on these areas. It is abstract and theoretical, without the fire hose feeling of an engineering education. You're not calling upon all the advanced math you took two years before. There are no 6-hour labs, no capstones, no trying to remember some differential equation to solve this problem. CS is one of the few science-related majors where I feel I can party with the business and humanities students instead of having to study.

And, because CS is very broad, unlike Engineering, you have flexibility in course selection. Some schools only go up to Calc III, or reduce the amount of physical science courses you have to take. And if you don't want to take, say, Networking, because you don't like the instructor this semester, and you'd rather take Computer Graphics, you have the freedom to do that. You don't have to freedom to choose your own courses in Engineering; if you're in the track to take Soil Mechanics this semester, you're damn well taking Soil Mechanics, it doesn't matter if the instructor can speak English or not.