@eval JS obfuscation is weak and not strong as with C++

C++ is complex and the generated code is complex too while C is not.

Decompilers are bad at decompiling C++ code . They need extra mess of plugins to decompile a OOP based C++ code.

@ReverendLovejoy

I guess my mind needs a lot of things.. LTS is just one of them.

@ReverendLovejoy They can't do what the fuck they want. Real Jeff Bezos can prove it. Legal systems are complex. Enough buffer overflows everywhere.

One tactic comes to my mind is patent trolling

@Berkmann18 It broke within a year. I need LTS.

At least 10 year or so. They are feel free to break it in 5-10 years.

@fristys Don't want to hear about that fraud anymore. Soon, he will be poorest person according to Big Short Seller.

Killed my GF and she worshipped him more than I. At the end, they didn't pay for her life.

@Sony-wf-1000xm3

Users care. See user who posted rant.

QT provide source code protection by default but Electron don't thus leaving your source code for anyone to unpack which I believe no company wants, apparently they have no idea it's even possible it seems!

QT is easy, fast. I have no complaints.

In my eyes, Linux is Fauxpen Source!!

@AtuM Linux is proprietary under open source mask.

$$$ -> Consulting & Conferences -> Linux Foundation

$$$ -> Startups -> IPO -> Gift -> Linus

Redhat rocked it :D

@Sony-wf-1000xm3 Assuming his Electron apps are Slack and Skype, QT is nothing for them.

They can buy 100 year worth license in one night.

@Sony-wf-1000xm3 NodeJS is expensive too.

You just don't know it.

500 MB just for modules.

On top of that, it eat ram.

Expensive than QT license!!

I fucking hate Electron apps too. Why the fuck they can't write in QT?

What a beauty is QT

@Fast-Nop

Well, If I put other way. I'm fine with breaking changes too but the one year gap felt too much to me. It's fine if they do a breaking change in 10 years from now.

@Fast-Nop Well, it's. I assumed you are a front end developer.

I don't want breaking changes ever, ever...

I want everything to be Windows alike.

@Fast-Nop

By the way,

The languages that supports function overloading actually use prefix when compiling. The prefix is made up from function signature.

@Fast-Nop

That's for languages that doesn't support function overloading.

I'm in this industry since 2003's and mainly working on writing Kernel level Drivers.

Svelte felt like C but that seduction is gold digger one.

By profession, I'm not a front end developer.

Svelte should become ISO accredited. and maintain quality control not dick moves.

@bittersweet You understand the US legal system is most complex in the world. There are always loopholes around it. You just need to find lawyers who charge $2000/per hour.

@bagfox

This,

github/sveltejs/template

It has changed now but it was diff by the time I used.

I don't want to learn it every time it change. I want it to be stable. This is like living next to SUN, you never know when it hit you!

@bagfox

I grabbed it on 2020/04 just like all other people do.

It's a NPX template with ready made config.

They broke that Config with this year update!!

This is not related to Browsers.

@Fast-Nop So what? Can't you publish content on that day? It's published for Fools who are trying to prefect every API.

@Berkmann18 I didn't read change logs on my life. I only know such a thing TODAY!

@Berkmann18 I created my app for Chrome.

The issue is not with my code. The issue with their configs like rollup. A year old config doesn't work because they added new option called compileOptions.

@N00bPancakes Well, they have broken their rollup plugin.

@bagfox Incorrect code?

Joking me?

I used their npx templates

@bagfox

More on,

snoyman dot com /blog/2018/04/stop-breaking-compatibility/

@bagfox

It wastes time
----

Let's face it: changelogs are a total waste of time. No one ever reads them. Ever. And the only reason you're writing them is to notify people of backwards incompatible changes. So now you've wasted the time of two groups of people:

The library maintainer has to write a changelog that no one is going to read
----

Users of a library have to spend time reading the changelog that they're never going to read anyway
Instead, try this one simple trick: never break the API in any way. It takes literally no time to not break things. So save yourself and your users some time, and:

Freedom is Slavery
-----

The freedom to break an API is a false freedom. In fact, you are now a slave. You're a slave to perfection. You will never be satisfied with your API. You'll always want to improve it. You'll want to make it safer, easier to use, or provide more efficient functions. If you go down this route, you'll never be free!

@bagfox I'm vegan and don't do drugs like you.

@N00bPancakes

Why do you call 1 year old app as legacy?

I fucking love React now and will learn as soon as possible. Svelte become a mess to me recently. I just opened a rant on it