varrock

From my understanding, though, the Netscape project was started from scratch as a result of trying to avoid any complications with the Mosaic browser.

How are you feeling now? I hope you are doing better. It's hard to read your experience. These are very unfortunate times.

This is the first time I am seeing these remarkable videos. I cannot tell you why, but I am feeling awfully emotional while watching them. It cannot be nostalgia, as I wasn't there during the recordings of these videos, so I'm not sure what it could be.

A comment above mentions that the benefits of an ortho board are not worth the learning curve of typing on one. Would you mind addressing the benefits you've found as somebody who is endorsing them?

You have a great website. I was especially curious about your minimalism section and how you list all of your possessions. May I ask; do you truly not own any bedding? I'm similar to you such that I find extreme value in being able to pack up my things and go somewhere else with relative ease.

Your point one isn't making sense because the parents are not caring for themselves, they are caring for another person. If they wanted to exercise, they'd have to find the same hours as those without children, which is usually before work or after work. They probably have a harder time doing that, too.

I used to enjoy this place because the community expanded on the content that was posted, thus extending the life of the article. Instead, we've reached a point where people seem to be doing the opposite in the way of critique. I can understand comments that criticize the intricacies and theory of the content itself, because that does in fact lead to good discussions, but the more trivial complaints don't add anything substantial to the conversation and unnecessarily bloat up the comments.

A trend I've been seeing on HN and Reddit alike are articles that are not in depth, but allow the users of the medium in which they are shared to have a reason to talk about something. This post probably got more attention because it was a dedicated link versus somebody asking HN if they think React is becoming a black box.

I'd much prefer the latter, but it seems that links are the way of websites such as these.

> 1. the prevalence of OO concepts in programming education and in practice in most engineering teams

What makes this point tricky is that React did initially introduce their library with OO concepts for years.

> The performance of fetching a mildly complicated query (3 joins) ended up being more than three times slower than Hasura or PostGraphile.

Please forgive my ignorance, but these type of conversations always intrigue me and make me want to learn more. As a software engineer, at what point are you running these performance benchmarks, and how are you doing them exactly? How have you had time to make these decisions and pivot to other technologies?

Which size did you find appropriate for your needs?

I'm not going to say you're wrong, because I don't have claim to back mine up, either. So, this is for the sake of discussion.

The sentiment that everybody reaches for Redux is tired, in my opinion. After following many in the web development community and keeping up with online forums such as this, it's fairly clear to me that people have moved on from the heavy armor previously associated with React if they have a choice. For instance, people learned that they were using Redux for prop drilling, which led to many switching over to the context API natively from React. Another good example is Gatsby, for those who realized they have a static site and would like to address the SEO issues associated with a SPA.

Also, a lot of times, companies adopted React and Redux before the inception of these new, more powerful libraries that are obvious choices on the ground as of August 2020. But, have fun refactoring your entire client side state seamlessly if you're tracking state more sophisticated than the status of the application sidebar.

> I can pick when I work, so when I'm feeling completely mindless and distracted at 2pm I can just zone out and do my own thing, but then make it up later.

This is by far my favorite perk of working from home. I’ve been able to max my efficiency. When I hit this wall, I usually go do something that requires me to move around, such as going to the grocery store or doing laundry, which are things I would’ve had to do anyways. The difference is that I’m doing those tasks when I’d otherwise be sitting at my desk being unproductive. It’s kind of like intuitive eating; working when your brain is up for it. Of course, you can’t utilize this luxury every day and every hour, as often times you do need to bunker down to accommodate the typical 9-5 schedule. But, it’s still much more apparent than when being in an office.

Has anybody befriended you after those type of conversations? I've had success explaining why I'm not drinking, but afterwards, it's difficult to reconnect.

I definitely agree with this sentiment. However, if there is any development job where enthusiasm would be of a benefit, I would think the front end is a good candidate. I imagine it also depends on the culture of the workplace, too. Some may favor the "trends" that are associated with the web, while others may just want somebody as you describe.

I do not hire developers, but I can imagine that with the lower barrier to entry for front end jobs in 2020, companies have a difficult time differentiating all the new grads/bootcampers/self taught developers. It's almost teetering towards the same conversation as the leetcode problem -- merely finding a way to cut the pool of candidates given the vast amount to begin with.

Do you ever drink decaf? It sounds like coffee was a real hobby of yours. Although your health is more important, it is unfortunate to see a hobby dissipate like that.

> but the physicist can learn to build and the engineer can learn theory.

So is this why frameworks exist? To abstract away the theory that proves something more "performant" or "sufficient", and allow the builder to do their thing?

How can you tell which one is right for you? So many computer scientist graduates I know ended up pursuing software engineering that I've mistakingly conflated the two.

I have the opposite take; I think it shows how well they do their jobs. It reminds of the Steve Jobs quote, "Simple can be harder than complex"

Thank you for writing this. I saw how well ASP.NET Core performed in the 2020 Stack Overflow Developer Survey and I was curious to hear from people who have had good experiences with it.

[0] https://insights.stackoverflow.com/survey/2020#technology-mo...

I’m very junior, so take what I say with a grain of salt. But when I was determining if I should use Firebase or not, my biggest hesitation was simply that if Firebase ended today, I have to completely transition my application’s architecture.

Though that is unrealistic, even thinking about it was enough to make me want to be in full control of my application’s various layers.

I'm a front end developer, so NestJS was a blessing for helping me write my API. It gave me a set of rules to follow and amazing utilities to make my life easier, such as exception filters [0]. One thing I admittedly struggle with is knowing when to create a new Nest Module versus a new service in an already existing module, and I do not think Nest provides such guidance on application architecture. However, I believe this is a result of my minimal back end experience, and shouldn't be held against the NestJS project. Overall, I am really enjoying it.

[0] https://docs.nestjs.com/exception-filters

Great read, though his writing style is less intuitive if you are fairly new to JavaScript and trying to grasp some of its concepts. For example, in his reduce function [0] example, he names his variable "current" to bind the accumulated value the reduce function is going to eventually return. That is a totally fair name, but I don't know if it really "clicks" if you were reading over this for the first time. I think it would be faster to grasp the reduce function's purpose if it was simply named "accumulated" or something alike, especially when this snippet is advertising the idea of higher order functions and callbacks.

Little things like this I am nit-picky about, but overall, great book.

[0] https://eloquentjavascript.net/05_higher_order.html#h_fx3e34...

One thing I've struggled with in JavaScript is choosing a more functional or OOP approach in certain situations. I can never tell if I should stick to one or the other. Allonge sounds like it'll really help me figure that out.

From my personal experience, I was not ready for this book when I was a beginner at took a stab at reading it. I had written in JavaScript before and stumbled upon this book through the Internet, and it demotivated the life out of me.

I am now about a year and a half of being deeper into the language, and I have finally picked the book back up again.

I decided to read Eloquent JS before exploring Allonge. Can anybody who has read both give their opinions on each? How are they similar/dissimilar?

The way you interpreted my question is correct.

I have a feeling the fake emergency calls are much more obvious than a real one, though. I will say, however, that emergency family calls are probably successful in the older generations.

Exactly. It's just as equivalent as having to memorize where some hypothetical share button is on a webpage. I've had this experience trying to change my settings in iOS; I often forget where I'm supposed to click to get to certain settings.

Can you link the HN thread about good software development books?