vb6 200MB,Python 10MB,twinbasic 21MB,Is there still a market for small ides?

[xiaoyao]

For example, the lowest price of an iPhone in China is $1,000 and the highest is $2,500.
Although he could also release a lower-priced product based on the IPHONE4. But it could seriously hamper sales of higher-priced products.

That is, if you keep VB6 updated continuously, with a small number of updates every year, it will cause many companies to not want to buy development tools like VS2019.
Just like if you have been XP,WIN7 a small number of updates, mainly to solve problems such as vulnerabilities. Although the workload will not be too large, but the maintenance of stable, small memory occupation of the classic old version of the operating system, will hinder the new version of WIN10,WIN11 sales.

What Microsoft needs is for businesses and individuals to keep buying new products, rather than sticking with old ones (which are almost free to upgrade) or not upgrading with no impact on usage, which is self-defeating for Microsoft.

But Microsoft did not consider the needs of users, such as forcing the installation of the new Google-kernel edge browser, and 100% blocking users from opening iexplorer.exe.
For individual developers and some small businesses, a 200mb VB6 is sufficient.
But a vs2022 requires iso have 45GB, and it may be necessary to add a separate hard drive specifically for development tools.
PYTHON 3.11, the installation package is only 10MB, unpack 19MB
VB6 core file 4.5MB, extract 11.5MB
vb6 sp6 Simplified Version 10.5MB 30MB
vscode 1.82; 90MB
A simple IDE with a relatively small footprint is also what many developers need.
There are many programmers who don't keep writing code every day, and installing an IDE within 500MB is the most convenient.

[xiaoyao]

What is Microsoft's attitude towards their product VB?
What is Microsoft's attitude towards their product? How concerned? Will they abandon the product?
Very satisfied, and continue to innovate and generate revenue.
Every piece of software is doomed because it was created to die, and Microsoft would never allow its customers to use the same software for decades without buying its new product.

VB6 and twinBASIC are "twins". You know, just like Arnold Schwarzenegger and Danny DeVito are twins.
https://nolongerset.com/the-twinbasic-family-tree/
Attachment 188716

[xiaoyao]

VB6 is one of the best products that Microsoft has axed.
I was fighting Delphi back in the day, and it was really good back then.
Of course, thanks to windows compatibility is too much, and it can still be used now.
The main reason was that it was really easy to learn and powerful (for the time). Especially the database desktop application and the smooth development of office, you can see how much Bill loved it.
After Microsoft killed VB6, in fact, it has not been able to make a development tool that can achieve such popularity.
Yes, even C# is not as good as VB6.

[The trick]

again

[fafalone]

tB was 11MB before the LLVM dll for optimized compiling was added. It's small by any reasonable measure of full-IDE based programming tools made after 1998. Though currently yes currently it's the biggest memory pig on my system, usually under vs2022 and waterfox, but too often exceeding it. That will be fixed eventually but it's low priority next to language and features.

radBASIC is, I **** you not, 2.48GB

[xiaoyao]

RADBASIC,YOU BUY IT?
How to use the effect, update once a few days?

[OptionBase1]

radBASIC is, I **** you not, 2.48GB

***. Size over substance?

[dilettante]

These advertising threads don't belong here. Post them in Other Basic if you have a point at all.

[fafalone]

Oh he posted his rambling in Other Basic too. I haven't checked the C++ forum yet.

[xiaoyao]

From the Internet, I saw a very powerful programmer who reduced Google Chrome 500MB RESIZE to a DLL of only 40 megabytes.

The biggest obstacle this time is the ubiquitous mojom. Unlike the old version of chromium, which makes external calls into interfaces, the new version is almost entirely a variety of mojo cross-process calls. The mojo script needs to generate a bunch of code to serialize and deserialize for transmission across processes. But I don't need these features. It took me months to figure out how to kill mojo. That pile of mojo is too big. Originally, I wanted to delete one by one directly and change it into an interface pointer. After a while, the workload was too heavy. I gave up and started thinking about new methods from scratch. Finally, I wrote a script to regenerate the mojo pile of files and simulate the call of mojo.

Just the glue code of V8 and dom binding in the gen directory, the generated lib is more than 4G, which is hard to imagine. Because the lib generated by this code before is only tens of M. And the new version of V8 itself is also very large, I split it into three parts to bypass the restriction that lib can not be larger than 4G, while the old version of V8 can be smaller than 4G without splitting. So when I compiled the release, I had an intuition that it was at least 6 or 70 M, but I didn't expect it to be 43 M. Although it is much larger than the old version, it has far exceeded expectations.

[xiaoyao]

If one day, TB also develops to two GB, I feel that it will be very inconvenient to use.

[fafalone]

I really don't see that happening as it's not intended to be the next .NET with all it's spectacular bloat.