3

OMF you motherfucking Eclipse developers. All I want is to build an application with SWT. WHY THE FUCKING FUCK is that near impossible.
1) why are there no SWT maven artifacts= only 3 year old ones on a custom github repo?
2) why is is fucking rocket science to even find a guide on how to build this fucking piece of shit yourself
3) WHY THE FRIGGIN FUCKING FUCK OF FUCKS is it so hard to build it your self - outdated docs .... nice, dead links and repos, nicer .... referenced maven artifacts from a non-existing, none-documented repo, ... wow you're really kickin it here.

All I want is to fix this nullpointer in this fucking piece of shit you call framework ...
Have you actually tried to read your docs (can we really call that shit docs?) from a none-100years-swt dev's point of view?
Noone understands shit!

Why is there no standard build system, like maven, grade or for fuck's sake even ant?
It almost feels if you devs don't want anyone use your abomination, so it can die in peace.

Arg, I could puke ...

Comments
  • 0
    1) probably because its deprecated, but i found 2017 ones in mvn
    2) see above
    3) again, why the hell would you ever use, much less, build swt in 2019?
  • 0
    Finally a good, proper rant.

    Now, why the fuck would you use SWT in 2019?
  • 0
    I want to use the eclipse infrastructure (midtly cide editir, autocomplete, integration into the compiler etc)
  • 0
    @mojo2012 even in 2019 when things like VSCode are available?
  • 0
    @unsignedint vscode for java is not yet ready for primetime. It lacks a lot of features! Maybe in two or three years or so ...
Add Comment