debaserab2

Is the mental model switches between classes, HOC's, and effects really that taxing? Rewriting your code to match the current framework flavor is really less exhausting?

Couldn't the frequency of profile information itself be considered a uniquely identifying attribute? Couple that with something that's harder to change on every request (such as IP address) and I imagine you can confidently build a profile out of that.

Now that Discord has taken such a strong foothold I wish they would offer an "enterprise" skin or something like that because I would love to replace my work's Slack chat with Discord. Discord is miles ahead of Slack in terms of stability.

Actually...

You don’t have to be “living a lie” to have a meaningful experience with LSD or any hallucinogenic.

I think there may be some overlap with Amazon Systems Manager too.

If you have a messy codebase with logic mimicked on both the back and front end its not just the developer experience that suffers - the user experience will eventually suffer too.

What about when the engineering decisions you make today affect the politics of the future?

Perhaps this doesn't apply to your area of engineering, but I do feel that it does affect a substantial chunk of the HN audience.

How and what data you choose to collect about internet visitors is no longer a purely technical analysis, it now has broader implications that potentially involve political actors. You don't know who might have access to that data in the future or what they might do with it.

We as engineers are the final implementer of these decisions. Should we really abdicate the ethical responsibilities tied to these decisions so easily?

I don’t think we’re talking about someone making neutral statements about their favorite color.

You aren't free unless you can say and do things without consequence? What?

You don't think there's any kind of limit that most people will reach?

I know I have the same cable unbundling problem and have mentally decided that the maximum amount of subscriptions I will have is 4. If I want to subscribe to a new one, I find the one I'm using the least and unsubscribe from it first before adding another.

Why do you need 30-40 reddit accounts?

From https://news.ycombinator.com/item?id=18250466:

"OOP is just a mental model. Deep down everything is made of bits. The church of OOP has failed but if something looks like a duck, walks like a duck and talks like a duck it probably is useful to make a duck class. We're now down to fighting for nuances. You can do most things with OOP or without OOP but each path has some upsides and downsides and most of the time it's good to use some things it provides where it makes sense and not get too religious about it. The great architect has the foresight on how the code will be used in five years and design it accordingly."

Hide is super useful for threads you want to read but have the typical knee-jerk flamebait war responses at the top that turn into massive comment trees that you want to skip.

A lot of times the good stuff is at the bottom.

Removing features to decrease maintenance overhead is also a pretty legit reason, and you don't have to be a corporate site for that to apply to you (I would say it applies even more to a hobby site).

That said, I really hope favorites isn't removed because even though I only discovered the feature a few years ago, I really cherish the comments I've favorited.

How many studios are even going to produce art assets at the level of fidelity that 8K provides? These installs are going to be huge.

I agree. I do not like Riot's "startup" approach to game design, where gameplay elements are plucked from the most popular titles on the market. The games have never felt innovative to me, they just seem like they took from everyone else and then focused on iteration so much that it gives the features and gameplay a level of polish that a lot of games don't get (especially from a esports vantage point). The art style also feels so accessible to me that it lacks a certain soul that defines a good game.

AutoCAD is an interesting example because it is consumed by professionals much in the same way a library is used by programmers. I think you'd want to be a little slower moving in that space than you would for your average application.

> turns programming from a white collar to a blue collar profession

why would that be a bad thing?

> which by definition will be at least as large as static HTML for the same content

Not really by definition - tables rendered on the server side are a good example of a payload that can easily be larger than template + dataset.

This works like every other AWS CLI tool - it uses your shells AWS credentials dir or ENV vars

I’ve never been more inclined than now to do the same thing.

How do you deal with spam?

How do you ensure your emails don’t get junk mailed?

No, the aws start-session command does not require a keypair - you're reading further down in the instructions about other ways to connect.

If you're willing to entrench yourself deeper into the AWS ecosystem you can go completely keyless and manage access solely through IAM by inventorying your instances in AWS Systems Manager - then you can start SSH sessions right from the AWS CLI itself[1].

[1] https://docs.aws.amazon.com/systems-manager/latest/userguide...

If the rate of unexpected things is "sometimes" and not "very rarely" it probably does indicate that there are problems with development, build process or something else in the infrastructure.

Most of us are building CRUD apps not sending people to the moon.

Does the v-if execute on the server side?

IE11 still accounts for 3% of our audience. We're B2B HR/performance management.

Still too high of a % to ignore.

Using dates as release version names has its own problems. The key thing I find challenging with them is you don't know what the release name will be until it's out there (or you try to guess ahead of time and are often wrong).

This makes talking about and planning for a release unnecessarily verbose. You can only describe your releases in terms of relative time. Item A is going in the next release. Or the release after next. Or three releases from now. It's much easier to know the name of a release ahead of time.

I did away with semver for my company awhile ago, moved to dates for a little while, and now just do plain numbers. It's basically just a simplified version of semver without a distinction between MAJOR or MINOR patches. This works just fine when you're building a web app and not a library to be consumed by others.

Well... how were they?

> In terms of using a primary db like postgres or mysql as a queue, I have personally run into issues with this multiple times. I would recommend never to do it, except on the smallest of side projects.

Postgres is fine as a queue for medium to large sized projects as it depends completely on your workload and what sort of performance characteristics you need. Thinking about it in terms of project size is the wrong way to evaluate it.