Hacker Newsnew | past | comments | ask | show | jobs | submit | jrhurst's commentslogin

All that really will matter is how the government and courts see it. Those words will be used in court.


Closer to two thousand years ago. That's how far removed it is.


I haven't played with nim for a few months, but only parameters with var will get mutated. I suspect you want to use someone else's cursed function and don't want to poison your blessed code


I see. I know nothing about Nim but I do see in their example they used var when declaring the function. This way seems like it's hidden to the consumer of the function but hopefully editor tooling helps with this.


You have to declare the variable as `var` as well, eg.

    var arr1 = [4, 2, 3, 6]
    sort arr1

    # Doesn't work
    let arr2 = [4, 2, 3, 6]
    sort arr2
You'll get a warning about the latter from the compiler (and nimsuggest for editors).


Hard to tell. We'd have to ping similar programs in order countries because there was massive depression on the value of the dollar than.


Price gouging is the free speech equivalent of yelling fire in a full movie theater. You are harming people for your own enjoyment.


People who use the "fire in a crowded theater" metaphor clearly don't know where it came from. It was coined by Justice Oliver Wendell Holmes, Jr. in Schenck v. United States.[1] He ruled that it was constitutional to send socialists to prison for distributing leaflets against the draft in WWI.

In the same way that dentists agree that sugared gum is bad for your teeth, economists agree that price gouging laws make everyone worse off.[2] For a concrete example of how price gouging laws led to shortages, read Michael Munger.[3]

1. https://en.wikipedia.org/wiki/Schenck_v._United_States#The_C...

2. http://www.igmchicago.org/surveys/price-gouging

3. https://www.econlib.org/library/Columns/y2007/Mungergouging....


Strange. I've often see people with peanut allergies have alligeries to nuts like Almonds but not to Legumes like Chickpeas or Lentils.


Our minds like to categorize things, but nature doesn't really give a shit about stuffing things into convenient cubby holes.


Where I am I've never heard of 'nut allergies' including peanuts, but people with allergies to peanuts (and other legumes) specifying peanut allergy.


My wife is allergic to peanuts, lentils, chick peas, etc, but not almonds and the like.


As one commented mentioned these "nut allergies" can be psychosomatic, where the mind is literally triggering the physical reactions based purely on expectation.

On the other hand "nuts" including peanuts are typically processed in the same facilities, so cross-contamination is real too.


Could you elaborate on how things get messy?


For me:

Trello: boards get stale

Txt file todos: more todos are added each day, none get removed because of new ones added!

Basecamp: same issue as Trello.

In this second half of my career I've dealt mostly in startup development. MVPs just pivot too much. It's a ride.


what do you think about auto delete tasks?


I find ECS a pretty intuitive concept, but it always ends up being a massive yak shave to me


Agreed. The vast majority of the benefit is simply from learning to use composition over inheritance.

Most applications that aren't games don't need to support things like finding all active objects of a type or maintain many discrete actors executing their own run loops.

But Unity isn't dumping a lot of marketing into talking about the decorator pattern so everyone is jumping right to ECS now.


When performance matters I often find myself yak shaving existing code to basically turn it into structure-of-arrays format (like is required for ECS), if not converting to ECS entirely. The alternatives scale so poorly...


What were your problems with it? Was it using a particular library or engine, or you did it yourself?

I'm curious because I started using ECS-like techniques exactly because traditional OOP in games felt a lot like yak shaving.


I assume if the company publicly denied the accusations it would not be considered insider trading


Same reason most businesses that are generating wealth from employees are not employee owned?


Generating wealth from employees, has nothing to do with generating wealth from customer data.

If what is of value is customer data, customers can and should own and control the entity generating the monetary value from their own data.


So initiative, organization, access to information and bargaining power


Employees at least get paid, knowledge workers sign over their intellectual property in exchange for a salary. There is no concept of data ownership, but there could be something similar. Imagine companies having to license your data and pay you a stipend or the like.


Your compensation is in the form of services rendered.


Yes, that is the big tech talking point.

However, the reality is big tech needs customer data, customer data does not need big tech. So where is the negotiation? How is it possible big tech can pay the same (i.e. service rendered) to all users, where users data is not of equal value?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: