> It's such a weird take I don't even know where to begin. Are you suggesting that all people who worked at Microsoft to make Windows and IE and all their other products had their labour "stolen" from them? If yes, can you expand on that?
>>This is just mental gymnastics on the level of "it's not murder when the military does it!".
What definition of embezzlement includes both parties willingly engaging in exchange of labour for financial compensation? I think you are right, there is mental gymnastic happening, just not where you think it is.
>>No, because it's not relevant to the discussion.
Norway is basically anything but the Saudi Arabia of Europe. The ONLY thing that is similar is that they both have oil and natural gas in their territory.
Well they do both have monarchs! Though the royal palace in Oslo is a public park. As I was strolling the park, to my surprise I attended a quick fanfare as the king left his palace and his driver (I presume) almost ran over a dumb kid that darted in front of the royal sedan. then at the end of the royal avenue, at the foot of the most glorious mathematician sculpture, the royal sedan turned a corner directly into rush hour traffic, which his highness had to endure just like the rest of us commoners.
What a lovely anecdote, I've been to the royal park in Oslo once and it's gorgeous!
As an Austrian, I personally prefer to look at my royals in the catacombs of St. Stephens Cathedral though ;)
Easy; if you don't want to pay for keeping up with SaaS, don't use SaaS! This is an entirely self-inflicted problem, and it's on you (as in, the gamedev) to fix it.
We don't require labeling for basically any other concerns about business practices and yet everyone seems to care about this one. When I buy chicken it doesn't have a sticker on it sayin "this chicken was probably kicked a few times". or slave labor was used on this chocolate. There are other voluntarily done labeling against both of those, but not a requirement to say it.
The problem is, the narrative is grouping them together. The general narrate is "concern over what it going into our bodies" which has nothing to do with business practices.
> We don't require labeling for basically any other concerns about business practices
Maybe we should. Then again, pretty sure both of those are completely illegal anyway. (Not that that stops it entirely, but somehow I'm not convinced lying about it would be the thing to stop those actors.)
Right I mean the chocolate one is illegal. The chicken one, honestly not fully sure since Purdue keeps getting exposed but idk if they actually have had legal issues? But my point with both of those is, as bad as those would be they don't have an impact on your health eating the product.
Regardless, I don't disagree that we should have some labeling on business practices behind the food that we eat as long as it is actually communicating what needs to be communicated instead of just fear mongering.
"GMO Free" (or requiring it to say it has GMO) tells the consumer absolutely nothing. Its meaningless. All it does is try to sow fear about a thing that its existence itself is not the problem.
"Forbids farmers from using last years seeds", "Uses increased herbicide" like the example the other person mentioned, or whatever that actually communicates what the business concern is to the consumer would be great.
But that is not what we are doing here with labeling GMO.
Not sure where you are from but in Switzerland you can very well choose these things from a product.
It's very unlikely a chocolate without a fairtrade label to be slavery free. Kinda easy to avoid that. So easy to pick to slavery one
We have a few relevant labels you find on ever meat. It's not as easy for meat as there are local variants without labels and high standards but in a supermarket in Switzerland you can literally pick by colour. To get the kicked chicken that never seen a grass halm you just buy the yellow or red package.
Rust macros don't really understand the types involved.
If you have a derive macro for
#[derive(MyTrait)]
struct Foo {
bar: Bar,
baz: Baz,
}
then your macro can see that it references Bar and Baz, but it can't know anything about how those types are defined. Usually, the way to get around it is to define some trait on both Bar and Baz, which your Foo struct depends on, but that still only gives you access to that information at runtime, not when evaluating your macro.
Another case would be something like
#[my_macro]
fn do_stuff() -> Bar {
let x = foo();
x.bar()
}
Your macro would be able to see that you call the functions foo() and Something::bar(), but it wouldn't have the context to know the type of x.
And even if you did have the context to be able to see the scope, you probably still aren't going to reimplement rustc's type inference rules just for your one macro.
Scala (for example) is different: any AST node is tagged with its corresponding type that you can just ask for, along with any context to expand on that (what fields does it have? does it implement this supertype? are there any relevant implicit conversions in scope?). There are both up- and downsides to that (personally, I do quite like the locality that Rust macros enforce, for example), but Rust macros are unquestionably weaker.
Thanks, that’s exactly what I was referencing. In lisp the type doesn’t matter as much, just the structure, as maps or other dynamic pieces will be used. However in typed languages it matters a lot.
I was already a satisfied paying customer. I don't need that new stuff but I understand they have to go where the market goes if they want to stay relevant vs competitors (Microsoft VSCode/Github/Copilot) in the eyes of prospective customers who judge products using comparative feature grids.
If you don't want to use an IDE or pay for your tools that's fine. You don't have to look for reasons to hate on it. No one cares what you don't use.
> I don't need that new stuff but I understand they have to go where the market goes if they want to stay relevant vs competitors
Looking at the people racing to jump off the cliff and saying "let's maybe consider not doing that" can be an competitive advantage, see https://procreate.com/ai
We have a metric for the difference between what you charge for something and what you paid to provide it, it's called net income. Here's Microsoft's: https://www.macrotrends.net/stocks/charts/MSFT/microsoft/net...
Elsewhere, we tend to call that embezzlement.
reply