I took a quick peek at Vineflower first, and it's a fork of Fernflower. So would recommend that for anyone who might stumble on this in the future who is looking for a decompiler.
222 karma · joined December 5, 2010
I took a quick peek at Vineflower first, and it's a fork of Fernflower. So would recommend that for anyone who might stumble on this in the future who is looking for a decompiler.
A lot of tech and tech-adjacent writing is like that these days. Our cool project X now does Y! With no introduction about what X is, or even a link to something that describes it. So most readers are left to wonder about why should care. At times, I've even tracked down X's github repo only to find that their README has the same problem.
It's an easy trap to fall in when you write. It's easy to feel like you're over-explaining things. You, the author, know what it is, and likely many of the people who follow X know too. The problem comes when some curious person outside of the Xosphere takes a look. Chances are good you'll lose most, if not all, of them.
If you want people to be interested in your X, then make sure they have a way of learning about your X when you introduce improvement Y.
That and ability to zoom in/out or increase/decrease font size.
It's definitely a strong statement, and thanks for the qualification.
When I saw the words on the page I began to wonder about all the other things that could go wrong. e.g. There could be bug in software that does the code analysis, or the compiler, or underlying libraries or operating system, or (sigh) in the CPU.
Also, there could be unexpected behavior when the machine its running on is under load. It would also be interesting to see it subjected to some of the fuzz-testing software out there.
Overall, I think it's a great approach and worth pursuing. Thank you for releasing the source.
Hopefully, it's a good enough of a hook to get you started on AWS that it is worth it to keep it cheap like it is now.