2 ms·
> The first case it was obvious no one tested installing SubEclipse on a fresh install. That sort of thing is embarrassing. You just know some junior dev thoug
by the_af 9y ago
> The first case it was obvious no one tested installing SubEclipse on a fresh install.
That sort of thing is embarrassing. You just know some junior dev thought "well, it worked on my computer!". I don't mind when an experimental new feature doesn't work, or when some obscure corner case is broken; shit happens. But when the main, "happy" path for a major plugin doesn't work, the project is in serious trouble and you know it's time to consider jumping ship.