Wow, not even a perpetual fallback license?
I wasn't super thrilled when Jetbrains switched to a more subscription-based system, but being grandfathered in (so I didn't have to restart the subscriptions as if I were a new client), the heaps of existing goodwill they'd built up, made the changeover much less of an issue, and super importantly finally listening to customer and adding perpetual fallback licenses alleviated much of the fear.
These vanity-soaked strokes of needless sensitivity is precisely what is keeping these bad meanings alive.
No one knows, or remembers an association, yet you can't help yourself doing a great disservice to the cause you pretend to care, by popping up and unsolicitedly "correcting" someone.
I do not care. I'm here to read about some tech company changing their revenue model, and what tech people has to say about it. If I cared about endless discussions and virtual virtue hoarding about race, gender and politics, I'd be browsing the dark side of twitter, not the front page of HN.
I'm so tired of langauge being turned into a minefield, and every conversation ending up being about race, gender, religion, politics and whatnot. I'm a technical person, I care about technical stuff, and I use langauge to communicate technical ideas, not ideological ones.
Like cool opinion, nobody has to accommodate you the same way you don't have to care about how the words leaving your mouth may be perceived by others unlike you
As I like so say: "I am merely 30 cloudy days away from white, and just one good tan away from 'person of color'." Therefore, I have the least stake in the racial discussion. Doesn't affect me one way or the other.
However, I am not least bit of shy to hiss at either side when they cross a certain line. At one side, if you take a person's race into account while deciding anyting, you're off the game for me. At the other side, if you try to control my language, you are off the game as well.
Your capability of being offended does not, and should not grant you rights or leverage against other people.
As a tech person, one should already know why censorship, blacklists and backdoors are bad ideas. Because no matter how pure your intentions were when you were first putting them in place, once in place, they inevitably will creep forward and get bigger and worse.
Let's skip the can of worms about if the political correct speech is effective. It will be an endless discussion. However, we can discuss the practicality of policial correct speech. Because those are the two requirements of any solution to any problem: 1) effectiveness 2) practicality If you fail one, your solution is, well, not a solution.
Simple argument:
1) "offensive" is a subjective, and elastic word
2) therefore set of possible offensive words for a large population is infinite
3) infinite amount of taboo words = no communication
4) THEREFORE: we must assert that political correct speech is not "practical", and can't be a solution to anything.
I advise you to put your energy into more practial solutions. That is, if you don't care more about being right, over being effective.
Don't pay for SaaS, don't encourage this bullshit. If foss offerings don't cover your usecase piracy is better for humanity than paying.
That's fine with fixed priced software if the software is static and frozen in time, but most software is living and breathing and requires continual investment.
You can absolutely use an old WordStar license. In fact, several notable authors do.
Saas isn't the only way to pay people.
> most software is living and breathing and requires continual investment
Is it though? or is this broadly another side effect of value extraction focused engineering? I'm quite happy to buy a new version if it makes my life notably easier. CS2 is broadly a better experience than CC, etc. etc.
> Saas isn't the only way to pay people.
> It kind of is if you have a product that people expect updates for, or you have to have very high prices, or a secondary source of income.
> > most software is living and breathing and requires continual investment Is it though? or is this broadly another side effect of value extraction focused engineering? I'm quite happy to buy a new version if it makes my life notably easier. CS2 is broadly a better experience than CC, etc. etc.
But are you happy to pay for better architecture that doesn't have shiny new features? Or support for new X (depending on the product this could be image formats, it could be architectures)? etc
To be clear I am not saying I want subscription based software, but I understand the business argument for it.
Depends on what product, and my use case.
> To be clear I am not saying I want subscription based software, but I understand the business argument for it.
Has nothing to do with more supported X or better architecture, its just about money. In fact SaaS offerings are often compromised and worse of than when they were standalone (at least in my experience with software that made transition from standard releases to subscription).
Additionally in my experience with software that went that route (standard paid releases to subscription) that just signals that the customer milking has become, and pretty much any new feature is looked at from how can we milk it standpoint.
That’s how more or less all features are chosen? The alternative is going out of your way to spend time/money on features you know have minimal/no interest.
For whatever reason at the time, that opened my mind to why people do things
Only the decompiler is better in Ghidra, IMO, but I'm sure there's a plugin for that.
I’ve been paying for Hex-Rays out of my own pocket for a decade because it’s a great tool, but $8000/year for a personal license subscription? Forget it.
> It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a denial of service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property log4j2.noFormatMsgLookup to true do NOT mitigate this specific vulnerability.
The new subscription model will almost double my costs ($900 / year), all while I've been getting less and less value with each update. Furthermore if I ever stop paying, I will lose access to the product.
Whereas if I stop paying now, I will maintain indefinite access to what I currently have.
I think I simply won't renew next year, and will rely on Ghidra to fill any gaps going forward.