So did I. But things have changed, and some of those people with whom I remained in contact now use FB to the near exclusion of everything else.
These people are family in their 90s, for whom well-meaning children and grand-children have set up on FB. They don't use email, they can't write letters because of arthritis (and time delays ... international post can be very slow), and effectively the only async comms they use at all is FB.
I'd ask that you not try to tell me what I really mean.
I had the same situation with far away old people (grandmas in Venezuela, on in France, me living in Africa or Asia), some had problem with sight, earing, etc.
They didn't have internet.
We managed to get in touch.
> I'd ask that you not try to tell me what I really mean.
Manner of speaking.
The important is again that it is a matter of cost vs convenience.
I understand the cost can get pretty high.
Yet still, people kept in touch for decades with old distant relatives before the internet.
Using facebook is convenience, that's the point. It is very convenient.
It's the whole argument of this thread: the convenience eventually makes most people discard the cost of not using FB as too high, and the privacy things as not important enough compared to that.
Yeah, for your mother definitely makes sense to already have more than one weekly phone call, but I was thinking about other family members.
Reading your post, it seems Facebook is a bit of a recreational activity to keep them sharp and social, which is good. What I was thinking is whether you need to participate in it, since the people this age I know is more than willing to keeping me up to date on all interesting stuff by talking. But of course each family is different so I'll just assume you know what you're doing!
I'm over 60 and I hate talking to people on the phone. My mother likes it, and that's why I call her three times a week. But most of my aunts and uncles prefer to show their photos on FB and talk about what they're doing there. I call them for birthdays and special anniversaries, and having kept up-to-speed via FB means I can talk about things that really matter, or get clarification on things that weren't obvious.
But they like using FB, and it's the only effective way I know to stay in touch and remain a part of their lives.
> What you realy mean is that you value more the convenience it offers that the price to pay for using it.
People should be more charitable.
They said that they must stay in touch with these people and that these people can’t seem to use other things. Often times you have to stay in contact with family members because they aren’t able to properly care for themselves. Those same people may not have the ability to easily change how they interact with the digital world due to mental health issues and you have no choice but to meet them where they are.
I think this is largely a straw man, or taking an extreme case as representative.
I have friends that are not on Facebook. It requires more effort to stay in touch with them (for example, calling them on the phone) but it's doable. I don't see how a thing that was invented 10 years ago is now the sole method of communication with loved ones.
That said, I agree it's not without cost to delete Facebook.
I spent 20 years talking to friends and familly around me, and they don't care. They won't even try Firefox if they are used to chrome. Not even that small effort.
We had the US mass spying revealed in the press, with the PRISM program exposed. The public mostly carried on as usual.
Snowden got persecuted, giving the issue a lot of publicity. He wrote a very good book explaning why surveillance is dangerous. Again, most people didn't flinch.
A lot of people on HN reported trying to talk to people and get blank stares. "I have nothing to hide". "I don't care if people are collecting my data".
This is not just a failure in regulation: people don't give priority to problem that are not a pain right now. It's too abstract. Not to mention they have other problems that are a pain right now, and are armed with limited time, resources and knowledge.
Same problem with climate change. Their life is fine now. They can't care about the impact of their consumption in x year when they have to think about a loan, their health, the kids getting in trouble at school, their boss being pushy lately and the lattest form they have to fill.
There is also the cost of trying to avoid tracking product at the individual level.
I won't use Apple since it's locked down. So I use android. But I can't sign in into a google account or it will track everything. So I can't use the app store and many app won't work.
I can't use the best app provider like gmap and waze, have to sandbox youtube which mean it's mostly suggesting terrible content as it assumes I'm the average human.
I have a collections of extensions on web browser and several Firefox containers to isolate everything. Something I spent a lot of time to learn, master and configure.
I use Linux because Windows is tracking you, and MacOS is a golden cage. So I can't buy the best laptop CPU out there, which is the M2, and have terrible battery life.
My friends harassed me to have a FB account. Then an insta account. Then a whatsapp account. So I have to accept to miss out on things, and their nagging about it for every communication.
Now I am willing to accept all that because I think there are things more important in life than being part of a group chat or having the latest trendy thing.
But it's a hard sell for a many, espacially since, once again, "their life is fine right now".
Python is used for Web dev (Django), geography (all SIG), system components (part of Unix), pen testing (E.G: scapy), 3d modeling (Blender), sysadmin (ansible), etc.
I've been coded mostly in Python for 15 years and using the scientific stack is a very small parts of what people pay me of, if they ever do.
You're misinterpreting that quote as criticism of Python instead of praise. He's not saying that's the ONLY thing that Python is good for.
I've also been programming in Python extensively for at least 20 years, including web application servers like Zope and TurboGears, embedding and extending apps and tools with the Python/C API and SWIG like SimCity, Gnu Radio, Big World MMPORG, robotics, simulations, Blender, Houdini, user interfaces like Tkinter and PyGTK and Sugar, XML processing, OLE integration, BeautifulSoup web page scraping, image processing, character animation, speech synthesis, system administration, infrastructure as code, machine learning, etc.
Python is of my primary programming languages, and I love it.
It's a GOOD thing that mathematicians use Python instead of Bash!
It's pretty clear and not subject to interpretation that I never claimed mathematicians ever used bash, but just the opposite: they use Python instead.
Bash is an easy way to plug other code together, but it's terrible for math. Python is a much better way to plug other code together, and it's much better at math.
If your argument requires me to "forget the technical debate for a minute" (and why should I?), and also you're nit picking at semantics with your own arbitrary definitions and personal interpretations, without any links or citations to back yourself up, you're really out on a limb there.
Do you really believe that I don't know what Python is good for after using it for over 20 years, working with clients including mathematicians, game designers, ai researchers, and my own personal open source projects like SimCity/Micropolis?
Doing map(lambda x: x + 1, stuff) or [x + 1 for x in stuff] adds nothing of value for those very simple cases. I wish we had map($1 + 1, stuff), or ever better, stuff |> $1 + 1.
Python does a lot of things right, but for a language with a strong emphasis on the iterator design pattern, I wish it would provide more expressive primitives.
However, it comes with the FP territory, which Python is not well suited for, and it would also imply a higher cost of entry to beginners.
I understand this coming from a newcomer but after a while it felt like second-nature to me. I was curious about parent poster, because they said they are using Ruby for years.
How does this make it confusing? What information do you feel () gives you?
You might say:
foo().bar().baz()
Ah well these are clearly method calls, they have ().
But this is Ruby:
foo.bar.baz
These are clearly method calls too, because in Ruby there’s nothing else they could possibly be. The ()s don’t actually disambiguate anything. Unlike C or Java or some other languages with some notion of bare access to internal fields, there are always and only method calls.
I can't fathom optional parenthesis. In this code it makes it very hard to know if today is an attribute or a method without knowing the context, meaning I can't scan the code, I have to read it carefully.
I'm going to emphasize this as well. Everything is an object, and everything called on an object is a method. Full stop.
Unlike with other languages, there is no ambiguity here.
In python, you don't know when you dir() an object whether your dealing with a property or method. In Ruby, you are guaranteed it's always a method. A perk is that you don't need parens.
Exactly. Once you get some basics of Ruby, there is no ambiguity, and I find it quite elegant.
And I think I’m in the minority here, but I prefer the cleanliness of optional punctuation.
That feature also allows for fluent DSLs (which seem to be falling out of favor for various reasons), but is one of the reasons I still love Ruby.
To look at the other side, I hate having to constantly add semicolons and parens in other languages. Makes my poor fingers hurt even more than they usually do.
I think this kind of falls in line with the idea of Ruby giving you sharp knives[0].
Like you I used to have a love / hate relationship with this because it feels inconsistent to sometimes use parenthesis and sometimes not. In a world where you just want to run Python's Black code formatter and always use parenthesis, having to think about when to use parenthesis feels really tedious.
But I think nowadays I'm happy that they are optional because when you want them to be optional it creates a really nice aesthetic to your code.
For example with Rails you can do: `2.days.ago` and then there's also things that feel like a mini DSL such as `validates :title, :body` or `belongs_to :users`. These just look nicer without parenthesis.
With that said, I do use parenthesis more often than not but it's nice to avoid using them when it makes something look nicer visually.
Given the context of this thread (comparison of ruby and python), it should be noted that python also has this. You can decorate a method with `@property` and call the method without parentheses.
It's really nice because it means you don't have to pre-wrap all of your properties with accessor methods. They can just be properties, and if something changes, you swap the property out with a decorated method and you don't need to change any code.
> I can't fathom optional parenthesis. In this code it makes it very hard to know if today is an attribute or a method without knowing the context.
Optional parentheses exist because it is impossible for there to be ambiguity: after a dot, if a name starts with a lowercase letter it is a method (and the reference is a call). If it starts with an upper case letter, it is constant (which is not callable as a method.) There are no other possibilities.
“Attributes” in Ruby are literally just getter methods (possibly paired with setter methods.) There is no object-dot-field access to fields (instance variables exist, but outside access to them doesn't use that syntax, but instead goes through a different set of method calls: Object#instance_variable-(get/set)
Makes reading ruby so much more difficult. Also optional return statements. If you need to refactor a function, it’s not always obvious that it’s relying on an implicit return and super easy to break things IMO
(not trying to convince you as I think in this thread no one will be convinced of anything)
Knowing that in Ruby a method will always return its last executed line unless explicitly returned early makes (at least for me) things very easy to get.
A method with two branches will always return the last line of the executed branch, thus you will always know what the response could be.
But this (IMO) is because Ruby OOP where the main concept is that when you are invoking a method you are actually sending a message to that object thus you should get a response. So Ruby makes this way of working with objects universal.
Once you call a method you will get a response.
I find it strange the other way around, working in languages where I need to put return even on the last line of the method. For example after almost one year of full time backend development in Ruby, I needed to write some JS code. I debugged for half an hour why a short function that I wrote was not working properly until I got it: I need to add 'return' to that last line to get the actual result. This was strange for me :)
In case you want (and need) to get how to think in Ruby I recommend you to listen to this talk by Sandi Metz (and in general I recommend all her talks even if they are old): https://www.youtube.com/watch?v=XXi_FBrZQiU
It presents OOP in Ruby in such a beautiful way and it takes a while to start thinking like this.
There may be other things about Ruby that I disagree with, but this is probably my primary disagreement.
It does make code more difficult to understand for exactly the reason you mentioned, and furthermore it can sometimes be disallowed based on the rest of the expression (such that parens are required).
In my own Ruby code, I often use parens when they are optional.
Almost any software project from Google with some kind of user-facing API seems to fail, because Google somehow sucks at API design. Like how awful to use Tensorflow became, leading to it getting largely replaced by PyTorch. Or how complex and convoluted AngularJS was, compared to ReactJS which replaced it. Google's design philosophy seems to be the polar opposite of Linux's "Don't break userspace", so I can see why application developers wouldn't trust a kernel written by them.
Dart itself is another example: it started similar to Typescript, but Typescript quickly grew to surpass it in every way. Because Typescript eagerly learned from modern programming language theory, while Dart stuck to Google's "try to make everything like 1990s OO" approach.
It's the same with feminism, pacifism, communism, veganism, etc.
I have around me numerous activists about various topics I'm not invested in: feminists, communists and vegans, mostly. Most of them don't try to guilt trip me or convince me of anything. They just do their stuff.
Once in a while, one of them do, just like once in a while, a doctor makes a medical error or a plane crashes.
But we tend to only remember this one, and associate the movement with it.
What you realy mean is that you value more the convenience it offers that the price to pay for using it.