461–470 of 680 posts
Earlier quoted context omitted.
There's also Fork: https://git-fork.com/
I'm really curious - why do people want a graphical git client? The command line exposes everything, and the model is simple and intuitive. I work in a very large monorepo, so it's not like I'm working in a git tree that isn't complicated.
Earlier quoted context omitted.
There's also Fork: https://git-fork.com/
I'm really curious - why do people want a graphical git client? The command line exposes everything, and the model is simple and intuitive. I work in a very large monorepo, so it's not like I'm working in a git tree that isn't complicated.
I nearly spat out my drink. Git is many things but those aren't the first two words that would leap into my head.
Earlier quoted context omitted.
> I'd also encourage you to consider separating your concerns about the Russian government and individuals living in Russia, just as you might other governments and their citizenry. That's a big ask, because the Russian government's relationship with its citizenry is very different from the relationship of a free country's government with its citizens. Namely, I am confident that there is substantially zero risk that…
> And we know that the head of that country is at best a violent and evil man, and so is an entity to be feared by those whose interests are misaligned with his. I’m not quite sure which country you were talking about? While I agree with your general point, it just occurred to me that that could be applied to both leaders. It’s the country and the structure of that country that is different (e.g. leaders will change,…
The single most feature I hate about their products is their reliance on JVM, which makes them memory hungry and slow on older machines. :)
I doubt this is even remotely true. The JVM (and the CLR, and every modern runtime) is a very well-tuned machine that performs well.
Language services make heavy use of system resources. It's effectively compiling your code as a service whenever you need it, which is a lot.
Earlier quoted context omitted.
In addition to what michaf mentioned, what we have now is not what they originally proposed. https://blog.jetbrains.com/blog/2015/09/18/final-update-on-t... - the perpetual license fallback did not exist under the original proposals and only happened due to backlash.
Why does this matter? Yes, their original plan was pure SaaS. But they listened to criticism and changed it once they realized that there was backlash from the community. If anything, that should be admired not criticized.
It's useful context. Yes, it's good that they listened to their customer base - and I've not criticised the current subscription model.
But I still think it's relevant and on-topic to point out that the previous model was more generous and they tried to do full-SaaS when reading the parent comment in isolation sort of suggests they did this out of the goodness of their hearts (and entirely unprompted).
Earlier quoted context omitted.
>But with a very customer-friendly clause of where if you pay for a subscription for 12 months you get a perpetual license for the latest version of the product when you initially subscribed. And then after paying for any particular version of a product for 12 months, you also get a perpetual license for that particular version and so on and so forth This came about due to a decent amount of consumer backlash, if I r…
Still commendable given how common it is these days for companies to get consumer backlash and just continue to do the same thing while comically trying to publicly convince the customer base that the new model is somehow better for them when any rational person can see it isn't. Also useful as a guide to show the customer they should go ahead and voice their displeasure when these situations arise, preferably before…
Earlier quoted context omitted.
Same here for Adobe Creative Suite; still on version 6 (perpetual license), which I run in a Virtual Machine due to support end-of-life.
Intuit Quickooks is same way. Hasn’t substantively changed in 20 years but they stop you from importing new data if you don’t update to latest every 3 years. They need some real competition.
Earlier quoted context omitted.
I believe you're seeing a conceptual mismatch between workspace and project from how Eclipse and IntelliJ model working. Try creating an empty project in IntelliJ and then add each of your Eclipse projects as a module to the IntelliJ empty project.
Yeah, tried that. Multiple times. IntelliJ just doesn't handle it performance wise, and it feels awkward because IntelliJ just isn't designed as well for working on multiple projects simultaneously. It's probably great for people working on a single project with some dependencies (modules). IntelliJ really wants you to open a project, work on it, then you close it and open the next project. That doesn't fit me. Doesn…
Import each one individually as a new module in a root project, and everything will be hunky dory.
A "module" in this case is just an atomic closure of some sort.
I've got plenty of Intellij projects with >50 modules, each of which are their own git repository, just fine.
Earlier quoted context omitted.
You're talking about how it's easy to move to a function or a file, and then you're "ready to edit", but edanm is talking about actually doing the editing . For example: say I jump to this function and want to fix a bug (the `search` should strip off the first two characters here, not just one). So I need to change `regex.search(s[1:], ...)` to `regex.search(s[2:], ...)`: def compile_hg_glob(line): pat = glob_to_re(l…
Or just use the mouse to point and click in the same time. With laptop mousepads it's just moving a finger. Most devs aren't writing that much code and all these Vim efficiencies are vastly overstated. I've seen many Vim/Emacs-only devs being easily beaten in speed by others using modern IDEs that have tooling and functionality (auto formatting, refactoring, templating, etc) focused on actually getting things done.
Earlier quoted context omitted.
> They used to sell standalone perpetual licenses which included a period of updates. I'm missing something. What's the difference between that and what they're doing now? You pay $X, you get a perpetual licence and updates for a limited period.
Your perpetual license is for the oldest version available during your subscription period, not the newest. Old model: Pay $X.XX and get one year of updates. New model: Pay $X.XX (spread over 12 months) and you can use all new versions UNTIL the subscription ends. At which point, unless you renew, you have to DOWNGRADE to the one year old version. Let's face it, downgrading such an import tool is not something develo…