1,323 karma · joined April 30, 2014
Would back/forward buttons continue to work if we decided not use browser history APIs?
Well in that case, it had the exact opposite of the intended effect on me.
You can set a breakpoint on your normal method and you can see if any proxy object was introduced by the annotation in the call stack and set a breakpoint there. You can also just see the usages of the annotation to see where and how it is being used and set a breakpoint there.
Anyway, going back to my original question, similar criticism is equally valid when you do metaprogramming in lisp/python/ruby. Why are these concerns only raised in the context of Java?
When you are using shared libaries, it is fairly trivial to hook into the library calls and replace them with whatever you want. When you are using static libraries, the linker and optimizer could for example inline the machine code directly in the application code. What tools do you have to do similar tricks with statically compiled binaries?
I don't quite get the criticism against annotations. Metaprogramming and code as data seem to get a lot of love in the context of lisp, python or ruby, but a lot of hate when it happens to be done in Java. I absolutely love the powers that reflection, annotations etc give me.
The difficulty of analyzing dependency injection and "magic happens here" is overstated. Just run the code in the debugger. And if you are having problems with the auto-configuration stuff, you can always selectively disable it and explicitly define the beans you need.
https://docs.github.com/en/actions/publishing-packages/publi...
The steps are roughly: 1. Configure the repository you want to push to. 2. Set up your account with the repository. 3. Configure your credentials. 4. Deploy.
There is not a single modern tool that beats Emacs in ease of customizability and extension.
I am guessing you took offense at the "an actual complexity theorist" part of my comment, but it wasn't a personal remark against you. The general audience of hackernews is programmers and startup enthusiasts.
>I'm more than qualified enough to understand and present well-known complexity results from half a century ago, even when a misguided appeal to authority is at play.
All the more reason you should not be so insecure and automatically assume the worst about other people's intentions. *
* This time the snark is intentional.
>The following does not quite show it can't happen but it does give one pause: an old result of Levin's shows that there is a program you could write NOW such that if P=NP then this program decides SAT except for a finite number of formulas (all of which are NOT in SAT) and can be proven to work in poly time (I will later give three pointers to proofs). The finite number of formulas is why the people above may still be right. But only a finite number- seems like a weak kind of nonconstructive.
So, based on this post, it is actually not known that P=NP implies existence of polynomial time algorithm for deciding SAT. The universal search idea only yields a polynomial time algorithm that decides SAT for all but a finite number of formulas.
Urban India is a very low trust environment, but people still have access to things like home loans, insurance and capital markets (equity and loans).
> lack of good governance (bad or non-existant laws, corruption etc)
I agree that good governance is a necessity for development of financial markets, but not sure what it has to do with being a high trust or low trust society.
Visit a part of the world where most people do not have access to home loans, health insurance etc. and you will not have to ask how mere redistribution of risk and capital adds to productivity ever again. (I happen to have been born one such part of the world.)
What an utterly useless thing to get pedantic about.
It's the exact same way Indians mispronounce many English words when they map it to some equivalent native sounds.
If you think that, your ear is simply not hearing the difference because the sound does not exist in your language.
The Wiktionary is in fact listing two different pronunciations of the word. The one mentioned under South Asia is the correct one.