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

Getting a rejection message, even an automated one, removes ambiguity. You're no longer wondering if you missed a call or an email went to spam, you have it right there in writing.

In college, I interviewed with two different local companies that had internships that would continue as part-time positions during the year. Both interviews went well and I felt that the interaction was positive overall. I was confident that I would at least have a good shot at each position after the interview. Both companies ghosted me.

For someone just developing their career and who was excited to work with actual professional companies (instead of the minimum-wage jobs offered to most students), that was kind of a big deal. Looking back, I'm pretty sure that's what really instilled a lot of the cynicism toward interviews I carried even after getting an internship and graduating into a full-time sysadmin position. I honestly got lucky getting the position I did, and I think without that success my cynical view would have spiraled downward.

> Getting ghosted is part of life.

The argument is that it shouldn't be. Responses like yours when people express hope that things can change is just digging your feet in because you think that other people have to deal with the same hardships you did. Everyone acknowledges that getting ghosted sucks, so maybe having a bit of empathy and sending something, even an automated message, should be encouraged more.


It's not like job searches are the only context where you can get ghosted. It happens often enough in friendships, social activities, finding romantic partners, etc.


The more and more rude interactions like ghosting we have, the less human we become. Relationships become transactional instead of meaningful. On the other hand, talking to people as humans and leading with your humanity first makes you a better human.


> It happens often enough in friendships, social activities, finding romantic partners, etc.

Yet as we get older we usually get the chance to curate our surroundings such that those people aren’t around us anymore.


I didn't want to bring up ghosting in other contexts because the conversation has been more focused around the job market. The idea that everyone hates getting ghosted even if they do it themselves is one I picked up from articles about dating, so there is still shared relevance.


The main relevant difference between the former and all of the latter is that we're generally fine with regulating the labor market, but (liberals at least) are generally much less willing to regulate the interpersonal relationships market.

(The other relevant difference is that the labor market involves a significant unilateral power imbalance between the employer class and the employee class, which is the biggest contributing factor which leads to the above difference)


Those aren't usually time-sensitive.


This seems like a problem with your friend moreso than with 3D printing in general. Most people I know who hear about 3D printing don't immediately think of making weapons. Toys and weird gadgets tend to come to mind first, or maybe an office accessory like my laptop stands. The fact that your friend immediately jumped to the conclusion that it's for making weapons says a lot about the way they think about the world.

I agree that the law seems to validate the viewpoint, but I disagree that it's a common one, nor that you should have had to spend time building that trust.


That case started over a year ago, I would have expected the topic to come up long ago if this was motivated by the shooting. Granted, lawmaking takes longer than public sentiment lasts, but I didn't really hear much about 3D-printed guns at the time.


NY legislators have been pushing for this in public statements over the past year.

e.g. https://d12t4t5x3vyizu.cloudfront.net/ritchietorres.house.go...


If I recall correctly, this is state-dependent. Some states just say you can't sell it, some require you to serialize anything you make even if you won't sell (the process of serialization isn't specified), and some ban self-made firearms completely. If you cross state lines with something you've made, you need to make sure you're following laws in both states just to be safe.


True, a terrible patchwork of different state laws makes it very easy to unknowingly violate a law.


> either way, at least you can't toggle between indexes starting at zero and one

You can, you just have to explicitly assign something to a[0]. Lua doesn't have real arrays, just tables. You have to do it for every table you use/define though, so if you mean "toggle" as in change the default behavior everywhere then I believe you are correct.


iirc that value at key zero won't be included in any array handling functions. if that behavior were toggleable we'd have the kind of nonesense that early APLs allowed before they realized that's a bad thing to stuff in a global variable you can write to at any time in your program.


Because Lua's Hello World is just `print("hello, world")`, which looks a lot like Python and doesn't tell you much about actually using the language.


The point is, it shouldn’t be too hard just to find an example and get a sense of the language.


Learn x in y is always my goto: https://learnxinyminutes.com/lua/


So put a slightly more informative hello world example then.

Look at the Go homepage. Or Nim. (But not Rust sadly.)


Rather than Hello World, I'd rather see something like a classic Fibonacci calculator with recursion. That way you see function definitions, variable typing, math operations (Lua doesn't have increment/decrement operators or augmented assignments), and even tail-call recursion if it's an option. Hello World is really only useful as an environment verification - do you have your machine set up so you can run the code, or are you missing something?


  function fib(a)
    return countfib(1,1,a)
  end
  function countfib(a,b,n)
    if n == 1 then
      return a
    else
      -- proper tail call
      return countfib(b,a+b,n-1)
    end
  end
  print(fib(6)) --> 8


Look at the Go homepage. It has a variety of examples.


The GPUs, sure. The mainboards and CPUs can be used in clusters for general-purpose computing, which is still more prevalent in most scientific research as far as I am aware. My alma mater has a several-thousand-core cluster that any student can request time on as long as they have reason to do so, and it's all CPU compute. Getting non-CS majors to write GPU code is unlikely in that scenario.


> Getting non-CS majors to write GPU code is unlikely in that scenario.

People mostly use a GPU-enabled liblaplac. Physics, chemistry, biology, and medicine departments can absolutely use the GPUs.


I provide infrastructure for such a cluster that is also available to anyone at the university free of charge. Every year we swap out the oldest 20% of the cluster as we run a five year depreciation schedule. In the last three years, we’ve mostly been swapping in GPU resources at a ration of about 3:1. That’s in response to both usage reports and community surveys.


This is whataboutism. Just because they are also doing it doesn't mean its okay to do at all. It just means that Mr. Beast is the one being focused on here, and that other organizations will have to wait their turn.


I like to call it "Selective Enforcement"


To add: Exercise builds strength, including cardiovascular. Just having a low bodyfat % isn't the epitome of health, there's plenty of facets to focus on.

I have a friend with a heart condition, prior to surgery he couldn't even walk 100 ft or stand for more than a minute. He put on significant weight, partially due to lifestyle changes when his heart was failing. Now he _has_ to walk a lot to strengthen his heart again, and he's working on his diet to lose weight as a whole separate component. The walking has nothing to do with weight loss for him, it's purely about strength. I think a lot of people fail to make any kind of distinction there, and they just think of exercise as a way to lose weight.


Maybe include it in the Assist response window? I know you can disable Assist from the settings icon there, but also including a way to avoid AI entirely where it's most relevant also seems like a reasonable approach.


Now, the first few times you interact with Assist, a dialogue automatically appears asking you how much you want it to show.


Most people have been trained to just ignore that stuff.


Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: