HNHacker News
TopNewBestAskShowJobs

eawgewag

122 karma · joined November 18, 2024

submissionscomments
eawgewag··on The Profitable Startup
I think your point would've been clearer if you clarified up front that Linear has taken 50M+ in funding. You would have clearly indicated where in the range of middle ground you are speaking from.

I know of YC startups that have taken <1M in funding and are now profitable. Similarly, the Discord founders (995M+ funding) have dropped hints on this very website several times that they are now profitable, but they would be laughed out of this room if they tried to outright claim that they are a "Profitable Startup". To say that Linear's story is comparable to any of these is, well, a stretch.

eawgewag··on The Profitable Startup
Wow.. really changes my perspective on this article to find out that Linear has raised 50M+

Thanks for this source

eawgewag··on My Time at MIT
Honest answer: as an MIT computer science grad, my life has been infinitely easier thanks to the label. But my time at MIT was very hard, and it is a difficult place for a young person to be.

It really depends on the child. I don't recommend MIT in particular to just anyone. Not sure if this lack of recommendation affects other top schools -- I don't have personal, intimate experience with them.

eawgewag··on My Time at MIT
Somehow I was/am both of those students at the same time!
eawgewag··on My Time at MIT
I spent my undergrad at MIT and I completely felt this way! I wish so dearly that I delayed my undergrad by at least a year and spent some time maturing. So many interesting and wonderful things I've missed out on from that place, simply because I was not mature enough to appreciate it.

If my child wants to go to MIT, I would strongly advise them to take a gap year.

eawgewag··on Why young parents should focus on building trust with their kids
> A dog isn't a kid obviously, the dog you leave him outside of the home once you're done and it requires maybe 30 minutes of attention a day. a kid, it's constant attention.

You can have a relationship with a dog like this, but you don't need to. You can have a relationship where lots of attention and love is shared. It's very meaningful and powerful.

eawgewag··on Why young parents should focus on building trust with their kids
My dog trainer explained this to me like this: trust is like a bank, you build up and store a lot of trust, and sometimes you spend some trust, but if there's a lot banked up it will be fine.

The first day I got my dog, he had parasites in his ears and stomach. We had to force down gross medicines into his ears and his mouth, and he hated it and us for it.

Three years later we have built up so much trust that I clean his ears every bath and he stands still and waits for me to do it. He still hates it, but he trusts me and knows that I'm not trying to hurt him.

eawgewag··on Sonos CEO steps down after app update debacle
I was an S1 app user as well, I've never even used or heard of S2 until the recent drama. I think it's worth highlighting that "Play X in Room Y" mandates defined rooms, and if you are in any kind of living situation in which this is not the case, Sonos is not right for you.

As a long time apartment/condo dweller, Sonos basically can't do what I'm looking for.

eawgewag··on Cosmos Keyboard: Scan your hand, build a keyboard
I've done the switch! My 2c:

If the Kinesis is working for you, I would not switch. It's an extremely high quality board and most of these Dactyl's are all attempts to replicate the Kinesis at a more accessible price point and/or with higher amounts of customizability. The tradeoff is that they tend to be extremely fragile, have really poor build quality, and have zero to none customer support attached.

However, the KA doesn't work for everybody. I find it too big and the switches too heavy. So I opted for a custom approach, which sadly only survived about 4 months.

eawgewag··on Sonos CEO steps down after app update debacle
I've owned Sonos for 10+ years, and I would not consider their products easy to use. They cater to a very specific use case (homeowners with distinct closed door spaces, 100% investment in their ecosystem, low interop outside of the ecosystem including with other Music streaming systems) and if you fit that narrow mold, you will have a great time. But if you don't, you will find yourself with a lot of overpriced equipment for what it is.

In the 10 years I've owned them, I've used the app less than 10 total times. I much rather prefer just using them as an over priced surround system and use my Playstation to play music through the TV/sonos.

eawgewag··on Best Pens for 2025
Just want to say, I've had incredible customer service experiences from Jetpens. If high end stationary is important to you, I highly recommend this store.
eawgewag··on The Future of Htmx
> React was created as a not-a-framework-but-a-view-library

Honestly, I think this was the biggest mistake the React team made. It was never intended to be this way. It was just marketed this way in order to convince people to try it.

Once you started to use it you could very easily tell how it never fit in the traditional MVC model.

eawgewag··on The Future of Htmx
> 1. If you consider yourself a "backend developer" only and want to write the minimum amount of JS/TS.

This is a great point and should be underscored more. I think generally the HTMX vs React/Vue/Svelte argument gets undercut when people don't express their innate bias on which part of the stack they want to give more control to. HTMX is great if you're pro-expanding the server; JS Frameworks if you're trying to expand it from the application layer.

