sebular
On the other hand, that’s just traditional banner/video style advertising where the goal is to force specific content on the user. If someone wants to spread the word about their product or service, I’m sure they’ll pay money to advertising services that use agents to inject their message into the global context. This is happening already, we just talk about it in the frame of “dead internet theory” and AI influencers, etc. Anywhere that content is being produced and consumed is an opportunity for the message to be nudged in favor of the person paying money.
I was really hoping to see what the "melt" effect looked like :(
The rotation formula eludes me.
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?
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.
It’s an homage to the old Taito electric arcade game “Ice Cold Beer”
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.
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 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.
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.
It is a true fork though, both projects have the same commit history.
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.
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.
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.
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.
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.