788 karma · joined April 20, 2016
https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...
I would like to think that the spirit behind that protocol is that the intent to cause permanent blindness in your opponent should be considered a crime. And not that it's not a crime so long as you don't use a laser to do it.
So you can put me in the camp of "this should be considered a war crime", even if it's not in any books yet.
[0] https://en.wikipedia.org/wiki/Convention_on_Certain_Conventi...
https://medium.com/@AlexanderObregon/how-pythons-multiple-di...
and the work of the author, Nancy Leveson:
I don't think the article being from 2006 (or 2004) makes it dated (though it does have a date). I think it addresses a fundamental issue with ORMs that will always be there, which makes it a bit of a classic.
David Hang's Django ORM article has a bullet-point section on ORM cons, including "difficult debugging", "performance", "hides underlying SQL". Whereas Neward's article goes into depth on each of the following topics:
The Object-Relational Impedence Mismatch
The Object-to-Table Mapping Problem
The Schema-Ownership Conflict
The Dual-Schema Problem
Entity Identity Issues
The Data Retrieval Mechansim Concern
The Partial-Object Problem and the Load-Time Paradox
If you haven't read the original article, I highly recommend it. You'll learn a bit more about "Vietnam" (from a US perspective), and be better equipped to discuss and make decisions about ORMs afterward.
[My own opinion is that ORMs can be useful (I wouldn't say never use one), but that a programmer should be grounded in SQL and the relational model[2] first, so that they'll know when to, and when not to, use one.]
[1] https://web.archive.org/web/20220823105749/http://blogs.tedn...
Here's the video of the talk: https://www.youtube.com/watch?v=tz-Bb-D6teE
Good on you for speaking out, and thanks for doing so.
Then I think about the United States' past (and present) wars of aggression overseas, and I can only imagine what a bad reputation american citizens must have all over the world. I'm sure many strangers must hate my guts without knowing me at all, and they have good reason for it.
But ultimately I think that pull/817 is discriminatory against a group of people, and therefor in violation of Github's TOS.
I hope OpenTofu's core devs can have a change of heart. And as hard as it might be, I hope "the Ukrainian dev" can have one too.
And who knows, maybe even Putin himself will be capable of a change of heart.
"Nice things" is a value judgement, subjective, and the question as phrased usually seems mostly rhetorical. It's always a struggle to communicate clearly.
We can, and do in fact have nice things. It's nice to be alive. It's nice to watch a beautiful sunset. It's nice to have potable drinking water. It's nice to have a computer with a keyboard and a monitor and an internet connection. And it's nice to be a part of a community.
But you have to take the good with the bad. We also have a fascistic police state. We have enormous wealth disparity and the resurgence of medieval plagues due to unsanitary living conditions on the streets of our cities. We also have microplastics in our bloodstreams. We have PFAS in our drinking water. We have Donald Trump.
I think your questions are pointing in the right direction. Profit motive. Dark patterns. Hamstrung governments. Acting selfishly.
Personally, I think we'll have a lot more nice things, and fewer bad things, when we can collectively acknowledge that the reason for microplastics and PFAS in our waters and bloodstreams is absolutely the result of the status quo. Just like addiction, the first step in getting help is admitting that you have a problem. And we most certainly need help.
It remains to be seen if we can admit that we have a problem.
Also: https://www.reuters.com/world/europe/eiffel-tower-grows-six-...
Utility may have been an afterthought, but it's still there.
>> Please forgive me, I'm going to be very direct and blunt for a horrible second. It could be thought that the technical way in which you currently look at programming is almost as if you were willing to be "guns for hire." In other words, you are the technicians. You know how to make the programs work. "Tell us what to do daddy, and we'll do it." That is the worm in the apple.
>> What I am proposing here is something a little bit different from that. It is a view of programming as the natural genetic infrastructure of a living world which you/we are capable of creating, managing, making available, and which could then have the result that a living structure in our towns, houses, work places, cities, becomes an attainable thing. That would be remarkable. It would turn the world around, and make living structure the norm once again, throughout society, and make the world worth living in again.
Remote: Preferred
Willing to relocate: No
Technologies: LAMP, Linux, Apache, MySQL, PHP, Perl, Python, Ruby, Java, SQL, JavaScript, Nginx, Drupal, WordPress, React, Bootstrap, Tailwind, HTML5, CSS3, SASS, OMG, LOL, etc...
Résumé/CV: https://ebcode.com
Email: eli at the domain above
I found it surprising, and thought others might as well.
I'm open to saying that the machine is "thinking", but I do think we need more clear language to distinguish between machine thinking and human thinking.
EDIT: I chose the wrong word with "thinking", when I was trying to point out the logical fallacy of anthropomorphizing the machine. It would have been more clear if I had used the word "breathing": When I write I'm breathing, so the machine must also be breathing.