sebular

It’s because there always were two types of engineers and the difference was never clear until this technology existed. Some love the craft, and some love the results.

It took me forever to realize this, but I'm pretty sure the "options" ("ghost", "melt", "evanesce", and so on) aren't anything at all, just terms that are all adjacent to "fade" which can be selected for some reason. A search for those terms in the repo doesn't come up with anything.

I was really hoping to see what the "melt" effect looked like :(

The way he animated points with an increasing z value made it click for me. Now, when I look at the formula it makes sense. The larger the value of z, the smaller your projected x and y will be. This checks out because things get smaller as they move farther away. Something that’s twice as far away will seem half as big.

The rotation formula eludes me.

Nonsense. Open the console on l any mediocre webpage and you’ll see a stream of JavaScript errors. But it’s still working. One script crashes? Doesn’t matter to any other script. Unhandled exception? Rest of the app is still working fine. Hell, that button may work if you just click it again.

And CSS syntax error causing only that single line of code to be ignored while every other line of code works fine is the very definition of fault tolerance.

What else could you possibly want?

I’m browsing around on this site and don’t see any indication that this is satire. I think your initial reaction is correct.

Congratulations! Beautiful design, very simple and appealing. The onboarding flow filled me with optimism, which I appreciated.

That said, I bounced off at the pricing. The $30 lifetime price isn’t something I find inherently too expensive, but I need to see if the app works for me before committing to it. It was weird that if I went forward with the free trial it would automatically put me on the exorbitant $3/week price. That option was repellent and got me worried about forgetting to either cancel or make the purchase. Compounding the issue was uncertainty about whether I even _could_ make the lifetime purchase after accepting the free trial.

Then I lost momentum and started thinking about how I was about to drop $30 on an app that’s just some HN poster’s 4-month project, and I have no clue how crippled it will be if (when) you decide to shut down the API.

If you’re confident the app itself is habit-forming, I’d recommend just letting people use it for a couple weeks and then hitting them with the paywall. And when you’re asking for that kind of money and using the word “lifetime”, I’d describe how you’re going to guarantee that to the user, even if they’re the only person who ended up buying your app.

Edit: Now I’m stuck on the payment options screen with no way to delete my account. Not happy about that.

I don’t know about that. Flying under bridges has got to be one of the most popular simple joys available in a flight sim.

I made a simple web game using Rapier that takes advantage of the deterministic physics to prevent cheating by running physics and computing win/loss states on the server (though I stupidly haven’t implemented the high score board yet).

It’s an homage to the old Taito electric arcade game “Ice Cold Beer”

https://beerbubble.xyz

Nobody would pay to supply to the grid. If it came to that, panels would have an automatic shutoff, or some device that burns off excess electricity by doing pointless work.

No, you misunderstood the interface. While they certainly encourage you to use the weird biometric scanner it's in no way required. However you do have to have the Amazon app installed on your phone. When you open the app there's an option to reveal a QR code which you scan at the turnstiles.

Try using the thermal limiting feature in the right-hand battery menu. Any game I’m playing, I bring it down as far as I can without unacceptable impact to performance. Often I find that I can set it to 7-9 and the fan goes nearly silent without any major performance impact.

NvChad is excellent. I recently finished converting my older .vimrc-based configuration to an entirely lua-based one on top of the base NvChad setup and it‘s just perfect.

Just pinch the screen a bit and it’ll zoom out to fit the text. Clearly the site wasn’t designed with mobile in mind but there’s no need to make a big deal out of it and say it isn’t readable. I just read the whole thing on my five-year-old phone.

Since the video game developers of that era certainly had access to reference CRTs while building games, you’re experiencing something closer to how it was originally intended to be seen.

I work from home and all of my driving outside of road trips probably averages out to about 40 miles a week. Considering that I paid $15k for my ICE car, something like this would be super attractive.

Heck, it would be even more attractive if I was commuting ~5 miles a day, which is farther than I’ll ever be willing to commute.

I was excited by Hathora and sat down to integrate it into a project I’m working on, only to find that it only supports Websockets.

Given the inherent latency of using TCP-based messaging, it feels odd to advertise this as being good for real time games.

I see that UDP is on the roadmap, so that’s good. Will you support WebRTC for building low latency real time gaming experiences on the web?

I have the revised K3 and the keycaps don’t have any quality issues. You should be good to reorder.

This is absolutely not true.

I worked with a guy who used a DSLR as a webcam and his picture was totally remarkable over Google Meet and Zoom. The very first thing I did was send a screenshot of the meeting's tile view to a friend, asking if he noticed anything funny about one of the videos, and he easily spotted the one I was talking about.

Every time we had a new team member join the calls, they would immediately comment on this guy's ridiculously nice picture quality and ask him what kind of camera he had.

If they could export mahogany, then they’d be cutting the rainforest down to export mahogany. What is your point?

The word "electronic" neither appears in the title or body of the article, nor in the HN post title.

I might actually be tempted use voice assistant/command software if I could communicate with it silently through a discreet sticker or necklace.

People from the 1980s are still alive and they’re not making anything more impressive than anyone else.

These people weren’t magicians only held back by a lack of computer power, they were (again, “are”) regular people trying to maximize their output given their resources.

Let’s say you go back and hand a powerful computer to them. What would Mac Paint look like? I’m sure it would have colors (assuming you also have them a monitor), probably a lot more of those goofy and useless textured fills nobody wants, layers, probably some filters, higher resolutions, and probably simple brush strokes. But do you really think they would manage to implement any of the seriously impressive features that modern Photoshop has? Content aware fill? AI upscaling? Of course not. It would probably take them a long time to get smart selection working in a halfway decent manner.

I'm assuming they mean it wasn't forked by clicking the "fork" button in GitHub, which creates a link at the top of the new forked repository page connecting it to the parent repository.

It is a true fork though, both projects have the same commit history.

I can relate to this. Keep your eye open for new opportunities and eventually you may find something that both pays well and contributes to solving the climate problem.

The good news is that more people are finding ways of doing meaningful work while also turning a profit. An obvious example is working at a place like Tesla, but there are an increasing number of lower-profile for-profit companies that need tech + data talent to execute.

My apologies. Your anecdotal experiences on a random team at Google clearly prove that anyone who hires US-based engineers at market rates is making a giant financial blunder.

Also it wasn’t even slightly condescending of you to declare that US-based engineers are overpaid and ask HN for validation. It was just a brave stance taken by a bold intellectual who knows better than everyone else.

The simple answer is that "whatever metrics you prefer to use" include qualifications that overseas engineers often cannot satisfy.

Great engineers are human members of a team, and there's more to a team member than their LeetCode score (seriously?) and/or how many GitHub stars they've obtained.

Just some examples off the top of my head:

If you're building products to target US-based consumers, you don't need to provide as much contextual information to a US-based engineer. They will have a stronger intuitive understanding of the product, and there's a better chance that they'll know when it's appropriate to push back and question something. There's a reduced cognitive load in communicating with them. And of course, there's a better chance you're going to enjoy spending hours working with them.

You're going to struggle as a novice if you're quick to form opinions about things that you don't fully understand, especially if those opinions involve rejecting wildly popular tools used by people with far more expertise than you have.

People who understand React/Vue/Angular are free to criticize them (and have many valid reasons for doing so), but when you do it after following a beginner tutorial or two, you're just being ignorant.

How do I know this? Because you're criticizing React for forcing you to "do everything through a JSX template" and "debugging through a transpiler", which tells me that you aren't aware that React can be used without JSX and without any transpiling.

Since that information is available to you on about the fourth paragraph of the "Getting Started" page on reactjs.org, you clearly haven't bothered to learn much about it at all.

You assumed that there was a strong uniform ideology because scientists aligned with one political party, when in fact there was a strong uniform body of data which caused the scientists to agree. They aligned with one political party because it supported an objectively correct stance, while the other did not.

Your heuristics utterly failed you, leaving you blind to a devastating truth at a critical moment. While you seem to be on the road to acknowledging the truth about climate change, I can only hope that you are also ready to let go of the flawed reasoning that set you so far back.

How do you explain the loathsome UX of software like GIMP?

I'm an American and I love smiling at strangers and receiving a genuine smile in return. It's the perfect minimal conversation: no words, just sharing a moment of mutual positivity and kinship. It's like you said the perfect thing, except you didn't have to think of anything clever.

It sounds as though people in some countries interpret it as if the smiling person is on the inside of a joke and you're on the outside, or even the object of ridicule. As if the default is hostile intent. It sounds like a terrible thing to assume about your fellow stranger, to be honest.

Maybe the point is that if you start off assuming maximum hostility, the reality is more likely to be a pleasant surprise?

At any rate, we have common ground when it comes to those meaningless questions. They're hollow and they ruin the perfection of a nice wordless smile or simple "hi" or "hey". The absolute worst is when you pass a stranger and say "hi" and they respond to your back as they walk off into the distance, "hey, how ya doin?"