I have never heard anyone mention this, ever.
tl;dr is that the French and German governments are really ahead of the curve then
I work at Apple, so I’m not concerned about being monitored—it’s all company-owned equipment and data anyway.
It was the same when I worked at Microsoft. I used Microsoft products exclusively, regardless of any potential privacy concerns.
Employees at Google and Amazon do the same. It’s known as “dogfooding”—using your own products to test and improve them (https://en.wikipedia.org/wiki/Eating_your_own_dog_food).
As for why people outside these companies use their products, it usually comes down to two reasons: a) Their employer has purchased licenses and wants employees to use them, either for compliance or to get value from the investment; or b) They genuinely like the product—whether it’s because of its features, price, performance, support, or overall experience.
> Why do people use obvious spyware when free software exists?
So, even though the poster was referring to ByteDance when they said "obvious spyware", I was feigning incomprehension in order to ask the question, how do we differentiate ByteDance from what Microsoft, Apple, Google, Amazon (and the rest) do.
It's a real question - why do technical people, who arguably should know better, and can do something about it - continue to use these data-harvesting and user-selling platforms? The answer is obvious when it's the case of an employee of those companies, I grant you that.
My apologies if you feel your response did address that, and I missed it. If so, please help me see what I missed.
Loading parent story...
Loading comment...
I wonder where April would fit in, with your idea? Joining forces with the fellow who made April might be a possibility. Strength in numbers, and all that.
To me the homoiconity of Lisp is mainly about code-as-data, the exact nature of the data doesn't matter to me that much as long as it's a first class citizen and enclosed in nicely balanced parenthesis (though sadly here Janet seems to have fallen to the temptations of the curly braces, and thus, is indeed heresy).
Speaking of unconventional lisps, I enjoyed this recently:
https://github.com/vygr/ChrysaLisp/blob/master/docs/lisp/lis...
from Chris Hinsley, author of the (very) cool Chrysalisp operating system. Same author who wrote this in 1995:
https://www.ponylang.io/discover/
to
https://www.ponylang.io/
On the second link, as another commenter mentions, the "Try it in your browser" is one click away, near the top. On the first link, it's two clicks away, but the first of those clicks is a perhaps surprising backwards-lick to get back to the homepage...
Unfortunately, many of the diehard language enthusiasts here seem to be getting quite worked up over how inaccessible the code examples are. Instead of being able to immediately see the syntax so they can rush back here to make insightful and educated comments on how that syntax compares to $their_fave_lang, they are forced to spend up to 4 or even 5 minutes reading documents clearly describing the design of the language, and being obliged to click on their mouses up to 10 times even in some cases.
If a member of the Pony team sees this: even though it's more than a tad ridiculous and you have in fact made a lovely website with loads of clear information, maybe consider adding the "Try it in your browser" link as another option in the burger menu thing on the left. That way it follows everyone around, and you never have to suffer a HN discussion getting needlessly derailed by the resident PL fanatics.