eawgewag··on The Future of Htmx
As a React developer, I love that HTMX is trying to aim for stewardship and "No new features as a feature". IMO, page router NextJS is perfect (and in line with the original API it pitched), and the bifurcation to app/page router has been complicated. Yes, I am fully aware that NextJS works with both app/page. I just find it mentally confusing to wrap my head around both worlds.

I feel this way about base React too, including -- functional/class components, hooks/non-hooks, and more recently, RSCs/Client components. Although I'm more willing to see React as an evolving research project, as contradictory as this may sound.

eawgewag··on Ask HN: Git Alternatives – Sapling vs. Jj
I'll use JJ through an integrated terminal in my editor
eawgewag··on Ask HN: Git Alternatives – Sapling vs. Jj
JJ is incredible. Highly recommend it. I can't put into words what a game changer it is for my workflow.

The only thing I reach for for git now is `bisect` when I need to debug an oncall issue.

eawgewag··on If not React, then what?
I'm definitely a fan of LiveView and Turbo. I think they present reasonable choices for applications that are more complicated than a static site and less complicated than a full application. I would like to see their interop story with React improve, however, since I think a lot of impetus towards React comes from the fact that the core business product, which has high application/interactivity requirements, is (understandably) in React, so the cost of build is significantly lower staying within the ecosystem.

This is actually something I think a lot about, because in my company I am the TL of all the setting pages. We don't have high interactivity requirements, and it's reasonable to explore a different path. But the core product is in React, and there's basically no justification to rebuild it in something else just to build out settings pages.

eawgewag··on If not React, then what?
I can't speak for other people; I can only speak for myself. I was an early adopter of React (around 0.12) and wasn't particularly interested in, or technical enough, to understand the "cool" things. I wasn't swayed by "hot reloading" or "virtual dom diffing" -- I didn't have a build setup that could hot reload, and I also did not even understand what the virtual dom was. But when I looked at its code samples, React answered my three basic concerns very clearly, in an obvious way:

1. Component based architecture

2. The ability to express view as a pure function of state

3. The ability to express HTML and code together in a neat and ergonomic way

This is what I mean by obvious -- all experienced frontend engineers I knew at the time immediately got it, they got that React nailed these three things, and why they were important. Surprisingly, even new frameworks don't always lead with these three principles, which makes me less likely to believe that they resolve the particular concerns that I find of most importance.

eawgewag··on If not React, then what?
I really appreciate this comment. You've very eloquently put into words how I feel about React and the ecosystem, and also my exhaustion towards these "anti-React" posts, which stoke an angry mob without offering obvious alternatives.

And I think the crux of the problem is that there is no obvious alternative. That isn't to say it can't, or shouldn't exist. I'm not a React loyalist. I was a working frontend developer when React came out and I remember how it took the web community by storm, because it was an obvious step forward.

When the alternative exists, it will be as purely obvious.

eawgewag··on If not React, then what?
Said this somewhere else, but: honestly, that wasn't clear to me from the article, and judging by the comments section to this post, I don't think I'm alone. That's part of why I advocate for defining these terms up front, because one person is talking about whether or not Linear should be in React, another person is talking about whether or not Linear's docs should be in React.

I don't appreciate the rudeness. I wasn't rude to you or the author, don't see any reason for you to be rude to me.

eawgewag··on If not React, then what?
Honestly, that wasn't clear to me from the article, and judging by the comments section to this post, I don't think I'm alone. That's part of why I advocate for defining these terms up front, because one person is talking about whether or not Linear should be in React, another person is talking about whether or not Linear's docs should be in React.
eawgewag··on If not React, then what?
I honestly think this conversation gets overly complex because we fail to define the kind of websites we are talking about. These are my definitions, so I'll just share them upfront:

- a web site -- which has low interactivity requirements. Blogs, documentation sites, etc, go here. A vast majority of websites are in this bucket

- a web application -- which has high interactivity requirements. Things like Gmail, Linear, Google Calendar, and an enormous amount of SaaS apps fit in this bucket of things.

React is better at anything else at making the second. React developers happily pay the weird tradeoffs that come with it in order to efficiently develop the second.

React is pretty reasonably good at making the first, but the negative costs are more obvious.

As someone who has worked on one of the most consumed React apps in the world (Discord), I think the concerns with React are overstated. People want a good product, they don't care about the framework and it's costs. React is one of the most efficient (in terms of developer productivity) ways to get there.

I'm not a React loyalist; I would love to see someone dethrone React. My ears are always to the ground for new developments in technology. In my opinion it hasn't happened yet, but I would be surprised if it never happens.

eawgewag··on Ask HN: How does one negotiate for a remote job?
Can your friend focus on all-remote companies?
← PreviousPage 2 of 2