BanazirGalbasi

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.

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.

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.

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.

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?

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.

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 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.

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.

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.

It really depends on what you're doing with your computer. For all of my computer science classes, a Chromebook would not have been sufficient. We did have a remote desktop server we could log into that had most of the tools we needed, but I don't even know if RDP runs well on a Chromebook. Even then, I found that I preferred developing locally so I didn't have to deal with shared computer bandwidth, which means a Chromebook would be completely inadequate.

For some of my friends outside of STEM degrees, a Chromebook would have (mostly) been fine. Given that our laptops were a major source of entertainment for us at the time, I think something with enough power for indie gaming and HD video is a must.

What action has been taken as a result of that ruling though? The Supreme Court might as well give the president a big thumbs down if nothing actually happens.

<This comment requires a Hacker News premium account>

I took a class hosted by a group affiliated with my local renfest, which kind of kickstarted me to actually follow up on all the research I did. Having experienced instructors helped with the beginning learning curve, plus they pointed out early pitfalls to avoid (like gripping the hammer too tight). While useful, you definitely don't need to take a class to get started. There's dozens of tutorials on making a basic forge on Youtube - either coal-burning or propane - and you can get started with something as basic as a sledgehammer head for your anvil. Even a Harbor Freight cast iron anvil is enough for a beginner, although they're more likely to crack.

My starting costs were reduced by gifts, and my dad giving me an anvil he made with a piece of railroad several years ago. A basic gas forge from Vevor is around $75, but you can make your own small one from a coffee can, some refractory wool, and a handheld propane torch.

Right now, I just make tools and trinkets for myself. I'm _very_ amateur at the moment, I have more theoretical knowledge than practical experience. Once I get comfortable, I'll make more trinkets and tools for friends and family, then maybe one day make things to sell.

On the cheaper side, Lansky makes a good jig and set of stones that's good for setting angles, and getting razor edges if you already have the angle set. [1] Worksharp makes a similar kit that's more stationary, with several versions at different costs [2]

For a little more, and a little more freehand style, you can try Spyderco's Sharpmaker [3]. My dad has one of these, and growing up he would sharpen kitchen and pocket knives to a razor edge very quickly with it.

I personally freehand sharpen my knives using Shapton stones [4]. I have the Kurumaku at 320, 1000, 2000, 5000, and 8000 grits, although the higher grits don't get used often; usually the 1000 grit alone is enough for getting a razor edge fairly quickly. I got mine from Amazon, but you can find them various places for $30-50 each.

[1] https://www.lansky.com/deluxe-5-stone-system.html [2] https://www.worksharptools.com/products/precision-adjust-kni... [3] https://www.spyderco.com/catalog/details.php?product=77 [4] https://shapton.co.jp/en/#products

It's a bit of a nitpick, but I hate the term "Damascus steel" used in this context. This is pattern-welded steel, which was first called Damascus by Bill Moran in 1973. It offers few (if any) benefits that a solid billet of a single high-quality steel wouldn't, and it offers none that the original Damascus was said to have.

Damascus steel was originally a crucible wootz steel that came from India or Iran and was sold to Europe through Damascus. The alternating colors came from the grain structure of the steel, not from different steel types layered together. As far as I am aware, we still do not know the exact process used to create it, although we have come close, and it's likely that modern CPM (Crucible Particulate Metallurgy) steels surpass it due to more consistent measurements for the components of the alloy.

I am only an amateur blacksmith, but I have spent the last 15 years dreaming and researching to prepare myself. Given that I live in an apartment, I am limited to a small mobile forge that I can wheel out to the complex's grill area where I am actually allowed to have a fire, which limits the projects I can do due to the forge size and temperature. Crucible steel is a dream one day, but for now I just nitpick and try to tell people about the original Damascus, which is (in my opinion) much more fascinating than what gets the label today.

I think it's because Xubuntu was a lighter alternative to Ubuntu when it ran Unity desktop. I don't know how Gnome compares to Unity, but at the time Xubuntu was far better for low-end computers than vanilla Ubuntu so the reputation of XFCE was justified.

This is why reading comments before contributing to the conversation is useful. There are already several comments outlining why a $25 wheelchair, especially a used one found at thrift stores, isn't comparable. Build quality, weight, fit, convenience, portability - all of these are reasons to spend more on a wheelchair.

We don't question why different computers are more expensive than others even though they all do the same job. We don't question why one bike costs more than another despite using the same mechanism for propulsion. Wheelchairs are another good with varying levels of quality at different price points. It's arguably more important for quality goods to be accessible because for many, they're living in these things constantly.

The idea is that there's several layers. If the spy appears like a normal citizen, then they won't be surveilled closely, so the book is less likely to be discovered. Keeping multiple books around means it's less suspicious that they have any given book - you just like to read. Why would the specific book be "discovered" when it's in a stack or shelf of them?

You also don't have to send an encoded message in every letter. If you have plenty of plaintext correspondence with a distant friend, and only some of it has any special meaning, then it will be less suspicious in the first place.

The whole idea is to blend in and not attract surveillance in the first place. Your counter-argument is based on the premise that blending in has already failed, in which case you're right - the game is up and the spy is compromised. Worse, it's possible to intentionally feed them bad information without them knowing (which happened multiple times in WWII). But this entire article (and the book it discusses) is about preventing that entirely.

