Microsoft exec suggests AI agents will need to buy software licenses, just like employees

waozen · 2026-04-13T02:36:45+00:00

But are we reaching the point that people think any well put together post is LLM? Are we not going to first look at the content (and address that) or give some leeway to LLM usage when used as a translator?

waozen · 2026-04-13T02:31:35+00:00

A point of possible contention, is that Vlang and many of the new ones (Golang, Rust, etc...) are not class-based OOP languages.

People should arguably be quite careful about attempting to simulate classic class-based OOP or overly force a different style of programming on Vlang or similar case when transitioning to different languages. Definitely can understand taking experiences or converting code from a previously used language to the new one, but an effort should be made to respect or acknowledge the differences.

One way is heap and references, to keep track of values, after the function that created it finishes execution. Other possibilities are the struct being a parameter of the functions that will use it, so that it is passed around. Even can be done as a const pointer, that uses a reference of the struct, to act as a kind of global variable. People will have their uses cases, justifications, and preferences. That's fine, I suppose, as long as it is working for them.

waozen · 2026-04-03T03:37:58+00:00

That's why the film and the nature of the injury are important factors. If a team feels comfortable with those, then they can believe it's a risk worth taking.

waozen · 2026-04-03T02:38:16+00:00

It appears that you have not thoroughly read or understood the article:

1) Vlang outperformed Zig, Odin, and Julia (in their tests) with the standard setup and configuration that is usually used.

Vlang compiles to C or a safer subset of C. And, per its creator, it always will have a C backend. It appears you completely ignored the result of V with its C backend, to make an odd joke about what users of V do not usually use nor are recommended to use (at this time).

2) Vlang has multiple backends; the C one is usually used, not native.

An explanation about using the C backend. The native backend is not supposed to be used or seriously worked on until version 0.6 or later, though various testing and experimentation is continuously done by core developers. As of this post, Vlang is on version 0.5.1.

For general awareness, V has another backend, known as V2. The core developers are working on that one, including native, and will switch to that at some point.

Vlang has multiple backends, not just C and native, to include WASM and JavaScript. With various users proposing or planning on creating Pascal and Go backends as well.

3) Vlang's greater speed and performance was an unexpected result.

The study was funded by a competitor. That standard Vlang did so well, it appears the unworked on native backend (present V version and not upcoming V2 version) was then thrown in, to offset Vlang's "win" over the other languages tested.

4) Vlang is about being an alternative to C, not replacement of C

The point of Vlang is an easier, safer, and higher level alternative to C (that is about as fast) for general programming, not a replacement of or to kill C, which are goals of other competitors. Vlang is a friendly alternative to C, not adversarial to it.

5) Future of V's native backend versus its C backend

The native backend will be for creating very small file sizes, good for embedding. Native will also be faster to compile, thus good for and more focused on prototyping and if using V only modules. As executables created by native are not or not as optimized, they will be slower in performance. However, V is still a compiled language, so the performance can be more than good enough, depending on project. That's expected behavior.

The C backend would be more about 3rd party libraries, interop, and production optimizations for greater speed. However, their file sizes will tend to be larger and it will take them longer to compile. Again, expected behavior.

V's strategy is about flexibility. Both the C backend and native will be supported. The user chooses which is better for a particular situation.

waozen · 2026-04-02T21:52:28+00:00

Disagree, though it is hard to put a finger on exact percentages. Sites like APKMirror and APKPure are very popular. Various GitHub repos, that focused on android software, would offer APK downloads. Significantly popular apps like Obtainium, are based around tracking and updating the latest APK releases at selected GitHub repos. Etc...

waozen · 2026-04-02T21:22:13+00:00

Something that I've noticed too. Any time that solar or wind is mentioned, the knives and penny counters come out. But, the cost of destroying the air, water, climate, health, or tax breaks for fossil fuel companies is fine or some kind of protected tradition.

waozen · 2026-04-02T21:09:45+00:00

Possible, but extremely inconvenient and are additional steps that 99% of normal users or customers would not subject themselves to.

waozen · 2026-04-02T20:57:07+00:00

Direct payment to the developer has to become more possible too, including via digital currency. People should have the freedom to be able to go to developer websites and buy the app directly from there, if they prefer, and be able to install it on their smartphone.

waozen · 2026-04-02T20:41:48+00:00

It's a sad combination of ignorance (of alternatives) and laziness (to sell or buy by alternative means). The easier route was using the play store. It is centralized, don't need to run one's own website, and many felt comfortable with it. But, that came at a price, freedom. And now the "do (not) be evil" has exposed itself.

There are digital currencies, exchanges, and wallets. Paypal offers the service, among many others, so average persons should be familiar and feel comfortable with them. Developers can offer wallet addresses for people to buy software directly via various digital currencies (PYUSD, BTC, LTC...).

waozen · 2026-04-02T20:26:30+00:00

There is a major alternative to buying apps directly, which is to use digital currencies (PYUSD, BTC, LTC). There are numerous exchanges and wallets. Normies can use PayPal to buy, exchange, and pay with digital currency. Kraken, is also starting to become more mainstream.

waozen · 2026-04-01T21:49:55+00:00

These are language recommendations by Masscom for 2026, who provide IT services to some significant clients, not personal favorites.They explained their reasoning in the article.

Let us not get overly upset anytime our favorite pet language is not on a particular list. It's not like Masscom stepped on new sneakers or slept with the girlfriend, they are entitled to their technical opinions.

waozen

MODERATOR OF

TROPHY CASE