There's, like, one per month on NH.
233 karma · joined April 8, 2009
There's, like, one per month on NH.
"trendy" is something new that exceptional people to, contrary to what everybody does. "trendy for average" is wtf.
If it really works (didn't check) then IDEA would be fine. Still I'd prefer these modes to be merged.
I'm not asking for a visual merge "when there are conflicts". I'm asking for a visual merge NOW; because I said so. Because if it fails to produce the said visual merge, it gets thrown off the window - exactly what's happened.
And it's more than visual merge; I also want a tree of files that have been changed, on both sides; and I want to look at diffs when clicking on them; and to choose what to update, what to commit. It's very much more than just a dumb commit all/update.
Nope, those people on ##java are really passionate about IDEA.
And that now C# is trendy for the same developer.
Anyway, "trendy for average" is oxymoron.
I want to see which changes are due, and which changes are to be imported. Like one does in eclipse under Team -> Synchronize with repository.
I fail to find such a mode in IDEA.
Noone is yet to point me to it.
However, I had my cow orker try it another day, and we've failed to find a way to visually synchronize project with repository, like you do in Eclipse. Therefore, threw it out.
If someone isn't judging languages by name and have broad sight, he would recognize that C# falls into entirely different bucket (bytecode virtual machine, mandatory garbage collection, managed execution, inseparable class library) than any of C, D, C++, ObjC, ooc.
Yeah, I've wrote one in Java, internally, too. But why announce it without code examples, feature lists and praises about issues with ORMs it would fix?
It turned out that I've spent more time making Hibernate do whatever I need without failing than doing everyting else. It followed the principle of most surprise: I could never guess what'd it go given a code snippet, provided all the complex machinery involved under the hood.
Now I fear ORMs. Wrote my own for that project, it's primitive but does its stuff and is completely predictable.
It's obviously designed by Unix orthdoxes and it shows
No dynamic linking! No threads! Not much of mem alloc, either!
Also I think there's more than basic physics, it was the whole series.
Your program is code, your proof is code, both are going to be buggy.
And what are you going to prove?
" menu for encoding
set wildmenu
set wcm=<Tab>
set ts=4
menu Encoding.koi8-r :e ++enc=koi8-r<CR>
menu Encoding.windows-1251 :e ++enc=cp1251<CR>
menu Encoding.utf-8 :e ++enc=utf-8 <CR>
map <F8> :emenu Encoding.<TAB>It's a thrown together mess.
But I'm afraid they want something different.
This year it failed for some reason, tho.
They also did that at MAKS this year.
XSLT does describe control flow pretty explicitly; most functional languages I know, too. In other hand, languages like Java allow the VM to shuffle their control flow considerably.
I vote for dropping "declarative". Call query languages query languages, functional functional.
XSLT is functional!
XSLT/XPath can also be statically typed: XSLT compilers happily infer types of all expressions in their XPath.