Keeping ctrl-C as the binding for copy is silly though. Intentionally having poor UX that's unnecessarily confusing to power users because of "reasons" is why Windows can never become a credible developer OS.

After skimming the skills I'm familiar with, I came to the same conclusion. I was actually relieved when I saw that Blacksmithing isn't finished yet, and that's something that I'm definitely still an amateur at. I can't contribute anything meaningful to it, nor do I feel like it really needs an in-depth skill tree because most of it is just applying the same few basic skills in different orders.

I feel like the author should have done a few for areas that they are actually knowledgeable in, then left the rest up to others. These feel too much like they were made by someone who tried to learn the surface of every topic they could access but doesn't know enough to organize any of what they learned.

For people new to the DIY skills it requires to do it right, 2 months seems reasonable. You have to learn the skills, and when you're applying them you stop constantly to check tutorials or look for advice. You take the entire project one step at a time and you do one part before even starting to research the next.

A day of demo leaves you with an empty room with pipes sticking out of the walls. Maybe you've removed the drywall too so now you have outlet boxes and studs to work with. You take the rest of the day to finish the cleanup and triple-check your measurements for everything. Half your weekend has now been taken to demolish and clean up a core part of your home.

The next day you do your framing, including buying your lumber. Again, if you're new to this, you're probably checking a tutorial or plans every 10 minutes as you go so you make sure you're doing it right. If you have time and you're confident, you can get the plumbing set up so that it's ready to drop the tub/shower and vanity in place next weekend.

For someone with experience, this is an excruciatingly slow pace. For someone who is doing it for the first time and may never do it again, this is pretty reasonable. I would absolutely be proud of taking two months to do a bathroom if it means it's done right the first time. Going by the comments about contractors here, that's not a guarantee just because someone else can do it faster.

Regarding using the right tool for the job:

sed, awk, cut, a quick bash one-liner, a simpler editor, an infinitely more powerful IDE, an actual IRC or mail client, an actual presentation program, some online CSV-to-JSON converter, etc.

All of these will take time to learn or find. I know basic sed syntax but I'm never 100% sure that my edit does exactly what I want, so I end up running without -i and then with. I don't know awk at all. I use cut but always mess up the field numbers, and if there's multiple spaces involved then forget it. In all of these cases, it's faster for me to open the file in vim, make the change or grab the word I need, then exit. I'm not saying the tools are useless, but vim is flexible and covers a lot of use cases.

Half these examples are gui programs. Who is realistically trying to replace a presentation program with vim? These seem like strawmen to pad out the list.

Is vim the right tool for every job? No, definitely not. But I think it does well enough that it's okay to lean on it if you already know it.

This is such an elitist attitude, and I'd like to see less of it.

The vast majority of users aren't going to be bothered by those screen specs. For many coming from low-end hardware, it's actually an upgrade. Most work won't be significantly impacted by increasing the refresh rate, and while better resolution can be helpful if you keep multiple windows on the screen, most programs still feel tailored to 1920x1080 screens. Office workers writing emails, reports, purchase orders, and basic spreadsheets aren't likely to notice a better refresh rate and they're more likely to get a positive impact from turning a monitor vertical to fit more of a page on their screens.

Don't get me wrong, I use two 2560x1440p monitors at 144Hz at home, but I honestly get just as much work done on my dual 1080p 60Hz monitors at my desk at work. Saying that a laptop with 1080p@60hz is a waste is elitist and unnecessary in my opinion.

Most repositories have some sort of vetting process as far as I'm aware. In the case of Zed, because it's open-source, it can be examined more completely, although I don't think it's expected for every update to be heavily scrutinized.

In the end, at some point you either have to inspect every line of code yourself or trust others to have done it for you. Package managers fall into the latter category.

Most of my local libraries close fairly early these days, I think the latest any of them are open is 8:00 pm. Because of that, the 7-8 pm time slot is popular and rooms get filled up pretty fast.

I recently found out that there's a local group for the 2600 Hacker Quarterly magazine that meets at the same Barnes and Noble cafe that my book club meets at monthly. They're open until 9:00 pm, which (in the case of the book club) gives ample time to talk about the books we just read, vote on upcoming books, and catch up on events in the area. If everyone has something to contribute, we can easily fill 2 hours of time.

You can use "man <command>" the same as in nix. The man command is an alias for Get-Help and it retrieves the same information.

There's a lot of nix aliases for Powershell commands. Get-ChildItem is also called with ls, mv calls Move-Item, cd calls Set-Location, etc. They made at least some effort to make it more accessible to people coming from *nix or cmd.

Maybe explicitly registered trails (like the one on your land) could grant more access than the default Scottish ones mentioned above. That way the people who are okay with motorized vehicle access can allow it while not affecting the majority who probably don't want vehicles running through their land.

A decade ago several teenagers wore a track through the back of my parents' yard with snowmobiles during winter. I'm not familiar enough with snowmobiles to know how much snow should be on the ground, but they kept going after it was reduced to muddy slush that had been churned up by the treads in the back.